Calendar Based Data Policies

From LongJump Support Wiki
Revision as of 15:51, 20 April 2011 by imported>Alice (Removed SOAP reference)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Calendar-Based Data Policies

Calendar based data policy actions are triggered on a schedule, defined by the following parameters:

  • Start Date and Time
  • Non Repeating or Repeating (Daily, Weekly, Monthly, Yearly)
  • End Date or Never-ending

Thumbsup.gif

Tip: A job will start at the time you specify. But the time it takes to complete depends on the system load, so it's a good idea to schedule actions well in advance, to ensure that it completes at the desired time.

Examples of calendar-based policies
  • Drip Campaigns use Calendar-based data policies. These policies detect values and conditions of the data fields and based on them, execute a combination of actions including: sending an email, assigning a task, updating the record content, delivering a Send Outbound message to an external system, or running Java code.
  • In a front-desk reservation system, set the criteria to verify that the check-in date must be in the future (after Today) and that the check-out date follows the check-in date
  • In a doggy daycare system, check that the pet owner's account has enough pre-paid credits for that week's care

Learn more: Build a Calendar Based Data Policy