I had a similar requirement, and used an Advanced Interface Form (this isn't necessarily relevant but it explains why I would have one Filter versus several that you will need.)
What I did was to have my AIF decide what the Task Group Template was based on criteria selected on the form in SRM. If you are using the normal type of SRM form, you won't be able to make your own active links and such so instead you'll have to move this portion to the Work Order itself, perhaps basing which Task Group Template you use on what is populated in one or more of the custom fields on the Details tab. Anyway, all you really need is some way to get the Task Group Template's Instance ID. >From there, you need a Filter that executes on Submit. Then you create the >following If Actions: 1) Push Fields to TMS:ParentApplicationTemplateBuilder mapping basically everything that looks like it fits, with the important ones being zTmpInternalCommand being set to "CREATECHILD", RootRequestFormName being set to WOI:WorkOrder or $SCHEMA$, RootRequestName being $Work Order ID$, RootRequestInstanceID to $InstanceId$, and the Parent Template InstanceId to your Task Group Template's Instance ID. 2) Set Fields on the Current Transaction, setting z1D Char01 with "$PROCESS$ Application-Query-Delete-Entry "TMS:Flow" 'RootRequestInstanceID' = "$InstanceId$" AND 'ParentID' = "$InstanceId$" AND 'Sequence Mode' = "Yes" AND 'Status' = "Pending" 3) Push Fields to TMS:FlowBuilder setting the fields that match, plus Parent Name to $RootRequestName(TMS)$, ParentID to $InstanceId$, Parent Type to "Root Request", zTmpInternalCommand to "CREATE", RootRequestFormName to $SCHEMA$, RootRequestName to $RootRequestName(TMS)$, and RootRequestInstanceID to $InstanceId$ 4) Set fields on the Current Transaction of CreatedfromParentTemplate to "Yes" Originally, I did it slightly differently, by setting up the Task Group Template to be attached to the Work Order instead. However, the users don't like Task Group Templates because it makes it harder to use Tasks so this method instead takes the Task Templates and attaches them directly to the Work Order instead. Thanks, Shawn Pierson Remedy Developer | Southern Union From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Gmail Sent: Saturday, February 11, 2012 9:04 AM To: arslist@ARSLIST.ORG Subject: SRM & Tasks ** I have an SRD that has 3 questions with several options. Depending on the answer from the user to those three questions, I determine the tasks needed and using a variable on the PDT, the process determines which Work Order template to attach. This is working fine. However, the number of different tasks along with the possibility of answers, bring the total number of WO templates to be created to 28 different templates with respective embedded tasks that represent the user's answers. As you can see this requires a great deal of maintenance. My alternative approach is to create the tasks on the fly once the SRD is submitted and the WO has already been created. So I was wondering if anyone had to do that or not. Any ideas or thoughts would be highly appreciated. Environment details ARS 7.5.04 ITSM 7.6.00 SRM 7.6.02 Win 2003 x64 Oracle 10.2.2 Thanks, Moe. _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ Private and confidential as detailed here: http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the link, please e-mail sender. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
