The newly deployed process definition will be applied when a new instance is started.

Yes, the tool supports inputs per one Exclusive Gateway. For example, If User Task "A" has decisions 'a1', 'a2', and User Task "B" has decisions 'b1', 'b2', and "A" is linked with an input flow to Gateway "G"and "B" is linked with an input flow to Gateway "G", then "G" will require to define output flows with conditions for decisions 'a1', 'a2', 'b1', 'b2' (except 'Cancel').

Refer the project Workflow Bitbucket.

A Bitbucket repository is a storage location provided by Reltio where you can store and manage your custom workflow code. It facilitates automated building and deployment processes through integrated pipelines, ensuring streamlined updates and adherence to code quality standards.

If you do not have a Bitbucket repository set up, contact Reltio Support to initiate the request. The support team will liaise with the Workflow team to create your repository and grant the necessary permissions. For more information, see topic Configure custom workflows.

Once a pull request is merged, an automated pipeline triggers the building of a new JAR file from the merged code. This JAR is then automatically uploaded to your designated AWS S3 bucket, ready for registration and use in your tenant.

The integrated pipelines with tools like Sonar and Snyk automatically review your code when you create a pull request. You must address any recommendations or required changes, these tools suggest, before the final merge to ensure compliance with quality standards.

Implement the necessary changes to your code based on the recommendations provided by the automatic code review process. Once the revisions are made, push changes to the branch and automatic pipelines will restart, and review the updated version of the custom code.

Once the JAR is uploaded, you can register it in the Reltio Workflow Modeler or use the specified API. Instructions and necessary links are provided in the notification email you receive after the JAR file is uploaded.

Automatic pipelines streamline the development process by automating code reviews, JAR building, and deployment. This reduces manual effort and accelerates the overall time from development to deployment, ensuring higher efficiency and reliability.

Direct changes to the master branch are restricted to ensure code integrity and compliance. All changes must be made through pull requests, which allow for proper review and testing before integration.

If you don't receive a notification, please check your spam folder and ensure that your email settings allow messages from Reltio domains. If the issue persists, contact Reltio Support for further assistance.

Both the Bitbucket repository and the AWS S3 bucket are owned and managed by Reltio. However, access to the Bitbucket repository is granted so you can manage and deploy your custom workflows.

Yes, a JAR file can be deployed across various tenants, and its classes can be incorporated into different workflows. We recommend isolating common functionalities, such as utility classes, into a separate JAR file. This approach facilitates the reuse of these components in multiple custom workflows, enhancing efficiency and consistency across your projects.

The repository with the code for custom workflow is based on Maven modules (https://maven.apache.org/). The sample implementation of a custom code is shared along with the repository and it is designed in a way where the parent module describes all the dependencies needed by its sub-modules(https://maven.apache.org/guides/mini/guide-multiple-modules-4.html).

Every sub-module is built into a single jar. You can create as many sub-modules as you need.

The Workflow API automatically utilizes the most recently registered version of a JAR file. If the same class is present in multiple JAR files, the system selects the class from the JAR that was most recently deployed.

To maintain system efficiency and reduce confusion, we recommend deactivating the previous version of a JAR after deploying a new one. However, previous versions remain available for registration, which is useful if you need to revert to an earlier version due to issues with the new implementation.

Our system retains all versions of JAR files, so previous versions are always available for registration. However, it’s important to manage the versions of your JAR files to prevent overwriting. If the version number in the pom.xml file is not updated, a new build may overwrite the existing JAR file with the same version label.

<artifactId>CustomWorkflow</artifactId>
<version>1.0-SNAPSHOT</version>

Yes, there is a comprehensive webinar available that provides a detailed walk-through of the new self-service custom workflow development process. View this webinar to understand the steps involved, along with tips and best practices. The webinar is available on the Reltio community page at this URL: https://community.reltio.com/blogs/nigel-burgess/2023/11/09/community-show-accelerate-custom-workflow-developm.