Switching Environment for Redwood personalization

Summary:

If you/your team recently switched over to a new dev/test pod for Redwood personalization, and you are experiencing issues such as CORS errors, REST calls against FA failing due to authorization, business rules editor reporting errors, or business rules not showing up, please check the VBS Environment that is associated with your workspace and ensure that the FA instance in this Environment is NOT connected using basic auth, instead it is connected via IDCS resource (Identity domain).

Content (please ensure you mask any confidential information):

When editing Redwood page on a new Environment with VB, if in your existing project you have an Environment definition corresponding to your new FA development environment but the instance is connected using basic auth, VBS is incorrectly using this Environment definition and opening up your VB workspace. This is the Environment definition you created manually but it was setup as a deployment target from the previous VBS. VBS team plans to address this issue in the upcoming 25.04.1 patch, scheduled for March 2025. Meanwhile, as a workaround, if you notice that the Environment that is