There can be instances, where you might need to associate a resource with more than one lifecycles. For example, when you govern an artifact by storing it in the WSO2 G-Reg Store, it needs to have both a development lifecycle and a store-specific lifecycle. WSO2 G-Reg Governance Framework supports all associated lifecycles to perform operations independently. Furthermore, deleting a lifecycle from a resource does not alter other associated lifecycles or lifecycle states.
For example, when you add a new SOAP service, it is associated with a service-specific lifecycle by default as shown below. For instructions on viewing this lifecycle, see Viewing attached lifecycle(s).
However, this does not limit the service provider from associating this asset with other available lifecycles. For example, you can add other lifecycles to this asset. For instructions on adding another lifecycle(s) to it, see adding a lifecycle.
You view the multiple lifecycles attached to the asset as shown below.
The Lifecycle History section displays the history of all the lifecycle state transfers as shown below.