A scheduled action rule is similar to a custom action rule. You upload custom Java or JavaScript files to use for the rule action. The difference is that when you define these rules in the user interface, you have the option to specify when and how often the action is executed.
For example, your system might need a custom rule requiring, when the qualifiers are met, a task is created every 15 days to remind the user to do something, for a period of 90 days. To accomplish this requirement, a custom Java class might be uploaded to TeamConnect, and you then select this class file in the scheduled action rule. However, the actual number of days between tasks and the number of times that a task must be created are specified on the Action tab of the scheduled action rule.
When a scheduled action rule is triggered, you may view information about actions pending in the Scheduled Actions Monitor, provided that you have the rights to this tool. If necessary, you may also delete (or cancel) pending actions using the Monitor screen.
If the qualifying conditions for a scheduled action rule are true, and the rule is triggered, it will continue to run as scheduled even if the qualifying conditions subsequently become false during the schedule. The qualifiers are only checked the first time the scheduled action rule is invoked.
For more details about the Scheduled Actions Monitor and scheduled action rules, see:
•Creating Automated Qualifiers and Actions
•Defining Settings for Scheduled Action Rules
By default, duplicate contact checking is not done when custom Java code has been written to create or update contacts. See the ContactService.readDuplicateContacts() method in the API Javadocs to use duplicate contact checking functionality.
