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.
Expecting two lines in extension lifecycle
Summary:
Hi Oracle Team,
We were just upgraded to 24D in Test.
I published two separate changes using VBS via two different Publish actions:
- Smart Form Customization removing "Manufacturing" Section
- Smart Form Customization removing "Agreement Type" field in "Source Section
The idea being that I could identify each one separately in the "Manage Extension Lifecycle" and deploy each change separately to our Dev and Prod environments.
However, I am surprised to see that there was no distinction between the two separate publish actions and when I clicked on the rocket and deployed to Dev 2, both changes were published to Dev2. I am sure I have seen in a demo that they should be two different lines in the "Manage Extension Lifecycle".
Tagged:
0