Add Log Entry for Updates to Custom Fields

This article provides instructions for adding entries to the activity log when updates occur to custom fields.

Step 1. Create the trigger

This step is to create the trigger that will initiate the script. The methods used to implement the trigger vary based on the Service Desk release.

For r11.x releases triggers are created via the Schema Designer utility. Simply add the following code as a Site-Defined Trigger to the alg (Request Activity Log), chgalg (Change Order Activity Log), or issalg (Issue Activity Log) tables.

POST_CI val_fieldupdate_site(persistent_id, audit_userid, CHANGED_ONLY, customfield1, customfield2, customfield3) 111 FILTER(EVENT("UPDATE"));

For older releases triggers are made by creating a .mod file and placing it in the NX_ROOT/site/mods/majic directory. Name the .mod anything you like, but it is recommended that it be preceded with a 'z'.

MODIFY cr POST_CI val_fieldupdate_site(persistent_id, audit_userid, CHANGED_ONLY, customfield1, customfield2, customfield3) 111 FILTER(EVENT("UPDATE"));
MODIFY chg POST_CI val_fieldupdate_site(persistent_id, audit_userid, CHANGED_ONLY, customfield1, customfield2, customfield3) 111 FILTER(EVENT("UPDATE"));
MODIFY iss POST_CI val_fieldupdate_site(persistent_id, audit_userid, CHANGED_ONLY, customfield1, customfield2, customfield3) 111 FILTER(EVENT("UPDATE"));

Step 2. Publish the Schema changes

The methods used to publish schema changes vary based on the Service Desk release.

For r11.x releases, follow these steps:

1. Save your Schema changes
2. Stop the Service Desk service
3. Run pdm_publish from a command line
4. Start the Service Desk service

For older release recycle the Service Desk service.

---

To make corrections or additions to this article, select the edit tab above.
To discuss or ask questions about this article, select the discussion tab above.