Configure Transact Function Service Definition

   Journey Manager (JM) Previously known as Transact Manager (TM).  |    Form Builder Platform Developer  |  v17.10 This feature was introduced in v17.10.

Manager allows you to configure a Transact function's main parameters in the Service Definition tab.

To configure the Transact function service definition:

1. Select Services > Transact Functions.
2. Locate a Transact function and click Edit.
3. Select the Service Definition tab.



4. Enter a new Transact function name in the Service Name filed. This name combined with the Version Number must be unique.
5. Enter a Transact function version number in the Version Number filed. Version number must adhere to semantic versioningSemantic Versioning is a formal convention for specifying compatibility using a three-part version number: major version; minor version; and patch. The patch number is incremented for minor changes and bug fixes which do not change the software's application programming interface (API). The minor version is incremented for releases which add new, but backward-compatible, API features, and the major version is incremented for API changes which are not backward-compatible. For example, software which relies on version 2.1.5 of an API is compatible with version 2.2.3, but not necessarily with 3.2.4. practices.
6. Select the Current Version checkbox to allow Manager to use this function in a form.
Note

You can use this option to rollback this Transact function.

7. Provide a meaningful description of what this Transact function does and why in the Description field.
8. Select the Transact function template type from the Service Type dropdown list as shown below.
• Fluent Function.
• Delivery Function.
9. Specify the organization, which this function will be available to, in the Organization field. If the organization is not set, this function is globally available, so it can be used in any Organization.
10. Select the Service Type Default checkbox to use this Transact function as the implementation of this Service Type. Only global services and Transact functions can be marked as the default.
11. Select the invocation method to create this Transact function from the Service Creation Method dropdown menu:
• Java Classname to create a new instantiate of this Class it as a new Java Object using Class.forName() method.
• Spring Bean to look it up from the Sprint configuration files.
12. Enter the Java Class name, for example, com.avoka.fc.core.service.fluent.FluentFunctionService, or the Spring Bean name, which is used to create this function, in the Classname / Bean Name field.
13. Select a service connection that this Transact function should use or leave it blank if it is not required.
14. Click Edit to go to this service connection.



15. View or edit the service connection if needed.



16. Select the Active checkbox to make this Transact function active so it can be used in Manager. It is selected by default.
Note

You can use this checkbox option to rollback this Transact function.

17. Specify the minimum Manager version, which is required to run this service, in the TM Min Version field.



18. Click Save to update the changes.

Next, learn how to edit Transact function Groovy script.