Difference between revisions of "Team Data Policies"

From LongJump Support Wiki
imported>Aeric
imported>Aeric
Line 2: Line 2:


A Data Policy can be set up to run when a Team is added, updated, or deleted.
A Data Policy can be set up to run when a Team is added, updated, or deleted.
__TOC__
===Policy Settings===
:;Name: The name given to the data policy, for later reference.
:;Name: The name given to the data policy, for later reference.
:;Enabled: Whether or not the data policy is currently enabled.
:;Enabled: Whether or not the data policy is currently enabled.
Line 37: Line 39:


====Calendar Based Data Policies====
====Calendar Based Data Policies====
===Date Criteria===
===Field Criteria===


====Parameters====
====Parameters====

Revision as of 23:11, 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 -
  • In an Action Based Data Policy, the Activation Sequence determines which actions are available
Actions Description Activation Sequence

Before Triggering Actions (Pre)

Activation Sequence

After Triggering Actions (Post)

Logout Logout Checkmark.gif
Login Login Checkmark.gif
Proxy Login Proxy Login as this User Checkmark.gif
On View On View - when the record is viewed Checkmark.gif
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