How caserules Works

The caserules area works similarly to projectrules. Here, you declare:

• Tasks that will be created from which Project and Case combinations

• Data that will be populated on those Tasks

For example:

          "casemap": {
         "contract_tech_task": "company.custentity_nxc_contract_tech",
         "case_skill": "custevent_nxc_case_skill"
      },
      "caserules": [{
            "//": "Contract 1 Case 1 Tasks",
            "project": [120,121,122,123],
            "case": 106,
            "offset": 0,
            "task": {
               "type": 101,
               "assigned": "${supportcase.contract_tech_task}",
               "custevent_nx_task_skill": "${supportcase.case_skill}"
            },
            "total": 1
         } 

        

The caserules area has an array of objects. Each object has the following properties:

• project

• case

• task

These Project and Case properties work together to capture the Project and Case Types. Both the Case Type and Project Type must match for a caserules object to apply.

In the example above, only projects of type [120,121,122,123] and case types of 106 will be processed.

The task property is an object of fields that will be set on the task after it's created. In the following example:

• Task type will be set to 101

• Assigned field will be set to ${supportcase.contract_tech_task}

  This is a field on the project that we can determine from the casemap, "contract_tech_task": "company.custentity_nxc_contract_tech"

• custevent_nx_task_skill will be set to ${supportcase.case_skill}

  This is also defined in the casemap, "case_skill": "custevent_nxc_case_skill"

          "task": {
               "type": 101,
               "assigned": "${supportcase.contract_tech_task}",
               "custevent_nx_task_skill": "${supportcase.case_skill}"
            }, 

        

Related Topics

• Program Feature Configuration

General Notices