Workflow issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2023 07:33 AM - edited 09-28-2023 09:08 PM
Hi Team,
We have the capability to initiate the RITM workflow when the incident's status transitions to a specific state.
This workflow is responsible for generating Requested Items based on the items mentioned by the customer in the incident description.
Upon submission, the RITM numbers are displayed as part of the list collector variable in the incident table.
However, we have recently identified an unusual problem.
When the workflow is triggered simultaneously for 2 different users (at the exact same hour, minute, and second), the Requsted for user in the RITM gets updated incorrectly.
Additionally, an incorrect RITM reference (referring to another user's request) becomes associated with the incident.
Could someone assist me in resolving this issue?
The issue mentioned above does not occur when there are differences in the timing of simultaneous workflows, even if it's just a matter of seconds.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2023 07:56 AM
Hello,
How does the workflow triggers is it through a BR? What are the condtions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2023 08:35 AM
Hello Saurav11
Thanks for the response.
The trigger condition is in the workflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2023 07:56 AM
It sounds like the workflow/business rule whatever is triggering this process needs to also include the caller/user, but without seeing the script that does this it's hard to say for sure.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2023 08:37 AM - edited 09-28-2023 09:10 AM
Hello Brad Bowman
Thanks for the response
However, the script functions correctly when the simultaneous workflows have slight timing differences, even if it's just a matter of a few seconds.