- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-15-2015 10:15 AM
Hi,
I currently have the following setup:
1. I have a change form that points toward both a parent and extended change table
2. I have enabled a multi-select field that allows users to select multiple users from a cmdb table
3. I have a workflow that creates a task for the Assigned To user upon approval. This change task must then be completed via the RFC. However, on the CH Task pop-up, there is a required field for selection of ONE CI.
What is best practice here, if a user has selected multiple CIs on the form but the task only allows them to select one CI? Should workflow dynamically create multiple tasks for each CI selected in the form? Only have the task show work against one CI regardless of what is chosen on the form?
Thanks in advance for any suggestions / advice!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-16-2015 07:39 AM
If the change request lists multiple CIs as the focus of the change, would an implementation TASK normally be created for each separate CI? Or would it be better to create an implementation TASK for ALL of the CIs?
Lesley, that's a good question and there is not right or wrong answer depending on the maturity level of your org and depth of control your process desires. I would start with creating One task for all CIs initially. Typically if the same task is being repeated on all CIs and assigned to the same person then it can be treated as an atomic task. If the change( task) needs to be implemented over a long period of time you can have a (process) policy to split it into multiple change requests.
Yes, the Change Request form has only one CI field but there is a related list called "Affected CIs" for many CIs. When you attach a CI to a change it is automatically added to the list and you also have the option to add more CI to the affected CI list.
If the change tasks for multiple CIs is being assigned to different assignees ... then it makes sense to create multiple tasks in the workflow.
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-21-2015 11:25 AM
Hi, Venkatesh,
Have you reported on the Affected CIs before? What's the best way to show a report of Affected CIs that were chosen, by change #?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-21-2015 02:24 PM
Hi Lesley,
You can create a report on task_ci table which contains the Affected CIs.
You can group affected CI's by change in the report.
-Venkatesh