Transact for Salesforce App Installation
PlatformApplicable to all products in Temenos Journey Manager. | All Personas | All versions This feature is related to all versions.
For any new deployment of Transact for Salesforce App, you should use the latest available version compatible with your Manager instance, as shown in the compatibility matrix below.
| Transact for Salesforce App Version | Release Date | Improvements | Manager Version |
|---|---|---|---|
|
August 24, 2017 |
Resolved issue with encoding of Post Request data |
4.3 |
|
|
March 7th, 2016 |
Point release to accommodate customer driven features and bug fixes |
4.3 |
|
|
December 16th, 2015 |
Point release to accommodate customer driven features and bug fixes |
4.3 |
|
|
December 2nd, 2015 |
Minor patch release to improve permissions around Apex class access. No functional changes are included. |
4.3 |
|
|
November 28th, 2015 |
Point release to provide client requested features and bug fixes. |
4.3 |
|
|
September 23rd, 2015 |
This is the original AppExchange version containing baseline features. |
4.2 |
The latest Salesforce portal war files are listed below.
| Manager Version | Portal WAR File |
|---|---|
|
4.3.4+ |
Manager version 4.3.4 and higher has the Salesforce form space war file built into the Journey Manager installer. |
|
4.3.3 |
avoka-sf-portal-salesforce433.war Journey Manager version 4.3.3 is EOL, so you must upgrade to newest Journey Manager, which includes the Salesforce portal. |
|
4.3.2 |
avoka-sf-portal-salesforce432.war Journey Manager version 4.3.2 is EOL, so you must upgrade to newest Journey Manager, which includes the Salesforce portal. |
The Salesforce app can be installed into the Salesforce Organization by clicking this link and following the prompts.
Service Definition Import Options
When importing service definitions deselect the Preserve Existing Services option in the import wizard while leaving the Preserve Existing Service Connections option selected:
Once you have imported new versions of the services you are required to manually activate these service versions and where appropriate, update the configurations that refer to the old version of the service to point to the new version.
Security Manager Import Options
When importing the security manager, deselect the Preserve Existing Security Managers option, as shown below.
Importing the security manager in this way will overwrite the parameters you have specified against this security manager, so make a backup copy of them first. In particular, the Client Id and Client Secret properties should be backed up and re-set after import.
Once you have imported new versions of the services you are required to manually activate these service versions and where appropriate, update the configurations that refer to the old version of the service to point to the new version.
Next, learn about Transact for Salesforce App troubleshooting.