...
Note |
---|
WSO2 Enterprise Store uses the lifecycle API provided by WSO2 Governance Registry. However, ES but does not support all the lifecycle elements provided by the WSO2 Governance Registry. |
...
Attribute | Description | Default Value | Fixed Values | Mandatory/ Optional | Notes |
---|---|---|---|---|---|
name | Defines the extension point (e.g., Transition Executors) that is used in the lifecycle. You can define only one extension point of a kind, because the underlined implementation ignores multiple elements and takes only one into consideration. |
| Mandatory |
Sample implementations
checkItems
Code Block |
---|
<data name="checkItems"> <item name="Effective Inspection Completed" forEvent="" /> <item name="Test Cases Passed" forEvent="" /> <item name="Smoke Test Passed" forEvent="" /> </data> |
The above code snippet based on checkItems renders as follows in the Publisher:
transitionExecution
Code Block |
---|
|
Code Block | ||
---|---|---|
| ||
<data name="checkItemstransitionExecution"> <item name="Code Completed" <execution forEvent="Promote"> <item name="WSDL, Schema Created" forEvent=""> </data> <data name="transitionValidation"> <validation forEvent="" class=""> class="org.wso2.jaggery.scxml.generic.GenericExecutor"> <parameter name="PERMISSION:get" value=""/> </validation> </data> <datahttp://www.wso2.org/projects/registry/actions/get" /> <parameter name="transitionPermissionPERMISSION:add"> <permission forEvent="" roles=""/> </data> <data name="transitionScripts"> <js forEvent=""value="http://www.wso2.org/projects/registry/actions/add" /> <parameter name="PERMISSION:delete" value="http://www.wso2.org/projects/registry/actions/delete" /> <parameter <console functionname="PERMISSION:authorize" value="authorize" /> <script type="text/javascript"> </script> </console> <server function=""> <script type="text/javascript"></script> </server> </js> </data> <data name="transitionExecution"> <execution forEvent="Promote" class="org.wso2.jaggery.scxml.generic.GenericExecutor"> </data> <data name="transitionUI"> <ui forEvent="Promote" href="../lifecycles/pre_invoke_aspect_ajaxprocessor.jsp?currentEnvironment=/_system/governance/trunk/"/> </data> <data name="transitionApproval"> <approval forEvent="Promote" roles="" votes="5"/> <approval forEvent="Demote" roles="admin" votes="5"/> </data> |
<parameter name="STATE_RULE1:Created" value="Internal/private_{asset_author}:+get,+add,+delete,+authorize" />
<parameter name="STATE_RULE2:Created" value="Internal/reviewer:-get,-add,-delete,-authorize" />
<parameter name="STATE_RULE3:Created" value="Internal/everyone:-get,-add,-delete,-authorize" />
</execution>
</data> |
...
Anchor | ||||
---|---|---|---|---|
|
...
Attribute | Description | Default Value | Fixed Values | Mandatory/ OptionalNotes | ||
---|---|---|---|---|---|---|
name | Defines the name of the check item. ES allows you to define check items for each transition. | N/A | Optional | |||
forEvent | Defines whether the check item is required for a specific transition. A check item can be required for more than one event, in which case, a user can give a comma (", ") separated list for theforEvent ") separated list for the
| Null : Keeping the forEvent attribute empty means that a specific check item is not required for any transition event. | OptionalThe forEvent value is defined under the <transition> element with the event attribute. |
Sample implementations
Code Block | ||
---|---|---|
| ||
<data name="checkItems"> <item name="Effective Inspection Completed" forEvent="">< /item> > <item name="Test Cases Passed" forEvent="">< /item>> <item name="Smoke Test Passed" forEvent="">< /item>> </data> |
...
The above code snippet based on checkItems renders as follows in the Publisher:
...
Anchor | ||||
---|---|---|---|---|
|
...