- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2014 06:45 PM
Tasks already created by the workflow will not be impacted by cancelling the workflow.
You will have to do that explicitly.
As Doug mentioned - a BR will be the best option. This will be an easy to maintain solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2014 07:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2014 08:08 AM
g_form only works on client scripts and br's run on the server.. so you can't use g_form, instead use current.number.
personally i would do it as an after rule.. so it applies AFTER the change is closed not before....
also lets back up a second and think about something else.. currently if they close a change... what happens to the change tasks?? if it is like ours was the tasks will stay open even though the change is closed <not just cancelled but ANY close>
what we have done instead of cancelling the tasks is to set in a client script that when you set the change to closed or canceled checks for kids and if it finds any prompts the user that they have to close all the children before closing the change and aborts the submit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2014 09:23 AM
Not real sure how to use current.number in this instance. Example?
As well, we require, during cancel, that all related records are auto-cancelled. If we start prompting the user to close child records, it will not save them any time, and cause frustration. But my choice would be to do exactly that, force them to close then proceed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2014 09:50 AM
Sure where you have g_form.getValue('number')
put in
current.number
that should take care of it the rest of the script should work fine on any server side script <BR's etc> current refers to the record that called the script... so in this case current is going to be your change record... and you can use current.anyfield to get to a field.. in this case current.number will return the change request number... current.state would return the state etc.
