Hello Everyone,
We have a custom Date/Time field on the sc_cat_item table which is populated via a Business Rule when an RITM is submitted. The field captures the date and time of the most recent submission, allowing us to track when the catalog item was last used.
However, since multiple requests are being submitted by users, this field gets updated frequently. As a result, multiple audit entries and catalog item versions are being created. We attempted to prevent audit logging by setting no_audit=true in the dictionary attributes, which successfully stopped audit records. However, even with this setting, a new version is still being created each time the field is updated, which is not the desired behavior.
Could someone please advise on how we can prevent versioning for this field or suggest an alternative approach to track the last usage date without impacting catalog item versioning?
Thanks in advance for your help.
Regards,
Atik
