Transact Config

Journey Engage allows you to use .transact-auth variables inside transact-config.json. For example, you can define formCode and clientCode in your .transact-auth file, allowing you to define different settings in different environments.

tmHost=https://tm.workspaces.avoka-transact.com
username=<your JM username>
password=<your JM password>
transactFormCode="workspaces-22-04"
transactClientCode="workspaces"

Then in your transact-config.json all you need to do is to wrap the .transact-auth variables inside "${...}".

Example transact-config.json

{
  "buildDir": "packages/workspaces/build",
  "domainModelFile": "transact-schema.json",
  "appDef": {
    "name": "Workspaces 23.04",
    "formCode": "${transactFormCode}",
    "clientCode": "${transactClientCode}",
    "configPath": "development",
    "idleTime": 1860000,
    "transactInsights": false,
    "locale": "en",
    "theme": {
      "primary": {
        "main": "#0075DB" 
      }
    },    
    "formVersion": {
      "versionNumber": "22.10"
    }
  }
}