Itemized Capsule Transporter Package




Hi Board Community,
Currently, when transporting capsules from one environment to another (e.g., Sandbox to Production), we can only select the capsules themselves in the Transporter Package. We don't have the ability to choose specific objects or components within each capsule (e.g., screens, procedures) to include or exclude from the package. This flexibility is available with the data model transporter, where we can select which objects (e.g., cubes, entities, procedures) to move or exclude. However, with capsule packages, it's an all-or-nothing approach—either the entire capsule is moved or nothing is.
It would be incredibly helpful, from both a deployment flexibility and control standpoint, to have the ability to select individual objects within a capsule. For example, the option to migrate just a few screens rather than the entire set. This would be especially beneficial in scenarios where client admins have made updates to some screens in their Production environment, while the development team has made separate changes (such as creating new screens or editing existing ones) in Sandbox. Without this granular control, we face a catch-22 and must resort to workarounds to handle the migration effectively.
Thanks for considering this idea.
Hamza