Once the sc task state is close completed, then the respective ritm will get to close complete.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Once the request is submitted for a catalog item, the associated Request Item (RITM) has one Service Catalog Task (SC Task). When the SC Task state changes to Closed Complete, the corresponding RITM should also move to Closed Complete.
To close the SC Task, we use the "Close Task" button, which is implemented through a workflow for that catalog item.
Currently, after the request is submitted, I see activities in the workflow overview as shown in the attached image. However, the expected behavior is that all activity comments should appear before the Request Item is marked as Closed Complete. I have attached another image for reference.
UI Action (button script):condition-"current.state < 3 && current.approval != 'requested'",onclick: changeToEdit()
workflow:
In the work flow: Over view, subflow
Once the request is submitted, I am getting activities like this in the below image. but actually, behavior is all acitivite comments should come before the request item is closed completed. I have attached one more image for your reference.
If you have any questions, please ask here.
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11m ago
It looks like at one time the UI Action was updating the RITM state, which is a bad idea for a number of reasons. Are you certain there are no other client scripts, business rules, or a script include affecting the RITM state? The workflow - the 'Positiv End' subflow in this case, should be the only thing updating the RITM. Is a state and/or stage change included in this subflow? Are you testing with newly-submitted requests to ensure the current workflows and subflows are the ones executing? If all of this checks out, the out of order comments could be from the UI action running simultaneous to the workflow, so adding a 10 second Timer activity in the subflow right before the End might help.
