Hello everyone. I’d like some candid feedback here.
We are planning to migrate from IIQ to ISC this year. We have heavily configured IIQ and it is doing a lot of work for us, from Workflows, to Forms, to Rules.
My question is this - When we move to ISC, will we need to have a medium number of scripts that run outside of ISC in order to help do various functions within ISC. For example, ISC may not allow for some certain action that we are used to in IIQ, so we would have a helper script that would run outside of ISC and would call the ISC API in order to do the task that we need to perform.
We have gotten the feeling that we will probably need quite a few scripts that interact with the ISC API in order to fulfill our business and technical requirements.
I want to understand what we should expect. Will we have to write a bunch of code outside of ISC? And if so, what would we need to write custom code for? What functions does ISC not support that people usually account for with scripts that talk to the ISC API?
My bigger question is - Does everyone expect that we will need a dozen or so scripts outside of ISC to make ISC work the way we want?
I want to understand what we should expect. Will we have to write a bunch of code outside of ISC? And if so, what would we need to write custom code for? What functions does ISC not support that people usually account for with scripts that talk to the ISC API?
Yes, it’s quite common for organizations to write a set of custom scripts outside of ISC to achieve the level of automation and integration they require. While ISC will handle many of the core functions, expect to write code for:
As ISC is a SaaS solution, it is important to manage expectations regarding the migration of all specifications and policies. Not all elements can be moved 100%, and this should be considered a baseline expectation. Prior to initiating development, it is crucial to draft a comprehensive requirements document. This document should include a detailed analysis of what can be achieved OOTB and what requires customization.
For complex use cases, we also use custom scripts outside of ISC, which leverage ISC APIs or SDKs. These scripts can be hosted on a dedicated server with access to ISC APIs. It is essential to implement robust logging in scripts and set up notifications for both failures and successes.
Furthermore, if the scripts need to access target systems directly, ensure that passwords are encrypted and stored securely, also discuss approaches taken with your client to ensure they are comfortable with these security measures.