Support for Digital Business Experience or Non-Digital Business Experience Deployment Model

Launch supports the multiple deployment options-

• Launch integrated into Digital Business Experience stack (DBE).

• Launch integrated into non-Digital Business Experience stack.

There are certain features applicable to DBE deployments that will have the solution level validations and mandatory properties for catalog definitions. However, for non-DBE deployments these properties may not be relevant. With the introduction of a Feature flag we can now absolve non-DBE deployments from using DBE features or restrictions. By default the Launch application will support DBE stack deployment. For non-DBE stack deployment, we now can set this Feature flag using a REST end point to inactive DBE features as a part of setup of Launch application. Once you have set this switch you can't toggle them.

Example - There are certain DBE specific fields like billing type, billing service type, service instance, composition type, fulfillment item code, Time based offer etc. on product offering which are required for the DBE solution. When switch is off then these DBE specific fields and validations will not be available.

The business benefit of this feature is the ability to use Launch for both DBE and non-DBE customers with much ease. 

Steps to Enable

To enable this feature you need to log a Service Request (SR).

• Raise a Service Request to Support to inactive the DBE capabilities  (one-time initial setup)

Access Requirements

• Communications Catalog Administrator