Rapid Setup - Version Control

Hi all,

I was wondering if anyone has any insight regarding Rapid Setup (RS) and version control.

What ould the best practice be to store the Configuration - RapidSetupConfiguration object. Is it as a merge object, so that upgrades will be easier?
Or perhaps is it that RS is not meant to be stored at all in Git, as its selling point is that BA’s can just use it to configure J/M/L workflows?

If any of you has stored RS files in Git, can you please indicate which ones?
And how have you managed upgrades so far?

Thanks in advance,

Charlie

A general principle I adhere to is to keep changes to out-of-the-box (OOTB) configuration objects in the codebase and utilize the merge function to deploy them across different environments. This approach offers transparency and control over the modifications made, while also mitigating potential conflicts during upgrades or patches. By managing these changes through the codebase, you can maintain a clear record of your modifications and ensure smoother deployment processes.

2 Likes

Just as a minor follow-up to Sunny’s response (which is totally correct) - I generally recommend customers that are using the Rapid Setup functionality to expose only non-prod IIQ environments to business users to use that (ideally a DEV environment). This allows them to make and test changes in a place that cannot impact production systems, and allows you to “check-out” their changes into your repository and validate them in a TEST IIQ environment (via a standardized build and deployment process) before promoting the changes to production.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.