Team Data Policies
From LongJump Support Wiki
Revision as of 23:36, 9 July 2012 by imported>Aeric (→Field 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
- Activation Date
- The date for the first execution of the Data Policy.
- Activation Time
- The time of the first execution.
- Repeating Frequency
- How often the Data Policy repeats: Never, Daily, Weekly, Monthly, or Yearly.
- Run As
- Choose the user who will be running the Data Policy, when it executes, where the users' privileges determine what the Data Policy can do. (The default is you--the logged in user who is creating the Data Policy.)
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
Specify fields and values for Data Policy. The Data Policy will only be in effect when all specified field/value comparisons are successful.
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