Activity
The Activity object of the target system is intended to store details of users’ field activities, such as visits, events, and meetings.
| It is possible to work with several Activity objects that must be set in CT Mobile Control Panel: Calendar / CT Mobile Control Panel 2.0: Activities. |
| The availability of functionality depends on the platform of the mobile device. For more information, refer to CT Mobile OS Comparison. |
Object API name: depends on the target-system data model
In case of their lack, the following fields should be created on the object:
| Field | API Name | Type | Description | ||
|---|---|---|---|---|---|
Application Ids |
ApplicationIds__c |
Lookup(Application) / Text(255) / Long Text Area(131072)
|
For Remote Detailing, create a field that stores CLM presentations IDs:
The field to store Application IDs should have the same API name on any Activity object for the Remote Detailing session. You can specify a process, for example, to create a trigger to autocomplete this field with values from the pre-configured picklist. |
||
Geolocation |
Geolocation__c |
Geolocation |
Create a field to store the geolocation data on the place of editing (opening) activity |
||
Identifier |
MobileId__c |
Text(255) |
Create a field to store the system label in a case where the record was created/edited in the CT Mobile app. The use of another API name is not possible. |
||
RD Link |
RDLink__c |
URL |
For Remote Detailing, create a field to fill it out with an invitation link. The field to store an invitation link should have the same API name on any Activity object for the Remote Detailing session. |
||
Email Required |
IsEmailRequired__c |
Checkbox |
If enabled, the user is required to provide an email on the Welcome screen to access the Remote Detailing meeting.
|