Follow the instructions below to add a lifecycle to the Governance Registry.
1. Sign in. Enter your user name and password to log on to the Management Console.
2. Click the "Extensions" button to access the "Extensions" menu.
3. From the left navigation menu, under "Extensions," select "Lifecycles."
4. Click the "Add New Lifecycle " link on the "Lifecycles" page.
5. A configuration page with a sample lifecycle configuration is shown. Make needed alterations and click on the "Save" button to save the configuration.
See the detailed information about a lifecycle configuration in Configuring Lifecycles.
See also Managing Lifecycle to learn how to assign a lifecycle to a resource/collection.
Adding multiple life cycles
WSO2 Governance Registry 4.6.0 allows only one lifecycle to attach to a particular governance artifact type. However, when an artifact governed in the G-Reg and is in the Store, it gets associated with a Store-specific life cycle in the Store, and also have another development life cycle within G-Reg itself. Therefore, the functionality of the resources is independent of the life cycles. With the new improvements in G-Reg 5.0.0 onwards, you can associate multiple life cycles to a resource.
For an example, when you add a new service in the Management Console, it is associated with a Service-specific lifecycle by default. You view it in the Attached Life-Cycles panel as shown below.
You can associate another life cycles to the resource by adding the life cycle in the Lifecycle panel, when you add the resource as shown below.
Now, you view the EndPointLifeCycle you selected above also associated to the Service artifact in the Attached Life-Cycles panel as shown below.
This does not limit the service provider to associate other available life cycles. All associated life cycles can perform operations independently. You can view and edit the details of each life cycle by selecting them from the drop down menu in the Attached Life-Cycles panel. Deleting a lifecycle from a resource does not alter other associated life cycles or their states.
If you add the Service using the Publisher, then it gets associated with a Service-specific life cycle and a Store lifecycle by default.
The life cycle history view displays all the history of all life cycle operations on state transfers as shown below.