Skip to main content

Category Policies

Category policies are in many ways the heart of a standard solution. They classify and define downstream actions, such as reviews, required forms, processing steps, and notifications, for each type of request—everything after request intake, essentially. For example, you may have a “Software Purchase Request” policy that includes an advanced reviews policy because costs are often beyond a set threshold, and required questionnaires that help establish business justification for the purchase. Each of these elements is configured for the policy here.

Add and Configure a Policy

To add a category policy, follow the steps below:

  1. In the Policies table, scroll to the bottom of the table and select the Create Row button, preference-table-create-row.png. The Create Row window displays.

  2. Configure by entering values for the relevant fields:

    Remember, you can select the insert field button, insert_field.png, to add dynamic values.

    1. Name (Required) - Enter a descriptive name for the policy.

    2. Description - Enter a description of the policy.

    3. Match Conditions - Define the conditions that determine when this policy applies. For example, you may have a schema field that defines several experience types, and this condition checks for when Experience_Type = “Purchase Request” for the purchase request policy.

    4. Priority (Higher goes first) - Set the order in which Tonkean matches to a policy if conditions are met for multiple policies.

    5. Request Title - Optionally, overwrite the request title with schema fields (or manually). By default, the request title is the request ID. The request title is displayed prominently on the Homepage.

    6. Reviews Policy - Select which review policies apply to the category policy.

    7. Required Questionnaires - Select which questionnaires are required for the category policy.

    8. Processing Steps - Round 1 - 4 - Select which processing steps to add to the category policy. Steps placed in the same round run in parallel.

    9. Request is NOT Cancelable - Define the conditions under which the request can no longer be canceled. Once these conditions are met, the cancel button is removed from the interface.

  3. When finished, select Create. The category policy is created.

In this section: