Page Comparison

Defines the class that is associated with the lifecycle.

org.wso2.jaggery.scxml.aspects.
JaggeryTravellingPermissionLifeCycle

org.wso2.jaggery.scxml.aspects.
JaggeryTravellingPermissionLifeCycle

Defines the name of the lifecycle state.

This element contains all the custom elements, which are defined in the lifecycle model. Based on the SCXML specification, you can define a data model to a lifecycle state and you can use this extension to define custom elements.

Defines the extension point (e.g., Transition Validators, Transition Executors, Transition User Interfaces and Transition Scripts) 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.

For transitionApproval, the following rules apply regarding roles and votes:

• • roles="" - Any user can vote
  • roles="admin" - Only users with an admin role can vote
     
  • votes="2" - Two votes are required for approval.

• checkItems - If the user is defining check items as its child elements.
• transitionValidations transitionExecution - If the data element defines transition validations.
• transitionPermission - If the data element defines transition permissions.
• transitionScripts - If the data element describes the transition scripts.
• transitionExecution - If the data element defines programmable programmable executions for transitions.
• transitionUI - If the data element defines custom UIs that accept user input for transitions.
• transitionApproval - If the data element defines lifecycle transitions that need user approvals.

These elements contain the check items for each state. There can be more than one of these elements.

ES lifecycle configuration has the ability to allow JavaScript functions to execute on both the server-side and the client-side. The js element defines the scripts that is executed for different events.

Defines the respective transition for which the JavaScript function is executed.

These elements contain the check items for each state. There can be more than one of these elements.

Defines whether the check item is required for a specific transition. A check item may be needed for more than one event, in which case, you can provide a comma separated list for the forEvent attribute.

An executor is business logic that is executed once a state transition takes place in a lifecycle. The execution element defines the event and the execution class that is invoked at runtime.

Defines the event for which this execution is performed. This gives you the flexibility to define executions for each event.
The forEvent value is defined under the <transition> element using the event attribute. 

Defines the JavaScript function that ES needs to execute on the client-sideThe name attribute defines the name of the parameter and value attribute defines the corresponding value of the parameter. This parameter element is defined under the <execution> element.

This attribute defines the name of the function that is executed when an asset moves from one lifecycle state to another.

This is the same as the console function and the only difference is that this element defines the scripts that are executed on the server-side.

Defines the name of the function that is executed at an asset transition from one state to another.

An executor is business logic that is executed once a state transition takes place in a lifecycle. The execution element defines the event and the execution class that is invoked at runtime.

Defines the event for which this execution is performed. This gives you the flexibility to define executions for each event.

parameter. 

• If you use the org.wso2.jaggery.scxml.generic.GenericExecutor executor, it is mandatory to specify the following default permissions as it is needed for the ES permission model.
  • PERMISSION:get

  • PERMISSION:add

  • PERMISSION:delete

  • PERMISSION:authorize

• In addition, you can specify custom rules for specific user roles that are executed when various state transitions take place.

• ES permission model related values
  • PERMISSION:get

  • PERMISSION:add

  • PERMISSION:delete

  • PERMISSION:authorize

• If you use the org.wso2.jaggery.scxml.generic.GenericExecutor executor, it is mandatory to specify the following default permissions names together with their corresponding values as it is needed for the ES permission model.
  • PERMISSION:get

  • PERMISSION:add

  • PERMISSION:delete

  • PERMISSION:authorize

• In addition, you can specify custom rules for specific user roles that are executed when various state transitions take place. In each of these rules you can specify as to which permission is added or removed when the state transition takes place. Permissions are added and removed in the following manner:
  • + <PERMISSION>
For example,  + delete means that the delete permission is added when the lifecycle state transition occurs.
  • - <PERMISSION>
For example,  - delete means that the delete permission is removed when the lifecycle state transition occurs.  

 For example:

• • Code Block
    <parameter name="STATE_RULE1:Created" value="Internal/private_{asset_author}:+get,+add,+delete,+authorize" />

    This means that when the lifecycle state changes to Created, the get, add, delete and authorize permissions are added to the private_{asset_author} user permission.

  • Code Block
    <parameter name="STATE_RULE2:Created" value="Internal/reviewer:-get,-add,-delete,-authorize" />

    This means that when the lifecycle state changes to Created, the get, add, delete and authorize permissions are removed from the Internal/reviewer user permission.

  • Code Block
    <parameter name="STATE_RULE3:Created" value="Internal/everyone:-get,-add,-delete,-authorize" />

    This means that when the lifecycle state changes to Created, the get, add, delete and authorize permissions are removed from the Internal/everyone user permission.

• ES permission model related values

  • http://www.wso2.org/projects/registry/actions/get

  • http://www.wso2.org/projects/registry/actions/add

  • http://www.wso2.org/projects/registry/actions/delete

  • authorize

The name attribute defines the name of the parameter and value attribute defines the corresponding value of the parameter. This parameter element is defined under the <execution> element.

A UI element is a mechanism to associate a user interface with a particular event during a given transition. This allows you to pass inputs that would be utilized when performing a transition. Note that you can not define an external reference link as the href attribute value. Instead you need to provide a relative path in the Carbon server as the value of the href attribute.

Defines the event for which the UI appears.

Defines the transitions, by specifying the name of the lifecycle state and the target lifecycle state, instead of using static transitions. Any number of transitions for one lifecycle state are supported.

Defines the transition event name , (e.g., Promote, Demote or any name that the user specifies.

you wish to specify).

This event name is used in the forEvent to trigger a specific event, before this transition this going on.