Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
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
Tagged:
0