Sandboxes and Brands

[BAli98]

Currently, we have a multi-branded main portal, with a couple of brands set up that have specific objects/properties/forms etc associated with them. When setting up a sandbox none of this comes across and all defaults to the Sandbox “brand” - which then causes us issues if we want to develop/test/deploy brand specific functionality.

We would like consideration for existing brands in the account to be carried over into the sandbox environment, and for us to be able to then deploy brand specific changes back into these brands on the live environment.

[GilBolster]

This also causes issues with deployments, as all emails default to the standard Sandbox brand, which then prevents them (and any other assets associated with them) from being deployed. This is a major bottleneck to large workflow deployments, as we tested these in the sandbox, have to remove all send actions, then deploy the workflow and add in the send actions again.