Presently HTML and Text fields can be localized so it is possible to create HTML content in multiple languages but that content can’t be used in notifications and the email quick action html editor also does not allow localization.
Using Local() function with email notifications will always default to English.
There are many multi-lingual companies now that have to work around this with multiple language fields and business rules to check the user’s language.
That is quite cumbersome and a better solution would be to:
- Enable localization for Email Quick Actions. Subject and Body
- Enhance the Local function with a “locale” identifier so that localized fields/html can be referenced in email quick actions. For example, local(“This is a test”,”de-DE”) or local (NotesBody,[FrsCompositeContractContact#.IncidentAssociatedCustomer]ContactLanguage)
Please vote for this Enhancement Request for Localized Email Quick Actions #Ivanti #Neurons #ITSM #IvantiServiceManager #HEAT #Localization #QuickAction #Email #EnhancementRequest
Recently one of my clients in the UK had an issue where they needed to reset a number of internal HEAT user passwords using the Service Desk Manager role for operations in Singapore.
The challenge was that the “Reset User Password” OOTB quick action and underlying API call can only be run by the Admin role.
The workaround was to add a flag to the employee business object that triggers a workflow to run with a quick action block to call the “Reset User Password” OOTB quick action, which although triggered by the SDM role, would then run using INTERNALSERVICES which has the admin role.
Here is a helpful UI Action to launch a Calendar Workspace.
The calendar workspace scope isn’t documented and you may have a hidden Task UI Action to launch a calendar workspace. In case you missed it here it is:
One of the HEAT Classic Features that is frequently requested is to bring back the customer history. There are several implementations for this, yesterday covered how to implement Incident Customer History for Related Items, aka Object Matching, today we will cover how to show Customer History using a Quick Action.
- Create a UI Quick Action for Incident
- Scope: ObjectWorkspace
- Command ID: Search
- Confirmation: null
- Command Data:
Save and add to the Incident Layout Form View Toolbar with disabled expression:
$(nvl(ProfileLink_RecID, “”) == “”)