Journey Manager (JM)
The transaction engine for the platform. |
System Manager / DevOps | 23.04This feature was updated in 23.04
A variety of modules can be installed in your Journey Manager environment according to your requirements and license agreement. These modules are selected during Journey Manager installation. Subsequently, Manager allows you to view, configure, and remove the installed modules. For more information, see Installation guide > Modules and Form Spaces.
If you can't see a module you are after, it is possible it has not been installed, so check with your system administrator or the Cloud Services team.
To view the modules, select System > Modules Config.
To search for a module, type its name and click Search.
Click Clear to reset the search criteria.
Click Export Data to export the displayed data as a Microsoft Excel (XLS) file.
Configure a Module
To configure a module:
Select System > Modules Config.
Locate a module and click Edit.
Select the Module tab to update the module's hosting configuration.
Update the portal application fully qualified domain name in the Context Path field, for example, https://my-domain.com/manager/.
You can turn off some of the CSRF security hardening settings in non-production environments to make it easier to work with multiple browser tabs open at the same time.
Select the CSRF Protection Host Check to enable Cross Site Request Forgery protection host check. This setting is only relevant for the /manager and /workspace contexts.
Update the Documentation Url, for example, https://docs.my-domain.com.
Click the Email 2 FA Message link to edit the email message for 2FA user account enrollment.
Edit the Email 2 FA Subject, which is an email subject for 2FA user account enrollment.
Select the Production Mode checkbox to enable the module to be run in the production environment. This is selected by default. | 23.04
This feature was introduced in 23.04
To help you avoid enabling the Groovy Debug Loggingoption for Groovy services and functions by mistake in a production environment, Manager checks if the Production Mode option is selected and then sets the Groovy Debug Logging option to false for them.
When you import a Groovy service or a function, Manager performs the same check and set the Groovy Debug Logging option to false even if it was set to true in an archive file. This is recorded in the Audit Log