Difference between revisions of "Team Data Policies"
From LongJump Support Wiki
imported>Aeric |
imported>Aeric |
||
Line 16: | Line 16: | ||
:: '''Before Triggering Actions -''' | :: '''Before Triggering Actions -''' | ||
:: '''After Triggering Actions -''' | :: '''After Triggering Actions -''' | ||
::''Learn more: [[Data_Policy#About_Actions|Activation Sequence]]'' | ::''Learn more: [[Data_Policy#About_Actions|Activation Sequence]]'' | ||
Revision as of 23:15, 9 July 2012
Settings > Global Resources > System Objects > Teams
A Data Policy can be set up to run when a Team is added, updated, or deleted.
Policy Settings
- Name
- The name given to the data policy, for later reference.
- Enabled
- Whether or not the data policy is currently enabled.
- Activation Trigger
- Action Based - Execute the data policy when a specific event occurs
- Calendar Based - Execute the data policy on a regular schedule
- Learn more: Triggering Criteria
Action Based Data Policies
- Activation Sequence
- Before Triggering Actions -
- After Triggering Actions -
- Learn more: Activation Sequence
Calendar Based Data Policies
Date Criteria
Field Criteria
Parameters
- The following Team parameters are available to Java code that is executing as part of the Data Policy:
Field Parameter Name Item1 item1 Item2 item2
- Actions available