Using the Scheduling tab on the Execution Options, you can schedule one or more projects to run either at a specified time or as soon as possible after another execution. Note that the date and time used are based on the time zone of the target server in all cases.
To start the execution at a specific time, select the Execution Type, ‘At Specific Time’, then enter the date and time in the Earliest Execution Start Date & Time fields.
To prevent the execution from starting after a certain date/time, enter a date and time in the field ‘Latest Execution Start Date & Time’.
To force the execution to wait until another execution has completed, check the ‘Depends On Previous Execution Of’ option, then select the name of the project from the list of existing loaded executions.
Note that the dependent execution will not start unless the current time is also greater than the Earliest Execution Start Date/Time and earlier than the Latest Execution Start Date/Time if specified.
If two executions are dependent on the completion of the same previous execution, then the dependent execution with the highest priority value is executed first.
If you want the execution to run repeatedly, select the frequency (daily, weekly, monthly, hourly, 30-minute, 15-minute, 10-minute or 5-minute intervals) from the Repeat field. In this case, the execution is set back to scheduled after it has completed and the new scheduled date/time is based on the repeat frequency.
When you click on the Schedule Execution button, a summary window is presented like this so you can view and check all the configuration settings for this execution. Select Continue to continue with the scheduling or Cancel to revert back and modify any of the configuration settings.
When confirming the execution, you may be presented with a message indicating that user input may be needed during execution. This will be the case if:
• Business Hours restriction is activated on one or more of the form mappings and the Business Hours Migration Restriction action on execution settings (validation tab) is set to ‘Prompt’
• The Connection Error: Action if the 'Retry Count Exceeded’ option is set to 'Prompt'
While waiting for a user prompt, the execution is paused and if further executions are pending, they will also be delayed until the user input is received and the current execution has completed.
Scheduling the execution automatically starts the loading process which performs the initial validation and enters the project into the Loaded Execution List with a status of Scheduled.
If you want to execute a project immediately, select the default scheduling options (Execute As Soon As Possible), then click on the Schedule Execution button which then loads the project into the Loaded Execution List with a status of Executing.
If you want to add a project to the Execution List but you're not ready to define the scheduled start time or dependencies then use the Load Execution button instead.
Comments
0 comments
Please sign in to leave a comment.