Difference between revisions of "Cascading Status Changes"

From SmartWiki
Jump to: navigation, search
Line 1: Line 1:
 
A change in '''status''' at one level can update the '''status''' at the levels beneath it.
 
A change in '''status''' at one level can update the '''status''' at the levels beneath it.
  
For example:
+
==Example 1==
From a L1, L2, L3, Transaction status – you can setup the following:
+
From a Level 1, 2 or 3 Transaction 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
 
* 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…
 
* 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 - it will change the status to this status
+
* Set Status To - xxx ''it will change the status to this status''
  
 
[[Image:Cascadetrigger.png]]
 
[[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==
Add New Level 2 Trigger
+
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:
Type To: All
+
* Add New Level 2 Trigger
Status Filter: All
+
* Type To: All
Set Status To: Complete
+
* Status Filter: All
 +
* Set Status To: Complete
  
  
  
 
[[Category:Workflows]][[Category:Universal Tracking Application]]
 
[[Category:Workflows]][[Category:Universal Tracking Application]]

Revision as of 11:04, 19 May 2009

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

Example 1

From a Level 1, 2 or 3 Transaction 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

Cascadetrigger.png


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