Integrations > IoT — Connected Field Service > IoT Setup for Administrators > Configuring IoT Events > Map to Apex > CreateCase
CreateCase
This event is used to create Case records automatically. The following table lists its various attributes.
Attributes
Values
Web service Class Name
CreateCase
REST Endpoint URI
*/services/apexrest/SVMXC/svmx/rest/IOTServiceIntf/CreateCase/2.0/
* The REST endpoint URI must be prefixed with http://<your salesforce organization url>. For example, if your Saleforce organization url is na17.salesforce.com, then CreateCase event can be invoked as http://na17.salesforce.com//services/apexrest/SVMXC/svmx/rest/IOTServiceIntf/CreateCase/2.0/.
The event request includes various fields as a part of the web service request payload. The mapping of these fields to the Case object fields are as follows.
Fields Received in Payload
Case Fields
Event > Subject
Subject
Description
Event > Description
Description
Event > AlertType
Description
Event > Property
Description
Event > EventTime
Description
Event > Priority
If value = 1 then Priority = "Low"
If value = 2 then Priority = "Medium"
If value = 3 then Priority = "High
Asset > ThingName
Description
Others > Installed Product record identified based on External Unique Key field-value pairs
SVMXC__Component__c = Installed product’s Id
SVMXC__Product__c = Installed product’s Product
AccountId = Installed product’s Company (Account)
ContactId = Installed product’s Contact
SVMXC__Site__c = Installed product’s Site
• The value of the Description field in the resulting Case record is set by concatenating the non-null values of Subject, Description, AlertType, Property, EventTime, and ThingName fields from the request payload in the mentioned order. In other words, Case.Description = Event.Subject + " " + Event. Description + " " + Event.AlertType + " "+ Event.Property + " " + Event.EventTime + " " + Asset.ThingName.
• The contents of the Others group in the request payload are considered only when Installed Product Lookup is configured in your IoT Setup. For each of the field-values pair sent in the Others group, the corresponding field is set in the resulting Case record (as per the mapping above) only if there is an exact field-name match in the External Unique Key section of the Installed Product Lookup configuration. Else, the received field-value pair is ignored.
Was this helpful?