LCA Handler Certification

LCA Handlers can be certified for performance, security, and other aspects.

Life Cycle Action Handler Certification

Each Life Cycle Action Handler created and used in a Reltio configuration, must pass certification for performance, security, and other aspects before it can be used and deployed in production.

Manual Certification

Code Review

Reltio engineers review handler code in order to prevent malicious or incorrect code execution inside the Reltio service. Reltio reviews the submitted code and checks for the following:

  • Does not contain memory leaks
  • Does not contain exploits

For synchronous hooks, Reltio ensures that the code does not contain attempts to work with the file system, network, or any other slow devices. This check is aimed at preventing long execution of synchronous hooks and API performance degradation.

Important: Ensure that your LCA is of high performance and executes quickly, typically within milliseconds. This is important since it is a synchronous operation with the entity life cycle.

Submitting LCAs to Reltio

You must submit each LCA (with tests) for review to Reltio. Each LCA must pass the code review performed by Reltio. In general, complex LCAs do not pass the initial reviews and may require iterations. After you submit the LCA, Reltio requires a few hours to review. You must schedule a time for the review process and potential iterations.

All LCA code must be submitted and stored in the Reltio Bitbucket repository. All the submitted LCA packages must use a consistent structure, with test and Maven build files that can be executed with a standard Maven tool.

LCA submission steps are illustrated in the diagram below.

Credentials

The credentials for the LCA repository are as follows:

<server>
          <id>reltio-libs-public</id>
          <username>read.only.life-cycle-framework</username>
          <password>xxxxxxxxxxxxxxxxxxx</password>
      </server>

The credentials for other libraries are as follows:

<server>
          <id>reltio-libs-release</id>
          <username>read.only.workflow</username>
          <password>xxxxxxxxxxxxxxxx</password>
      </server>

The POM should reflect the most recently used version.

<dependency>
   <groupId>com.reltio</groupId>
   <artifactId>life-cycle-framework</artifactId>
   <version>[2019.1.0.0.0, 2019.2.0.0.1)</version>
</dependency>
<dependency>
   <groupId>com.reltio.services.lca</groupId>
   <artifactId>reltio-lca-service-test-framework</artifactId>
   <version>[2019.1.0.0.0, 2019.2.0.0.1)</version>
   <scope>test</scope>
</dependency>