9.1 Create Strategy

This topic describes the information about Create Strategy.

The Create Strategy page facilitates user to create a strategy. While creating a strategy, user can associate multiple tasks to the strategy.

Table 9-1 Field Description: Create Strategy

Field Name Description
Basic Details This section is used to provide basic information of the strategy.
Code Indicates the unique identification code of the strategy.
Description Indicates the description of the strategy.
Effective Date Indicates the date from when the strategy is effective in the system.

Note: The date should be later than or equal to the business date. However, it must be earlier than or equal to the expiry date.

Expiry Date Indicates the date till when the strategy is effective in the system.

Note: The date should be later than or equal to the business date. However, it must be later than or equal to the effective date.

Task Details This section is used to add the tasks that user want to group together under the strategy, and set the task related configurations.
S. No Indicates the sequence number of performance of task.
Task Indicates the task type to be added to the strategy. User can search and select the required task code and description for the task type.
Mandatory Toggle to indicate whether it is mandatory to perform the current task before proceeding to perform the next task in sequence.
Wait Period (Days:Hours:Mins) Indicates the waiting time before prompting the next task to the collector or initiating the system task after this task is completed. For example, if user specify the wait period as 2 days, 6 hours, and 30 minutes, system will prompt the next task to the collector after the specified wait period on completion of this task.

Note: This field is enabled only for mandatory tasks.

Expiration (Days:Hours:Mins) Indicates the time after which the task will expire. If the task is not closed within the specified time, system will automatically expire the task and move to the next task in sequence.
Escalation Rule Select the rule condition. If the condition is met, the task status will be updated to Escalated.
Escalation Expression Detailed expression of the escalation rule.
Dependency Click Add to configure the dependent task that needs to be performed before initiating the current task. This means before the current task is initiated, the dependent task must be performed and should be in a particular status.

When user click Add, the Dependency section is displayed using which user can add the expression for the dependent task. User need to select the sequence number and dependent task and specify the status in which the dependent task should exist. The task list displays the sequence number and task type of all the previous tasks that you added in the table before the current task. The status list displays the status in which the task must exist. Once you specify the details, the generated expression is displayed in the field.

Note: This field is not applicable for the first task in sequence. User can add dependent task from second task onwards in the sequence.

Template Click advice to add correspondence template for the task.

Note: User can add multiple correspondence templates for a task. However, user need to mark one template as default.

This section consists of the following topic:

Parent topic: Strategy