Disable Integration -> Best practices

Silvie Cady
Kilo Contributor

Dear All,

I wanted to ask you all for your advice about the best practices to Discontinue not user integration.

Functionally it was been all cleared up, and also trigger groups have been removed.

Is it recommended to remove all setting from the instance or just update them with the comment that its not used anymore?

For example : SOAP message,Script Include, properties,transform maps, import set tables,

In the left Navigator menu: we have the application with with its modules also,

Does anyone of you have any experience with this ?

For example for users its recommended to keep them in the system, but I suppose for Integrations, there is not such recommendation?

 

Thank you,

Silvie Cady

1 ACCEPTED SOLUTION

Hello Silvie,

 If you have solution / integration document available, then make use of that and check/disable whatever configuration available like SOAP, REST web services, Scheduled imports, business rules related to integrations. transform maps,

Please go through the document available then makes changes.

Thanks,

Abhishek

 

Thank you,
Abhishek Gardade

View solution in original post

8 REPLIES 8

vinothkumar
Tera Guru

Yes you have to deactivate all the  SOAP message,Script Include, properties,transform maps, import set tables if you are not using the integration

For application navigator and modules, just add admin role alone so that it will not be visible for other user.

 

Make sure to disable all the outbound and inbound calls that is enough.

 

so we will just mark them active = false 

Hello Silvie,

 If you have solution / integration document available, then make use of that and check/disable whatever configuration available like SOAP, REST web services, Scheduled imports, business rules related to integrations. transform maps,

Please go through the document available then makes changes.

Thanks,

Abhishek

 

Thank you,
Abhishek Gardade

Thanks Abhishek