LCA Certification Checklist

You can use this checklist before submitting the LCA to Reltio for review.

Ensure that the following points are taken care of, before submitting the LCA to Reltio for review:

  1. Before sending the Life Cycle Handler for review to Reltio, confirm the following items in the LCA review ticket:
    1. Ensure that the full LCA source code is attached.
    2. Ensure that the compiled jar (without dependencies for S3 upload) is attached.
    3. Explain the purpose of the LCA purpose and the modifications.
    4. Ensure that the package structure is named properly to avoid conflicts with other LCA JAR files.
    5. Ensure that the LCA executes in a reasonable amount of time.
    6. Ensure that the LCA does not use slow devices/media (such as the file system).
    7. Check the code with a static analysis tool and ensure there are no bugs and major issues.
    8. The LCA code must not have any System.out or System.err statements. Instead, the code must use log4j.
    9. The LCA code must not use static fields or perform long-term data caching. Short-term caching of a small amount of information (no more than several strings, such as the OAuth token for user) is allowed and helps to optimize LCA.
    10. The LCA code must try to minimize the number of calls to the Reltio API or Reltio OAuth. Reltio recommends requesting an additional extension of the LCA Framework API instead of calling the API directly from the LCA code.
    11. The LCA code must avoid execution of third-party services, as the LCA server is installed in the Reltio Connected Cloud.
    12. The LCA code must be designed to run in clustered environments. Reltio offers no guarantee that several consecutive LCA calls can be run in a consecutive manner and on the same server.
    13. The LCA implementation must consider frequent execution of the LCA code and must be done in a way that LCA code execution does not take more than 15 milliseconds to execute.
    14. Ensure that the LCA does not contain memory leaks and does not contain exploits.
    15. The LCA must have unit tests to cover the testing of LCA requirements.
  2. Consider the recommendations provided by the Reltio team to replace the LCA with the existing platform functionality if the platform has similar functionality. Reltio has many features that suit your requirements and advices you to choose one.
  3. Consider the suggestions that the Reltio team may provide to resolve the issues found.
  4. If the handler is blocked in runtime because of poor performance metrics, Reltio notifies you and provides a performance report.
  5. The following estimations are made for the certification process based on the Life Cycle Handlers complexity:
    • Simple (basic checks, operation allowance/declining, and changing simple attribute values): 1 day
    • Medium (changing/adding multiple attributes based on some computations and Reltio API access): 7 days
    • Complex (complex computations and use of the external APIs): 7+ days