History

Eazflow - Documentation - Quick start

Step by step instructions for creating Eazflow-based Grails application

Prerequisites

Creating the ''eazdemo'' application

  • Create new Grails-application named ''eazdemo'' (you may, of course, use another name for it)
1 grails create-app eazdemo
2 cd eazdemo
3 grails install-plugin modalbox 0.3                     # updating plugins list cache may take some time
4 grails install-plugin richui 0.6
5 grails install-plugin ../grails-eazflow-0.1.zip        # yes, that is our plugin downloaded above
  • Optionally: Put content of `grails-app/conf/EazflowConfig.groovy` into `grails-app/conf/Config.groovy`
  • Optionally: Configure `grails-app/conf/DataSource.groovy` (defaults should be OK for demonstration purposes)

Run the application

  • Start grails application
1 grails run-app

(give it some time for initialization)

Application description

On the ''worklist'' page, you should see an (initially empty) ''List of processes''.
On the top of the page there are ''demo login'' links, allowing you to login to the system easily.

Eazflow manages long running ''processes'', consisting of ''activities''. In each ''activity'', a ''user'' may read or edit a set of ''variables'', and then choose a ''transition'' into another ''activity''.

There is a predefined ''Ticket'' sample process where:
  • Logged-in users can create a ''ticket'' (Start new process: Ticket), fill in the form and ''Submit'' the ''ticket'' for further processing
  • The manager (''mng'') processes submitted ''tickets'' and assigns a ''worker'' user to each one of them (clicking ''Assign'' for next step)
  • Assigned ''workers'' process the ''tickets''...
  • Note the different access rights (to displayed variables, activities, transitions) applied for different roles, some of which are dynamically assigned according to filled-in values (e.g. ''worker'')

The ''Ticket'' process presented is very minimalistic, meant for the demonstration of ''Eazflow'' plugin abilities only. It can be simply extended (adding variables, activities, transitions and access rules) by data-based process definitions.

Inspect `grails-app/services/EazflowBootStrapService.groovy` for the data definitions used in this example.

Also available in: HTML TXT