Release date: 17 November 2021
Add skip to triggers on batch/future async transactions
To avoid errors when the triggers run on an async transaction. In this scenario, the translations will not be triggered.
Add translation facade to allow using custom flows on automatic case/email translations
This can be used to request translations automatically based on any custom flow you may have in place. This can be used on:
On a trigger context you just need to invoke the method:
Then you just need to pass as an input the Case Ids to be translated.
- Process Builders:
On a process builder you just need to add an apex action with the apex class "Request Case/Email Translation" and add it on top of your custom logic:
Translations will be requested for the case description and the last email message of each case. If a valid input is passed such as a null or empty list we will throw an exception.
*Please reach out to us if you have any custom flow where you would like to use automatic translations.
[your Salesforce Org URL]/packaging/installPackage.apexp?p0=04t1n000002Guac
Unbabel for Service Cloud
[your Salesforce Org URL]/packaging/installPackage.apexp?p0=04t1v000002GzJI
⚠NOTE: We recommend that you test this feature in a test/UAT environment before enabling it in production. A validation/trigger on the Case may impact or process when assigning a new owner.
Please sign in to leave a comment.