Setup Guide - ProntoCase

Owned by Posimente
May 23, 2023
2 min read

Installing and configuring the package

Upon successful installation of ProntoCase, there are some settings that need to be configured in the ProntoCase Settings.

Field Mappings

Session ID Fields: This provides the Salesforce field ID of fields used in the session screen when a new session is created.

  • Session object: Go to setup and copy across the session object ID

  • Primary Client Field ID: Go to setup and copy across ID of the Session Primary Client field

  • Related Client Case Field ID: Go to setup and copy across Related Client Case field ID 

DSS Integration

Pronto Case connects to both a DEX staging environment and live production environment with system access. Staging environment access can be granted by DSS DEX for testing. For live system access, a DSS Data Exchange Access Request Form is required to be submitted.

DSS Login settings are as follows:

  • DSS Username: the username of the DSS DEX portal

  • DSS Password: The password of the DSS DEX portal account

  • Environment:

    • Pre-Production for connecting to staging

    • Production for connecting to live environment

  • Sync Settings:

    • Sync Frequency> options available; 10 mins, 30 mins, 1 hour

Once the connection to DSS has been set up, you can click on the below Sync buttons to activatebackground jobs in Salesforce. These jobs pull data from the DSS DEX environment.

  • Sync Organisation: Pulls the organisation details as setup in DSS

  • Sync Reference Data: Pulls the organisation specific reference data

  • Sync Organisation Outlets: Pulls the available organisation outlets from DSS

  • Sync Reference Assessment Data: Pulls the list of Assessment reference details used in scoring

  • Enable Sync Schedule: Starts the batch job to look for any records that are set to sync to DSS and begin syncing them.

NOTE: You should only click these buttons ONCE. 

If you are doing a Bulk Upload to DSS rather than an API Connection, the file format needs to be XML. 

Service Types and Dependant Fields in DSS

Each DSS Org may have unique Service Types that may have dependant fields such as "Money Business Course Delivered". In order to mirror the conditional nature of making the dependant field mandatory, you will need to create a Validation rule that is unique to the Org.

Below is the sample code.

Session Validation Rule

AND(ASPC__Service_Type__r.Name = 'Education and Skills training',ISBLANK(TEXT(ASPC__Money_Business_Course_Delivered__c )))

This means when Service Type: Education and Skills training is selected, you must also select the Money Business Course Delivered