
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā12-16-2018 11:22 AM
I have a requirement that needs Problem state to be set as "Pending change" when a change request is created from a problem record.
Problem state should be set as "Pending change" when a change request is created using the UI action "Create Normal Change" or "Create Emergency Change".
Any help in doing this will be much appreciated!
Solved! Go to Solution.
- Labels:
-
Problem Management
- 6,905 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā12-16-2018 12:36 PM
Hi,
In the UI Actions Create Normal Change and Create Emergency Change, add the below line in the script.
current.state = '3';
Mark my answer as correct or helpful if it helped.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā08-18-2023 03:34 AM
Hi Giga,
Thanks for posting this excellent solution. Succinct and to the point. Keep up the good work.
Regards,
Alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā10-13-2019 09:20 PM
Did simply setting current.state = "3" actually work? I would have expected it to be much more complicated. The value of "3" does not appear to exist as choices for either the state field of the task table or the problem_state field of the problem table. I followed this process:
- Editing the system dictionary choices, I added a choice with "Pending change" label and arbitrary value (I used 110) for the state field of the task table, ensuring the table was problem, and the sys_choices problem_state element of the problem table.
- From the problem form, I edited the Configure Choices option to add "Pending Change" to the slush bucket list.
- Update the Script Includes:
- ProblemState: added problem states: PENDING_CHANGE : "110" (be sure that every state line ends with a comma except for the last line.
- Updated the 'Copy Problem State to State' business rule to add a condition for Problem State IS NOT Pending Change to prevent the state update and avoid creating a new state in the flow
- Like the other responses, I also updated the Create Normal Change and Create Emergency Change UI Actions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā07-02-2024 06:44 PM
1. Problem State choice of 'Pending change'
Solution: All > Problem > All > Open any problem record > right click on State > Configure Dictionary > Choices > Update Personalized List > add Table > Back to the Choices list > Filter the table (=problem) > Filter the language (en) > NEW > Table: Problem[problem]; Label: Pending change; Value: 108 > Submit > Save.
2. Modify the existing Create Normal Change AND Create Emergency Change UI actions to set the Problem state to "Pending change".
Solution: All > Problem > All > Open any problem record > right click on the grayad bar above > Configuration > UI Action > chose the table: problem [problem] > Look for the Name Create Normal Change > add current.state = '3'; to the script > Update > Look for the Name Create Emergency Change > add current.state = '3'; to the script > Update.
Please, mark my answer as Helpful if it help you.
Best regards.