Difference between revisions of "Team Data Policies"
From LongJump Support Wiki
imported>Aeric |
imported>Aeric |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
# Click '''[Save]''' | # Click '''[Save]''' | ||
# Click '''[Add Action]''' to specify what action to execute when the policy fires: | # Click '''[Add Action]''' to specify what action to execute when the policy fires: | ||
#* '''Invoke Method -''' Select a Java [[Class]] and a method within | #* '''Invoke Method -''' Select a Java [[Class]] and a method within it | ||
#* '''Execute Java Code -''' | #* '''Execute Java Code -''' Provide the Java code to be executed | ||
# When multiple actions have been defined for a Team Data Policy, click '''[Reorder Action]''' to determine the order in which they execute. | # When multiple actions have been defined for a Team Data Policy, click '''[Reorder Action]''' to determine the order in which they execute. | ||
# When multiple policies have been defined for a Team, click '''[Manage Execution Order]''' to determine the order in which they are processed. | # When multiple policies have been defined for a Team, click '''[Manage Execution Order]''' to determine the order in which they are processed. | ||
| Line 46: | Line 46: | ||
:;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.) | :;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.) | ||
===Locked Package Options=== | ===Locked Package Options=== | ||
This section only appears for users who have the ability to create and distributed [[Packages]] that contain an Application that others can install. | This section only appears for users who have the ability to create and distributed [[Packages]] that contain an Application that others can install. | ||
:;Allow Installer to Disable: When the Data Policy is included in an externally-published [[Package]], this option specifies whether the package installer | :;Allow Installer to Disable: When the Data Policy is included in an externally-published [[Package]], this option specifies whether the package installer can disable it. | ||
==Programming Parameters== | ==Programming Parameters== | ||
| Line 68: | Line 62: | ||
| Item2 || <tt>item2</tt> | | Item2 || <tt>item2</tt> | ||
|} | |} | ||
:''Learn more:'' [[Data Policies#Writing Java Code for a Data Policy|Writing Java Code for a Data Policy]] | |||
Latest revision as of 00:09, 10 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.
Creating or Modifying a Team Data Policy
- Go to Settings > Global Resources > System Objects > Teams
- Select an existing Data Policy or click [New Policy]
- Fill in the information below
- Click [Save]
- Click [Add Action] to specify what action to execute when the policy fires:
- Invoke Method - Select a Java Class and a method within it
- Execute Java Code - Provide the Java code to be executed
- When multiple actions have been defined for a Team Data Policy, click [Reorder Action] to determine the order in which they execute.
- When multiple policies have been defined for a Team, click [Manage Execution Order] to determine the order in which they are processed.
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.)
Locked Package Options
This section only appears for users who have the ability to create and distributed Packages that contain an Application that others can install.
- Allow Installer to Disable
- When the Data Policy is included in an externally-published Package, this option specifies whether the package installer can disable it.
Programming 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
- Learn more: Writing Java Code for a Data Policy