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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Manage Build / Migration of Redwood HR Helpdesk UI configurations in Multiple Environments of Fusion
Summary:
Manage build/migration of Redwood HR Helpdesk UI configurations in multiple environments of Fusion, acknowledging the Oracle limitations
1) ONE VB Studio instance for development
2) Lack of migration tool to migrate app composer objects selectively
Content (required):
I'm currently working on a Redwood HR Helpdesk implementation.
I see challenges with migrating Redwood HR Helpdesk UI configurations from TEST to other environments due to the limitation that Oracle provisions only ONE VB Studio instance for development. The challenges I see in the following areas.
a) Layouts conditioned based on (Request) Category ID values (HRHD has a limitation of using other attributes of category such as Category Name or Category Short Name in conditions)