Reltio Connect

 View Only
  • 1.  Deployment steps for Custom Workflow to Reltio

    Posted 24 days ago

    Hi Team,

    I heard that the custom workflow deployment process has been changed to self-deployment now, does anyone have the steps to follow? 

    Second, does anyone know how to test workflow locally?



    ------------------------------
    Abhimanyu Kumar
    GSK
    Cary NC
    ------------------------------


  • 2.  RE: Deployment steps for Custom Workflow to Reltio

    Reltio Employee
    Posted 22 days ago

    Hi Abhimanyu, 

    Yes, in the recent past, there has been a change in the workflow deployment process to reduce the dependency on the Reltio Support tickets. I am sharing the link to a community event where our product management and engineering team demoed and shared detailed information about the new process - https://community.reltio.com/blogs/nigel-burgess/2023/11/09/community-show-accelerate-custom-workflow-developm

    On a very high level here are the steps you would need to follow 

    • Create a support ticket to request a Reltio bitbucket repository to be provisioned for the customer to perform workflow development and deployment. Please make sure to share the tenant IDs where the workflow jar registration should be enabled and the list of users who will need access to the bitbucket repository. 
    • The Reltio workflow team will provision the bitbucket repository for you with a sample project for workflow customization. 
    • You will then enhance that as needed and make enhancements to the workflow customization as per the requirement. 
    • Once the build and unit testing is completed using a local workflow adapter, check-in the code in a feature branch of the previously mentioned repository. 
    • Create a pull request to merge the code to the master Branch. **You will not have direct access to merge to the master branch as that will happen by the PR and the pipeline. 
    • Through the pre-built bitbucket pipeline, a series of build, code quality, and coverage checks will be performed on your code, and if everything is in order the build will be completed successfully.
    • A manual approval is required from a default reviewer as well in the pull request. The PR will be ready for merge only when the automated build process is successful and the default reviewer approval is obtained. 
    • Once the PR is approved, you will merge it to the master branch. Which will trigger another bitbucket pipeline to build the code, prepare a jar, and deploy in into an S3 bucket. 
    • After successful completion of this process, the jar will be available in the respective tenants for registering. 


    Regarding your second question about testing the workflow in local, you will need to deploy a local workflow adapter in your local machine and then use that to test your code. Detailed process for that is documented in - https://docs.reltio.com/en/engage/manage-data-workflows/overview-of-workflow-customizations/setting-up-the-reltio-workflow-adapter

    Few prerequisites : 

    • Java 11 should be installed in your local system.
    • Install MariaDB server
    • Install IntelliJ Idea Community Edition or any other java IDE.

    Please review and let me know in case you have any follow-up question. 



    ------------------------------
    Diparnab Dey
    Technical Consultant
    Reltio
    Kolkata, West Bengal
    ------------------------------