Do you have feedback on our new interface?
Do you have feedback on our new interface? Let us know HERE

configure pause subscription at catalog or offering level

configure pause subscription at catalog or offering level

•Brief Description
configure pause subscription at catalog or offering level
•Benefits / Value
this allows different models of acting towards failures in different Designs/offerings.
organizations are not right level to define pausing. if a subscription should be right away failing or should be fixed by an operator is usually to be decided based on the Design and what it is good for.
currently it is impossible to allow designs to fail when you have other offerings/designs that must be handled by pausing
•Design details
Move/add a function at minimum at catalog level that defines if subcriptions will pause or fail.
probably catalog is the right level between micromanagement and flexibility.
although at catalog level might grow the amount of catalogs exponentialy taking the matrix of different settings into account(permissions, potentially notifications, approval policies)
based on the growing amount of potential settings it might be a better way to set all at offering level.
there is anyway a lot that needs to be configured at offering
maybe it is good to make a standard set of Configurations for a CSA instance for newly created offerings
this would allow an CSA admin to sepcify best match for most new offering cases

1 Comment
Micro Focus Contributor
Micro Focus Contributor

I fully agree and acknowledge that failure hanlding configuration should not be made at the organization level, as how a failure should be handled will depend on the implementation of the service design and can vary from one service design to another which has no relation to where from (catalog or oragzation) that service is being consumed. 

From that perspective, would it make more sense to allow this configuration at the service design level, so that all the offerings created from that service design inherits that behavior and not require this to be configured per offering (a lot of times multiple offerings are created from a service design)? When we "revisit" this we want to do it the right way :-)

Also agree that there are a lot of configuration that can be offered at the service offering level for more flexibility, to name a few, default or allowed ownership type, e.g. user owned or group owned, default or allowed subscription lease type, e.g. recurring or periodic etc. These type of settings should be allowed at the service offering level.





The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.