Current Version Selector Service

   Journey Manager (JM) The transaction engine for the platform. |   System Manager / DevOps |  All versions This feature is related to all versions.

Manager comes with the Current Version Selector core global service, which chooses the appropriate form version to render a form. The default service returns the current form version unless a specific version was requested.

If you would like to customize the way versions are selected, for example, for A/B testing, you can create your own form version selector service and implement custom logic in a GroovyGroovy is a powerful scripting language which runs on the Java Virtual Machine. Across theTemenos Journey Manager platform, Groovy is used to create services in Manager. These services are primarily used to create plug-in style systems that interact with Manager. script.

Note

This service can be configured on the form level, otherwise, the system default version selector service is used.

To configure the Current Version Selector service:

  1. Select Services > Core Global Services.
  2. Locate the service and click Edit.
  3. Configure the standard service settings.
  4. Select the Parameters Edit tab to view and edit the specific service configuration.
  5. Select the Ignore Form Version Request Parameter checkbox to always use the current form version regardless of the value of the tmFormVersion request parameter. This can prevent users loading and creating transactions of an old form version by providing the tmFormVersion URL parameter. This option is not selected by default.
  6. Click Save to update the changes.

Next, learn about A/B testing form version selector service.