Source Opcode Mapping for Network Operations

USE CASE

CASE Users want the ability to add a source opcode to an operation which their service location does not own and have that code used anytime they add this operation to a case within their service location so that those operations added will be able to export to my business system without error. Previously, users could do this per operation on each estimate within CASE as needed. Now, this can be handled within Builder to reflect for an operation every single time automatically.

STEPS TO COMPLETE WITHIN BUILDER

1. Login to Builder

2. Select the entity which represents the primary service location, i.e. the entity where all of the dealer defined operations are housed - 9999 for example as shown below. 

3.  From there, select "Customize Operations" shown below. 

4. Network operations should appear here along with dealer defined operations. Network operations will reflect as whatever entity they are built within (VLV, MCK, DCV, for example) and the dealer defined operations will reflect as the primary location's entity.

Note: If you do NOT see any network operation entities (VLV, MCK, DCV, for example) please escalate to Decisiv Support and request your service location's main entity to be added to the correct entity group.

5. Search the network operation you'd like to apply your source opcode to - Quick Care Plus Inspection for example - and apply the dealer defined source opcode as needed. Be sure to select the check mark after completing this so your adjustment is saved.

Moving forward, whenever the Quick Care Plus Inspection is selected within CASE, users will see their source opcode in place on the "Edit Operation" screen and this opcode will export over to the business system as needed.