We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.
We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Copy to New task to copy template and retain parent relationship
Mark_Wahlert
Customer Advanced IT Monkey ✭✭✭
Hi. We've had to remove the task Copy to New, as it creates orphan SRs with no RO and an unapproved template. It allows users to be lazy and bypass our catalog to fast track SRs by skipping approvals.
All it does is copy text into a draft SR template, with no RO link retained, leading to reporting identifying a growing list of orphan SRs.
Can the task be altered to copy the template and retain the RO? I know there are runbooks to copy CRs and RRs, can you trigger a runbook from a task?
9
Comments
You could create a task which sets a trigger, and have a Runbook monitoring that trigger when a work item is updated and run from there. From there you can locate similarly named objects and update them according to what RO/Template relationship they need.
Here is a great blog, from our very own @pzergeron how to do this: http://www.systemcentercentral.com/how-to-initiate-a-runbook-from-powershell-and-orchestrator-web-service-the-easy-way/
https://blogs.technet.microsoft.com/orchestrator/2012/05/15/cool-tool-new-command-line-utility-to-start-a-runbook/
Would love to see the default behavior of the SR "Copy to New" task be to (1) use the existing template of the source SR, or (2) prompt for template selection.