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
Get Started: AI Resources for Oracle Cloud HCM – Go Here

Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here

Why do changes in one project skip when changes in another project are published?

Summary:

Hi all,

we are facing a problem in VBS: we created a project for the migration of customizations from the old UI to Redwood.

After months, a group that is not part of the Redwood implementation team created a new project with its own workspace.

We realized that when the other team publishes the changes in their project, our changes are skipped.

How can we solve the problem?

What is the best practice to follow?

Should we have only one project in VBS and create a workspace for each module where?

Thanks in advance,

DFEC

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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