Multiple conditions constructed within the Advanced Statement Builder can be used to define the criteria matching rules that will track repair status changes for specific entities, identifying those scenarios where a Generic Case or CRM Case should be triggered. Alternatively, for more complex expressions, these can be defined through a SQL Stored Procedure, which is then mapped to the case trigger rule instance.
The procedure to add entity criteria to a case trigger rule is as follows:
- Prerequisite procedural steps are covered separately in the topic To define a case trigger rule for a repair status code. Refer to these before proceeding to step 2.
- With the Case Configurations grid in current focus, highlight a case trigger rule against which entity criteria is to be applied.
- Click on Add Criteria. The Add Criteria Step 1 window is displayed.
- Use the Description field to add contextual notes that will explain the derivation and purpose of the entity criteria.
- Choose an Effective from date for this entity criteria i.e. the date on which it came into effect
1.
- Choose an Effective to date if the entity criteria is to be reviewed on a specific date or to capture a change of circumstances; a blank field means the criteria will be continually valid.
- Where a bespoke SQL stored procedure has been created to execute potentially complex entity criteria rules, activate the Use advanced query tick box provided and enter the Stored procedure name into the adjacent field 2. Click on Confirm and proceed to step 10.
- Alternatively, click on Next to launch the Statement Builder, ready to compile the logical expressions using the Add Function and Add Field options. This requisite step mirrors functionality covered separately in the topic Understanding the advanced statement builder.
- Click on Save. The specified Criteria is displayed in the corresponding summary grid, including the compiled statement algorithm (Criteria column).
- Repeat steps 3 through 9 to add further criteria to the same case trigger rule.
Note
1 The Effective from date defaults to the current system date and cannot be left blank.
2 More complex algorithms can be captured within a SQL stored procedure and steer the derivation of case trigger rules in this way. Where a stored procedure has been linked, an expression statement cannot also be employed, and vice versa.
See related topics...
To define a case trigger rule for a repair status code
To remove entity criteria from a case trigger rule
Understanding the advanced statement builder
