Disable or Deregister LCA
You can learn about the various scenarios where you may want to disable or deregister the LCA service.
In some scenarios Reltio recommends you to use a cleanse function instead of an existing LCA. Take a look at the use cases below to get a clear understanding of such scenarios.
Use Case to Disable LCA for a Particular Update
In this scenario, LCA is already in use and is invoked by the Reltio APIs. However, this impacts the performance and leads to infinite loops. To prevent cascading the LCA event from the LCA hook, you have to skip or disable the LCA.
While performing any update using the POST/PUT/Delete call from the
LCA hook, use the executeLCA=false parameter to prevent cascading
of the LCA.
Use Case to Deregister LCA and Use a Cleanse Function Instead
In this scenario, LCA is already in use. However, Reltio recommended you to check if the same functions can be achieved using a Cleanser with minimized efforts. The following steps guide you to deregister/disable the LCA:
- Disable or deregister from the LCA Action.
DELETE : {{lca_uri}}/{{tenant}}/actions/<ActionName> - For the respective entities remove the LCA action entries from the L3
Configuration.
Sample L3 Configuration
{ "uri":"configuration/entityTypes/Organizations", "label":"Organizations", "description":"Organizations", "typeColor":"#008000", "typeIcon":"images/base_type/org.png", "typeImage":"images/defaultImage/no-org.png", "typeGraphIcon":"images/graphIcon/organization-icon.png", "uniqueGeneratedValuePerEntityPerRequest":true, "extendsTypeURI":"configuration/entityTypes/Organization", "lifecycleActions":{ "validate":[ "Lambda/BinaryJSON/HPOrgVal", "Lambda/BinaryJSON/HPEntityAttrLengthValidate" ] },From the Sample L3 Configuration, Remove the LCA Action Entry
"lifecycleActions":{ "validate":[ "Lambda/BinaryJSON/HPOrgVal", "Lambda/BinaryJSON/HPEntityAttrLengthValidate" ] } - Use a recommended cleanser instead. To know more about the Cleansers that Reltio provides, see Data Cleansing and Standardization.