- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2019 04:06 AM
Solved! Go to Solution.
- Labels:
-
Service Catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2019 05:40 AM
Hello Shiva,
Go to business rules on that table and check for condition
1. If any BEFORE INSERT/UPDATE business Rule contains current.udpate(), then remove it from script.
2. If any AFTER INSERT/UPDATE business Rule contains current.udpate(), then add current.setWorkflow(false) in your script.
Please mark as Correct Answer/Helpful, if applicable.
Thanks!
Abhishek Gardade
Abhishek Gardade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2019 03:18 AM
Great!!! Exact same thing i am telling you. Happy to help you.
Thanks,Abhishek
Abhishek Gardade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2022 03:31 AM
Hi Abhishek,
I'm facing the same issue. Will these changes on business rules cause any side effects? I hope it should not make any other changes in the system.Please confirm the same.,
Thanks,
Ankita Kolhe

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2021 09:02 PM
We faced a very similar problem.
There were 4 duplicate activity logs every time we updated a field on a table.
We also verified that there were no 'Before' Business Rules with current.update();
And then we tried something new!
We found a few 'After' Update Business Rules that had current.update().
We made 2 changes to these:
- removed the current.update() line of code and
- converted the BRs to Before Update.
Voila!! There were no more duplicate logs 😉
And truth is there were 4 of these 'After' Business Rules containing current.update(), and that's the reason we had 4 duplicates!