Currently, we are performing SIT and our next step would be to migrate from Sandbox Environment to Production Environment.
We have developed lot of artifacts in our Sandbox Environment like building the authoritative Source, Identity Profile, Transforms, Connector Rules, Cloud Rules, AD Source, Provisioning Settings etc.
I would like to hear from experts on the ways to migrate all these artifacts in to the Production Environment.
Also, I seek the best practices for doing this activity along with some do’s and don’ts to avoid turn around time.
I will share my experience with the caveat that I am by far not an expert.
Note that I come from the ServiceNow development world, where all your updates are captured in a single “update set” that you can import and commit to another environment quite easily inside the GUI.
The first thing I realized is that you cannot do everything all at once. You need to commit items in order of least dependency, meaning the items that have zero dependencies go first, items dependent on those go next, etc.
I haven’t had good luck with moving new identity profiles and new sources using the sp-config API endpoints. Importing the identity profile doesn’t seem to work if you’re trying to add a new identity attribute in the profile that leverages an account attribute from a source you just imported. IDK if I need to wait longer, but I eventually gave up and created the identity profile manually.
This seems more of a philosophical thing, but in ServiceNow I was used to the Ids of objects persisting environments. This is not the case in IdN as new Ids are created for each object that’s imported. It makes it slightly inconvenient when you’re trying to integrate with an external tool because you have to set environment variables storing those object ideas, but not the end of the world I suppose.
Anyway, good luck and hopefully others will chime in.