How We Can Make custom log field Like As Comment log?

Hi M kumar 

Why to do that instead of playing the regular Comment Log?

Regards

Hi,

why Comment Log is NOT possible to include in a report or in the Historical Summary!

Regards

I'm going to chime in here and say - I agree with you Renzo Leone; of course there's an expectation that Sugar should behave differently than Skype, Slack, and chat text: SugarCRM purposely strives to set themselves apart by thinking and moving beyond conventional boundaries. 

OUR DILEMMA...documenting pci compliance for external audit, the Case Resolution field isn't a log format and is not time-stamped. Additonally, compliance dictates that the history not be editable. SOLUTION? Easy, they thought: use the Comment log. It's problematic now that they are culling examples however, because the value lies within the non-reportable Comments (unfortunately, they assumed if they saw it on the interface, it would be reportable).

Our system is used by all teams for all things, including an external Customer Case Portal, for Quote generation, Product Catalog, Terms & Conditions, Accounts, Contacts, Vendors, Integrations, Hosted Systems , Machines, Registrations, Events, Trainings, Tradeshows, Opportunities, Emails, Meetings, Calls, Reports, IT tickets, Notes, and many other custom modules with lots of processes. Because there are 158 users accessing most of the modules (which mostly relate to other modules) the Comments area, with its timestamp - and ability to notify - has become popular. Making it reportable could solve many additional issues besides the need to document compliance as well. 

Open to ideas and suggestions

(Sugar Hosted / Serve.Sell )

I'm going to chime in here and say - I agree with you Renzo Leone; of course there's an expectation that Sugar should behave differently than Skype, Slack, and chat text: SugarCRM purposely strives to set themselves apart by thinking and moving beyond conventional boundaries. 

OUR DILEMMA...documenting pci compliance for external audit, the Case Resolution field isn't a log format and is not time-stamped. Additonally, compliance dictates that the history not be editable. SOLUTION? Easy, they thought: use the Comment log. It's problematic now that they are culling examples however, because the value lies within the non-reportable Comments (unfortunately, they assumed if they saw it on the interface, it would be reportable).

Our system is used by all teams for all things, including an external Customer Case Portal, for Quote generation, Product Catalog, Terms & Conditions, Accounts, Contacts, Vendors, Integrations, Hosted Systems , Machines, Registrations, Events, Trainings, Tradeshows, Opportunities, Emails, Meetings, Calls, Reports, IT tickets, Notes, and many other custom modules with lots of processes. Because there are 158 users accessing most of the modules (which mostly relate to other modules) the Comments area, with its timestamp - and ability to notify - has become popular. Making it reportable could solve many additional issues besides the need to document compliance as well. 

Open to ideas and suggestions

(Sugar Hosted / Serve.Sell )

We will never get the result while we confuse simple and careless  comment-like writing with  reporting, which demands structured info in its DNA.

I call for considering two roles - Comment Writer and Awareness Seeker (Reader) - which are different - if not opposite - in there target functions. 

Writers make short notes as they like - in comments or elsewere - no obligations about style, form, content, ect- ajust do it as fast as possible. 

Reader deals with others “written thoughts", trying to structure  those exclamations into, hopefully, whole picture of current situation. 

If Reader would like to get meaningful reports on any history,  they do have to think about reports criteria, and about the data  to be properly collected for reports.  CRM /ERP/e-commerce/Skype - whatever  software  systems they use - should be configured to collect  that data in a form that could be somehow useful  for Readers' reports 

And that efforts has nothing to do wth Writers'  commenting skills.

Readers may order software  for preparing data for reports by configuring the software to collect that data e.g. at the very moment data appears(event happens) -  comment posted, meeting marked as held, date has expired, ect.

That is called "to perform key data identification" which is successfully solved by now in many systems by using configurable logic hooks or similar techniques. Key data/event identification procedures are triggered on event happens and  automatically deliver collection of  structured data - report-ready, that can make  Readers reports ever  built - along with awareness ever achieved. 

No need to reinvent the approach - learn how TimeLine Viewer for Sugar collects key data for reporting key events on the TimeLine and consider employing it for users that perform Readers role - for the sake of better current CRM system adoption