You are here:
Action Labels and Custom Label Mapping
Reference for how the Life Sciences Cloud mobile app retrieves action labels and maps action names to Custom Labels.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise and Unlimited Editions with Life Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the Life Sciences Customer Engagement managed package. |
Standard Actions (Record Page)
The app gets Standard Action labels directly from the standard action metadata. Override these labels in the Translation Workbench.
Configurable Actions
As of Summer '26, the label lookup behavior for Quick Actions and Custom Actions has changed.
| Action Type | Before Summer '26 | Summer '26 and Later |
|---|---|---|
| Quick Actions | The app used the Action Name as the Custom Label key (for example,
NewVisit). |
The app first looks up a custom label that uses the MasterLabel as the key. If there's no match, the app uses the built-in action name mapping for backward compatibility. If neither produces a match, the app shows the MasterLabel value. |
| Custom Actions | The app used the MasterLabel directly from the Custom Action record. |
There's no action name fallback for Custom Actions (URL, App, Utterance). When the app shows a Custom Action on a record page via a Standard Action counterpart, it uses the Standard Action's translated label instead. |
How Quick and Custom Action Labels Are Determined
The label for a Quick or Custom Action depends on whether it appears on mobile or the web. In both cases, create a custom label to control the displayed text.
On Mobile
The Life Sciences Cloud mobile app determines the label for a Quick or Custom Action in this order. The app first checks whether your org has a custom label whose API Name matches the value in the action's Label field. If a match exists, the custom label's translated value appears.
If no custom label matches, the app checks whether the action's API name corresponds to a standard Life Sciences Cloud action, such as New Visit, Start Remote Session, or Activity Plan Adjustment Request. If a match exists, the app shows the default translated label for that standard action.
If neither produces a match, the value entered in the action's Label field is shown as-is.
On Web
The app reads Quick Action labels on the web from the SObject's Buttons, Links, and Actions configuration. For example, if the SObject is Account and the Quick Action is Inquiry, the label shown is the one configured on the Account object under Buttons, Links, and Actions.
To override a Quick Action label translation on the web, use the Translation Workbench's Import Translated Files feature.
If the Quick Action doesn't exist on the corresponding object, the web follows the same lookup order described in the On Mobile section.
Quick Action to Custom Label Mapping
The app maps action names to custom labels for backward compatibility. This table shows what label text appears for each action in the Life Sciences Cloud mobile app.
| Action Name | Custom Label Key | Value |
|---|---|---|
activityplanadjustmentrequest |
ActivityPlanAdjustmentRequest | Activity Plan Adjustment Request |
createmedicalinsight |
NewInsight | New Insight |
email |
||
inquiry |
Inquiry | Inquiry |
intelligentcontent |
IntelligentContent | Intelligent Content |
lastvisit |
LastVisit | Last Visit |
newvisit |
NewVisit | New Visit |
nextbestcustomer |
NextBestCustomer | Next Best Customer |
reportcomplianceactivity |
ReportComplianceActivity | Report Compliance Activity |
startremotesession |
StartRemoteSession | Start Remote Session |
survey |
Survey | Survey |
viewconsent |
ViewConsent | View Consent |
viewonline |
ViewOnline | View Online |
