What is best practice for rolling out Visual Builder and Redwood in HCM Cloud?
We’ve been investigating Visual Builder and the various ways to run it to integrate with and extend Oracle Fusion, as well as our overall journey to Redwood for SaaS.
As such I have a few queries:
- Our customer success manager advised we can move the instance of VB associated with TEST to another pod, but once only. As we see it, we have two options with this – either pair to our usual DEV environment (DEV2) so we know Visual Builder can be used in all BAU changes by developers. Or, we can pair to DEV17, which is our Redwood discovery pod. We know Redwood becomes mandatory for Learning in 24B, so our Learning developer is using DEV17 as the assurance pod before we put it live. We are thinking of pairing Visual Builder with DEV17