Scheduled Tasks are used to set tasks for execution at certain dates and times within Aptify. This could include sending out scheduled email reminders about a particular appointment or scheduling the expansion of scheduled transactions. At the time that the task is scheduled to occur, the Windows Scheduler triggers a Process Flow Run, which is then executed by the specified Application Server. Scheduled Task Form
Top Area
Name
The name of the Scheduled Task; all Scheduled Tasks must have unique names. Note that each Scheduled Task within Aptify corresponds to a scheduled task in the Windows Scheduler on the specified Application Server. The Windows Scheduler is available in the Windows Control Panel.
...
Fields within the Process Flow Input tab flow down automatically from a Process Flow when a Process Flow is added to the Process Flow field.
Process Flow Input Map
Input Property (read-only)
...
- Source Type = Static Value — Source is set to an alphanumeric string which indicates a permanent and static value to fulfill the input property. This string may include field tags, as long as the field name is enclosed in <% %>.
- Source Type = Entity Field — Source is set to a field on the Scheduled Tasks entity.
- Source Type = SQL Statement — Source is set to an SQL statement that extracts the data from the database.
- Source Type = GE Object — Source information is already populated with the Generic Entity (GE) object.
Note:
| Note |
|---|
Refer to the Process Pipeline Overview chapter in the Aptify 5.5 Process Pipeline Guide for information on how to configure Input Maps. |
Comments
The Comments field contains any additional details relevant to the input map.
...
- Once — The task is scheduled to run one time only, at the date and time specified.
Scheduled Task: Once
- Daily — The task is run every XX days, where XX is the frequency interval selected. For example, a task may be scheduled to run every 3 days.
Scheduled Task: Daily
- Weekly — The task is scheduled to run weekly, on the days specified.
...
- Monthly — The task is scheduled to run once per month, in the months specified, at the time specified. Numeric day of month may also be specified (for example, a task could be scheduled to run in May and August, on the 10th day of each month selected).
...
- Monthly Relative — The task is scheduled to run once per month, in the months specified. Time of day and day of month (such as the first Monday of the month) may be specified. The layout of the Schedule tab is similar to the tab's layout when Monthly is selected.
- Run when service starts — The Scheduled Task is run whenever the scheduling service is started.
Scheduled Task: Run When Service Starts
- Run when computer is idle — The scheduled task is run whenever the computer is idle for at least ten minutes. The layout of the Schedule tab is identical to the tab's layout when Run when service starts is selected.
...
When this option is selected, once the time in which the task should run has expired (the trameframe in which the scheduled task should no longer run is past), the task is deleted from the Windows Scheduler on the application server. Note that the Scheduled Tasks and associated Process Flow Runs records are not deleted in the Aptify database and the task can be re-activated at a later date by modifying the frequency information on the Scheduled Tasks record in Aptify.
| Anchor |
|---|
...
|
...
|
The Aptify trusted user account that runs the scheduled task on the Application Server and creates the Process Flow Runs record. This is the user that appears in the Scheduled Task's Run as: as field. The Job Account user must have a trusted user account in Aptify with the appropriate privileges to read and edit Scheduled Tasks records, read and create permissions for Process Flow Runs and its sub-type, and execute the process flow. You can specify the same user account that is running the Application Server's Aptify Asynchronous Processor or a different user account.
Note that the Job Account Name and Password are required when using the Windows Scheduler or Remote Scheduler service.
...
The password for the specified Job Account Name user. Note that this field is encrypted by default using the Generic Entity Encryption Key. By default, the sa user and members of the supplied Accounting, Administrators, and/or Users groups have access to this key.
Only users who have access to the key can enter a value in this field. Also, any user who will create a Scheduled Task (manually, via View Scheduling, or via Delayed Message Delivery) needs access to this key to successfully save the record and create the Windows Scheduled Task.
Depending on the security model that your organization has implemented, you may want to create a new key to encrypt this field and allow only designated users access to that key. This is the recommended approach but you should use the same key to encrypt this field that you use to encrypt the Default Job Account Password field in the Application Servers entity. See "About the Application Servers Form" on page 54.
See the "Field Level Encryption" section in the " Entity Security " chapter of the Aptify 5.5.1 Administration Guide for for information on using Field Level - Encryption. In the Aptify 5.5.1 Administration Guide, see the "Scheduling Messages for Future Delivery" section of the " Bulk Messaging Configuration " chapter for information on Delayed Message Delivery and the "Enabling View Scheduling" section of the " Administration Services " chapter for information on View Scheduling.