Team Data Policies
From LongJump Support Wiki
Revision as of 23:23, 9 July 2012 by imported>Aeric (→Date Criteria)
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 - Execute the Data Policy before the Team change occurs.
- After Triggering Actions - Execute the Data Policy after the Team change occurs.
- Learn more: Activation Sequence
- Triggering Action
- Add - Execute the Data Policy when a new Team is created.
- Update - Execute the Data Policy when an existing Team is updated.
- Delete - Execute the Data Policy when an existing Team is deleted.
- Run As
- Logged In User- Run the data policy as yourself--the user who is currently logged in and creating the data policy.
- Specific User- Run the data policy as some specified user, who has the particular set of privileges needed to perform the actions associated with the Data Policy.
Calendar Based Data Policies
Date Criteria
Specify date ranges for the Team Date Created and Date Modified fields. The Data Policy will only be in effect when the selected fields are within the specified date ranges.
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