Activity Journal not recording the updates done through Import Set

[Subhadeep1]

I have a requirement where data updated using Import Set (Transform Map) is to be captured in the respective record -> Activity Journal.

For example: There are existing asset records which are updated using the upload file (Import Set). Changes to the asset records which are done using the import set is not getting recorded under the asset record -> Activity Journal.

Is there a way to achieve this?

[Periyasamy P · Accepted solution]

You mean, field changes are not reflecting in record history ?

1. If you are able to see changes in history, then you need to configure activity formatter to display missing columns.

2. If you are not able to see changes in history, then check related transform map whether run business rule is checked or not.

[scott barnard1]

Hi Subhadeep

Generally there is a value on the transform map that is "run business rules" if this is set to false you lose a lot of the history of updates etc. 

Check this first then potentially share some of the transform map and associated logic as someone may spot something helpful

Regards

[shloke04]

Hi @Subhadeep 

This will only happen when the flag "Run Business Rule" on transform map is marked as False as shown below:

Please make sure this is checked.

Reason being why it does not update when this is cleared is because of the below reason:

The Run business rules option on the transform map effectively runs GlideRecord.setWorkflow(false). Clearing the Run business rules option stops all auditing, business rules, workflows, approval engines, field normalizations, and other processes during a transform.

Also I am attaching a list of components which will not run when this flag is turned off are listed below:

https://docs.servicenow.com/bundle/sandiego-application-development/page/script/general-scripting/reference/r_ExecutionOrderScriptsAndEngines.html

Refer to the HI article below from ServiceNow confirming on the same:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0535209

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

[Subhadeep1]

Thanks a lot for the response. Issue resolved now :). Thanks again to all who responded.