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
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