Rules perspective can be used to:

• add variables whose scope can be either public or private.
• define business rules using spreadsheet functions and operators on both public and private parameters.
• define business rules on parameters across other models using ‘networked-object’ access.
• provides a WYSIWYG approach with one-to-one correction of  ’spreadsheet form’ to ‘application form'.

Forms perspective can be used to:

• map different UI widgets for the public parameters.
• customize the page based on work-flow status.
• include parameters from other models that are related to  the current model.
• enable/disable fields or grids based on work-flow state.
• add static and dynamic validations for the fields.
• map actions defined in process design to form buttons.
• specify permissions statically and dynamically based on expressions/formula.

Process perspective can be used to:

• create work flow activities.
• specify activity owners – either users or roles.
• write rules to dynamically assign activity owners.
• associate different forms and queues to different states.
• create conditional branches.
• create parallel branches.
• execute actions before and after state transitions.
• routing based on level, designation and login id.

Actions perspective can be used to:

• Update the current entity.
• Create a loop which breaks on a condition.
• Search and call an action of a unconnected entity.
• Search and call parent/child entity.
• Send mail and call external web service.