Custom SQL Step gives the option for users with the ability to write SQL to write custom SQL statements that will run during the matching rules. It is there to service the fringe matching rules that may not be possible when using the other two step types.
Step Name – A brief description of the purpose of the matching step. | |
|
Check SQL Button – Will check your SQL to ensure that the syntax and field/table names are correct. A notification will show at the bottom of the SQL Editor to show whether there are errors or not. |
|
SQL Editor – The SQL that will run. |
Final Step
This step type is mandatory and ensures that a decision is made towards activity that may still be unmatched to an episode. There are two options:
- Leave as Unmatched – the activity will still be loaded and bought through into CostPro, however the cost will not be on an episode. There is an unmatched activity report that users can use to audit this data.
- Create Own Episode – This option is the same as the “Make Own Episode” step type, however there is no ability to add additional criteria.
See the other matching rule steps:
Post your comment on this topic.