Learn about Redwood and be one of the first to join the conversation

Visit Redwood Community
Best practice pertaining to application names and maintaining prod & non-prod environments — 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

Best practice pertaining to application names and maintaining prod & non-prod environments

Accepted answer
11
Views
5
Comments

Summary:


Content (required):

Hi Everyone,

I'm looking for experiences/recommendations/best practices regarding application names and maintaining a prod & non-prod environment. If both environments have a different application name (i.e. CompanynamePROD & CompanynameTEST), how do you manage migrating objects between environments. As of now, I have spent about 1.5 hours trying to migrate a simple navigation flow and for the life of me I cannot figure out what text needs to be changed in which files of the source environment export. I wonder if it is easier to simply re-configure whatever object you want to migrate in the new environment, but that would allow for further

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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