Contents
Tenant Code Rules
Updated
by Mike Nolan
Purpose
This article will help you understand how to best configure the Tenant Code Rules within DRS and why we might use them.
Tenant Codes Rules can be configured to monitor the inbound jobs where they are raised against locations which have Tenant Codes configured.
Tenant Codes (could also be known as Warning Flags) are commonly used to identify customers which have previously been identified to require more than one operative to attend, or other non-default scheduling requirements.
Using this function, we can direct the scheduling of the job away from your standard scheduling rules and onto something more appropriate, responding to the needs or your customers.
How does it work?
The Tenant Code Rules use the value mapped to the Tenant Code Business Data on the Customer record to re-direct the Job Template assignment from the default job template to one that is alternatively defined.
Once a request for a new booking has been received, DRS will confirm the default assigned Job Template and whether there are any Tenant Codes active against the Customer record. If there is, and a matching Job Template translation is found in the Tenant Code configuration, the booking will be assigned the translated Job Template prior to an appointment being offered.
Customer Record
Below shows where the Tenant Code resides on a Customer record. This customer has a Tenant_Code value of VIP (Visit in Pairs)
How do we populate the Tenant Code?
The Tenant code on the customer can be populated in a few different ways
Automatically managed through Integration
Customer records can be updated through the API integration when creating new scheduling records. The integrating system can pass a value through in the relevant API calls for DRS to manage all of the Customer details, including the Tenant Code Business Data.
Manually managed through the UI
The Tenant Code business data can be manually managed through the DRS UI. By searching for the relevant Customer record and clicking Edit
The Tenant Code value can be manually updated and managed.
Once the record is updated, click Save for it to become active.
Bulk Update
Using the Import/Export routine, the Customer records can be updated to display any changes, including adding and removing a Tenant Code.
Tenant Code Rules Configuration
DRS > Configuration > Tenant Code Rules
New Tenant code rules can be created as well as copied, viewed and deleted by using the relevant buttons across the top of the page.
When creating new Tenant code rules:
You identify the specific Job Template and what that template will map to as shown below:
By clicking the + Add New Line button you can add multiple tenant warnings within the same window and delete them using the corresponding Delete button
The value you enter within the Tenant Code must be an Exact Match to the values held against the Tenant Code value in the Customer object.
NOTE: Because Tenant Code Rules are free text, multiple tenant code rules can be configured for the same combination of Source Job Template and Target Job Template. In the case of conflicting Tenant Code Rules, the first matching Tenant Code Rule will be used.
What do we see?
Once a Tenant Code rule has been correctly configured, any recieved job associated with that Rule, Customer and Job Template will be mapped as configured.
In this example, the job was received for the Job Template of JOINERY, with a Customer record who has the Tenant Code of VIP configured.
The resulting created Job has now been assigned the Job Template, JOINERY PAIR.
