Welcome > Process Designer module > Configure the properties of a process > Configure the general properties of a process

Configure the general properties of a process

  1. Open the process map to configure the properties.
  2. On the Properties bar, click Settings.
  3. Enter a Name and Description for the process.
  4. To change the type of map, on the Type list, select one of the options:

    • To change a process map to a case map, select Case Definition.

    • To change a process map to a Case Fragment map, select Case Fragment and consume the case map in the Associated Case box.

    Note By default, the map type is displayed based on the type of map you selected. You can change an existing Process map to a Case map, and Case Fragment map, but not vice versa. All the settings configured on the current map are automatically applied for the new map . When you change a Process map to a Case map, all the associated process variables are converted to case variables.
  5. Consume a process to associate with case in the Associated Case box.
    Note You can associate several business process maps with the same case, provided you first change a process to a Case Fragment type.

    When a process map is associated with a case map, the case milestones, case variables, and case roles become available to all associated processes. The Associated Case property is only available for a Case Fragment map.

  6. Select a Category to stores process maps. By default, a new map is placed under your working category. Exporting a process map also exports the map category. You can also place the process in a different category. See Create a category.
  7. Enter the Priority for the process.
    Note Priority defines the level of importance for the process. A job with priority level 1 indicates that the job is of the highest priority and level 100 indicates the lowest priority.
  8. Use Work Type as the primary method of managing workflow in a business process.
    Note Work types are custom task lists used by operational staff to display, manage, and execute their work tasks. To assign a work type to a process, you must have read access to work type and access to the category of the work type. See Work types.
  9. To use skins, click Yes for Support Skins.
    Note Using skins, you can have many views of the same process, typically for different products and customers. See Manage skins.
  10. To associate a Create New Job form with a process, in the Job Creation Form box, consume the Create New Job form or specify a static value.
  11. By default, the reporting tag is not associated with the process. To associate a reporting tag with a process, on the Reporting Tag list, select a tag.

    The associated reporting tag is applied for all versions of the process. If a reporting tag which is in use in a process is removed from the system settings, the system displays a warning when the process map is opened.

  12. Expected Duration is how long a process is expected to take. To define an expected duration, use one of the following options:

    • Time: Enter values in Days, Hours, Minutes and/or Seconds.

    • Variable: Consume a Date variable.

    • Milestone: Consume a milestone.

  13. Specify the overall Expected Cost of performing the job.
  14. Specify the Budget of the process using a static or dynamic value.
    Note Budget determines the amount of money allocated to a process (mainly case fragments). A budget helps managers track and monitor key business processes to determine whether the process is under or over budget. Budget and Expected Cost are different. For example, a typical Appeals case process is made up of several case fragments such as Register an Appeal, Medical Examination, or Convene Court Hearing. A budget is usually associated with the overall case fragments and is the summation of the expected cost of each case fragment.
  15. Define the Service Level Agreement. See Define the Service Level Agreement.

Define the Service Level Agreement

Service Level Agreement (SLA) is the visual representation of a threshold status or job state on a job list or work queue. Threshold statuses indicate if the job is within or has exceeded the set target duration.

TotalAgility supports a maximum of five statuses. Three statuses—Red, Amber and Green—are available by default. You can also include Black and Purple. See Configure the work process settings.

Green is the first and the default status. If additional SLA thresholds are not set, the status of the job remains Green until the current time exceeds the expected duration, and then the status changes to the last status, or Red.

For an SLA Status indicator to work effectively, define the thresholds in a decreasing order. For example, the Amber threshold should always be more than the Red threshold.

You can define the time relative to the expected duration when the job status should change state, such as from Green to Amber or to Red.

You can configure the state to change before the expected duration is achieved or after the expected duration is met (Post). The default is pre-expected duration.

  1. Enter the SLA Threshold for the status in Days, Hours, Minutes and/or Seconds.
  2. To configure the state to change after meeting the expected duration, select the Post check box.
    Note By default, the state changes before reaching the expected duration.

Configure the following settings for the process:

  1. Amber threshold = 1 hour

  2. Red threshold = 30 minutes

  3. Expected Duration = 2 hours

If the job is started at 12:00:00 AM, the expected finish time is 2:00:00 PM.

  • From 12:00:00 AM to 1:00:00 PM, the SLA status for the job on the work queue is Green. This means that the job is pending and the current time is outside the Amber threshold.

  • When the time is 1:00:01 PM (less than 1 hour from the expected finish time), the SLA status turns Amber. This means that the job is still pending and due to be completed; the current time is within the defined Amber threshold.

  • When the time is 1:30:01 PM (less than 30 minutes from the expected finish time) the SLA status turns Red. This means that the job is overdue. If the current time is within the defined Red threshold or exceeds the expected duration, the SLA status of the job remains Red.