Relate field not showing in audit log after saving through the logic hook in version 10.

Hi everyone,

I have a related field and saving it through the logic hook. After saving it is not showing in the audit log in version 10 and the field is selected with audit in the studio.

It works fine when we save it normally in the module but getting an issue with the logic hook.

Please suggest a solution.

Thanks

Laxmi Chand Saini

Parents
  • Hi Laxmi Chand,

    Yes, unfortunately, Audit Log does not log this change.

    However, that may help us to look at the situation from the use case perspective :)

    I think of questions:
    1. What user role requests to log this change? Isn't that other role than the role of the change performer?
    2. How they are going to use that physical data change collected? How are they treat it not physically but logically? Does context matter for consideration of the change happened?

    If they pay attention to a particular field and eager to monitor the change, they probably treat change as a key fact and therefore logically consider it somehow.
    It is possible to help facts-seekers not to go through numerous similar physical changes in the databaseinstead it is possible to help readers more  - use the same logical hook to collect logical key event on the Timeline,  specifying not only the previous and new value but giving a possibility to monitor the named key event within the context and in a form of conclusion  - like this "Tier 1 customer XYZ  has got a Key Person changed from PeterP to BillB. OMG!" 

    Actually, there is an interface to observe key events collected with logic hooks - the Timeline Viewer for Sugar
    It helps to monitor not only for the particular record, but also monitor for the list (e.g. "Tier 1 customers"), dashlet and report.

    The approach of using TimeLine to manage different events regardless of their source and nature and origin is quite common in CRM that collects info rather then data

    Best,
    Dmytro

    Best Regards,
    Dmytro Chupylka

    integroscrm.com
    We make work in Sugar CRM system faster, more convenient and efficient

Reply
  • Hi Laxmi Chand,

    Yes, unfortunately, Audit Log does not log this change.

    However, that may help us to look at the situation from the use case perspective :)

    I think of questions:
    1. What user role requests to log this change? Isn't that other role than the role of the change performer?
    2. How they are going to use that physical data change collected? How are they treat it not physically but logically? Does context matter for consideration of the change happened?

    If they pay attention to a particular field and eager to monitor the change, they probably treat change as a key fact and therefore logically consider it somehow.
    It is possible to help facts-seekers not to go through numerous similar physical changes in the databaseinstead it is possible to help readers more  - use the same logical hook to collect logical key event on the Timeline,  specifying not only the previous and new value but giving a possibility to monitor the named key event within the context and in a form of conclusion  - like this "Tier 1 customer XYZ  has got a Key Person changed from PeterP to BillB. OMG!" 

    Actually, there is an interface to observe key events collected with logic hooks - the Timeline Viewer for Sugar
    It helps to monitor not only for the particular record, but also monitor for the list (e.g. "Tier 1 customers"), dashlet and report.

    The approach of using TimeLine to manage different events regardless of their source and nature and origin is quite common in CRM that collects info rather then data

    Best,
    Dmytro

    Best Regards,
    Dmytro Chupylka

    integroscrm.com
    We make work in Sugar CRM system faster, more convenient and efficient

Children
No Data