Landing the Expansion

distributing your new expansion solution you've just created follows the exact same lifecycle as your original product did you have already built the workflows, tested them in your dedicated developjment environment, and prepared them for release the mechanism for moving from dev to staging and production remains unchanged you package your work into a bundle and push it to the warehouse the primary change int he process is the identity of the bundle because this solution targets a different external platform or set of external platforms, your bundle name must reflect that specific context (e g , background check for ukg pro recruiting vs background check for greenhouse ) once imported into the solution manager , this new bundle becomes a distinct entry in your catalog, allowing you to manage and deploy it independently to the relevant customer segment while maintaining the same underlying operational logic as your original solution