- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-15-2024 12:40 PM
Hello All,
After obtaining approval, I am creating the catalog task with an advanced script. Once the task is closed, it does not move to the next step. Please see below.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-15-2024 02:52 PM
The issue has been resolved. I'm creating a change request from the catalog task using a UI action. The script sets the Parent field on the catalog task to the change request number by removing the RITM number, causing the catalog task to not move to the next step.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-15-2024 01:15 PM
Hello,
A quick verification you can do by populating all fields in Catalog Item would be helpful. Since, usually in scripting, if the values return empty/noValue then the script lines goes unpredictable while execution.
If the current.variables.priority, description, short_description are populated and the workflow moves to next stage after Catalog Task closure, then you can add IF blocks for each field assignment with variables something like -
if (current.variables.priority){
task.priority = current.variables.priority
}
If my response proves useful, please mark it "Accept as Solution" and "Helpful". This action benefits both the community and me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-15-2024 02:52 PM
The issue has been resolved. I'm creating a change request from the catalog task using a UI action. The script sets the Parent field on the catalog task to the change request number by removing the RITM number, causing the catalog task to not move to the next step.