Difference between revisions of "Trigger a Workflow from a Custom Browser Script"
From SmartWiki
Julia Decker (talk | contribs) |
Julia Decker (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | [[ | + | [[Workflow|Workflows]] can now be triggered based on a value in a [[Custom Fields|custom field]] on the object using [[Browser|browser]] script. The [[Workflow|workflow]] id is passed to the system from the script. |
'''Impact''': If it's a [[UTA]] [[Workflow|workflow]] you must create a status that will not be used by any other [[Workflow|workflow]] as the One-Status-One-Workflow restriction is still in effect. | '''Impact''': If it's a [[UTA]] [[Workflow|workflow]] you must create a status that will not be used by any other [[Workflow|workflow]] as the One-Status-One-Workflow restriction is still in effect. | ||
[[Category:Workflows]][[Category:Enhancements]][[Category:Custom Fields]] | [[Category:Workflows]][[Category:Enhancements]][[Category:Custom Fields]] | ||
Revision as of 12:16, 5 September 2008
Workflows can now be triggered based on a value in a custom field on the object using browser script. The workflow id is passed to the system from the script.
Impact: If it's a UTA workflow you must create a status that will not be used by any other workflow as the One-Status-One-Workflow restriction is still in effect.
