Changes

Cascading Status Changes

34 bytes added, 15:04, 19 May 2009

no edit summary

A change in '''status''' at one level can update the '''status''' at the levels beneath it.

For example:==Example 1==From a L1, L2, L3Level 1, 2 or 3 Transaction status Status – you can setup the following:

* Type Filter – The L2, L3, Transaction type that you’re going to filter on to obtain items to update status

* Status Filter – Once it finds the records that match the type, now it filters on the status, and any of those matches…

* Set Status To - … xxx ''it will change the status to this status''

[[Image:Cascadetrigger.png]]

For instance, in a [[Universal Tracking Application]] if you have a Template named ''ThisTemplate'', and there are many activities on that ticket of different statuses. We could setup the trigger set all L2s to Complete status, regardless of what status they’re on.

==Example 2==In a [[Universal Tracking Application]] if you have a Level 1 Template named ''ThisTemplate'', and there are many activities on that ticket of different statuses. You can set up the trigger to set '''all''' Level 2s to Complete status, regardless of what status they’re on: * Add New Level 2 Trigger * Type To: All * Status Filter: All * Set Status To: Complete

[[Category:Workflows]][[Category:Universal Tracking Application]]

• ← Older edit
• Newer edit →

0

edits