Creating varying numbers of SR from Change

[gabraham]

Hi,

Struggling to get a process that works for this.

I have an intelligent capture field with a dynamic checkbox linked to a simple list to allow for a number of options to be selected from a list of servers. This then creates a change request.

I am looking to then create a service request for each server selected in the intelligent capture. The number of calls created and the servers this will relate to will vary each time a change is created using this process.

Is there a simple way of achieving this?

[Victor]

When the CR is created, the answer to that dynamic checkbox will be in the form of a string with all the selected options separated by commas. So, if the user selected Server 2, 5, and 9 from the dynamic list, the stored answer would look like: Server 2, Server 5, Server 9. With this setup, in the CR workflow, you can have a chain of decision nodes to check if the answer string contains a specific server. For example, if the answer contains 'Server 2', then you path the workflow to create an SR for that answer. You replicate this decision (hence the decision chain) for all possible selected answers. The downside is that you will need a decision for each possible answer, which might not always be feasible, especially with dynamic values. Hope this makes sense.

[gabraham]

Thanks Victor, suspected that would be the case.
with 27 servers and any combination of them requiring a separate job to be logged from the change thats going to get complicated quite quickly, i'll have a look at an alternative solution.

 

[Victor]

1 hour ago, gabraham said:

with 27 servers and any combination of them requiring a separate job to be logged from the change thats going to get complicated quite quickly

If you only need as you said a separate request for each server selected then 9 13 chained decisions should do the job... But you know better if there are other aspects or factors that complicates this (simple) logic...