Question

1) We would like the Salesforce custom mapper from case 109707 removed. There was a misunderstanding where we were seeking approval and instructions to deploy ourselves, rather than having it deployed.

To deploy CL need to create a ticket for CL review and deployment. It should be done by the integration team.

2) Can we share the details on how we can develop and test a Salesforce custom mapper ourselves before seeking approval?

Answer:  Doc, how to test custom logic without deployment? SFDC Connector Custom Logic | Steps to test custom logic. It can be shared with the customer. 

• https://reltio.zendesk.com/knowledge/editor/01J9YGYMN1WMSCA5M4RVTQR7NH/en-us?brand_id=2680616

3) How can we deploy the mapper ourselves after your team has approved it? Per #5 in https://docs.reltio.com/en/integrate/reltio-application-integrations/reltio-integration-for-salesforce/object-and-field-mapping/reltio-integration-for-salesforce-custom-logic/setting-up-custom-logic, our admin was not able to deploy via API.

Answer: Custom mapping can be deployed by the integration team only, because it can contain the code that will affect the whole service (for example infinite loop). For this reason, customers are prohibited from deploying custom logic themselves.

4) We also want to know the implications/risks of a custom mapper. Why are approvals needed? Does the data go through some kind of shared tenant with the use of a custom mapper?

Answer: Custom logic only affects data passed to the custom logic hook as an input parameter, but because of #3, it has to be validated by the integration team.