Configuring Account Routing Policy in Salesforce


Enable Account Trigger Flag

  1. Go to Setup.
  2. Type Custom Metadata Type in the Quick Search bar and select it.
  3. Select Manage Records against Fullcast Setting.
  4. On the next window, select Edit on Fullcast Setting.
  5. Enable the checkbox on the Account Trigger flag. This enables the trigger on Account and Domain Related functionality on the Account Object.

Steps to Enable Account Territory Routing

  1. Go to Setup.
  2. Type Custom Metadata Type in the Quick Search bar and select it.
  3. Select Manage Records against Fullcast Policy Setting.
  4. On the next window, select Edit against the Enable Account TerritoryRouting record.
  5. Set Field Value to True to enable Territory-based routing for accounts.

Example of Fullcast Policy Setup :

The figure below is a sample of filled policy rules. The details differ from customer to customer based on their requirements.

Accounts Field Mapping

  1. Go to Setup.
  2. Type Custom Metadata Type in the Quick Search bar and select it.
  3. Select Manage Records against Fullcast Policy Setting.
  4. Click on New.
  5. Create a record as shown in the figure below:

  6. The field value of Label is fio_id which is a mandatory field for mapping.
  7. Fill in the Module Name field as RouteAccount.

Label, Field Value & Module Name

The module name should be RouteAccount for all the field mapping records in Custom Metadata (between Salesforce and Fullcast Application) to execute Territory-Based Routing for Accounts.

The Label section in Custom Metadata refers to the field name on Fullcast Application based on which hierarchy is created.

Field Value on Custom Metadata refers to fields on Account Object.

Where to find the fields in the Fullcast Application

  1. Click the Settings icon (gear) and select Entities & Fields.
  2. Pick Accounts from the Entity dropdown.

The Label Section in Custom Metadata is case-sensitive. The FieldValue is case-sensitive as well.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us