Do we need to create separate project for Redwood implementation for each module for the below case? — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Do we need to create separate project for Redwood implementation for each module for the below case?

Summary:

Hi Team,

In our business case, we have an ORC implementation going on in the lower environment, we also also working on the migration of the customizations to REDWOOD pages as a REDWOOD implementation for Core HR, Talent , Absence and OTL Modules, However, we can see in our lower instance, already one project and its workspace is created as part of ORC implementations for ORC related personalizations to cater, now that we are starting with the migrations for other module, what should be the ideal and recommended approach in this case?

Should we need to create separate projects for each module or should we utilize the same project, since we have to plan for a migration of these customizations in production too in the upcoming month.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!