Joget Workflow v6 Beta 2 Released

Check out the latest Joget Workflow v6 Beta for many new features and improvements in user experience (UX), app maintainability and performance.

Skip to end of metadata
Go to start of metadata

Overview

Joget Workflow v3 is a web platform that simplifies the process of developing workflow apps.

Unlike typical workflow engines, Joget Workflow allows IT professionals to turn their processes into a full-fledged workflow web application. With v3's user-friendly drag-and-drop user interface, developers are able to quickly design and prototype complex processes, easily create and map dynamic forms to process activities, combine forms and data listing into CRUD (create-read-update-delete) seamlessly, and assemble web UI components to create the final application front-end.

With v3's comprehensive plug-in architecture, developers are also able to easily extend the platform and integrate Joget Workflow with other systems whenever required.

What's New in v3?

A high-level summary of Joget Workflow v3's new features are outlined in the following blog posts:

App Management

  1. Joget Workflow v3 introduces the concept of apps. We create an app, and an app can contain one or multiple processes.
  2. We can create multiple versions of an app.
  3. An app is not published until the administrator publishes a specific version of the app.

Process Management

  1. Users no longer need to worry about process versioning. Based on user feedbacks, the implicit process versioning in v2 (and earlier versions) is confusing at times, as it creates a new version of the process and all of its associated forms every time the process is updated.

Workflow Designer (Enhanced)

  1. Simplified interface for all workflow objects. For example, participant types are streamlined from 6 to 2. There are 4 unsupported participant types in v2 which sometimes confuses users.
  2. Workflow variables are editable in all activities. In v2, the need to set workflow variable as "Editable" in "Activity Form Editor" is a step that a many new users tend to overlook.
  3. New "Guide" palette which shows all errors in the workflow design, as and when the process is being designed. Clicking on the "bulb" icon will help you to automatically resolve the error by applying a suggestion given by Workflow Designer.
  4. Easy-snap which makes it a lot easier to connect objects with transitions (arrow line)

Form Builder (Revamped)

We heard all your comments.  Yes, Form Builder in v2 is rather limited in a lot of aspects, and many users resorted to using Custom HTML (JavaScript and HTML) for most of the forms. Custom HTML works, but it can be messy.

Form Builder in v3 is a complete makeover of Form Builder in v2.

  1. Drag-and-drop. You decide where the new element should be positioned.
  2. Section. Section replaces Fieldset.
  3. Multiple columns in a section allows for creating flexible grid layouts.
  4. Wizard style Property Editor. While editing any element, the Property Editor is shown in multi-step wizard style to help the user understand the type of property he/she is configuring.
  5. Options Binder for multi-option elements. When configuring multi-option elements such as select boxes, check boxes and radio buttons, the property called Options Binder allows the user to choose how options are populated into the element. For example, by using "Form Options Binder", options are populated into a select box by retrieving values submitted in a form.
  6. JSON definition. When a form is being designed, its definition is formatted in JSON object form. Advanced users, however, can modify the form design by modifying the JSON definition which is copied from the JSON definition of another form.
  7. Everything is a plugin. All form elements (Load Binder, Store Binder, Options Binder) are plugins. Thus, installing a new form element in the Form Builder is as easy as installing a new plugin. To support the custom approach of storing submitted form data, one can install a compatible Store Binder plugin.

Datalist Builder (New)

  1. Datalist Builder allows users to design listing tables (i.e., list of product types, list of leave types, list of company types) using a drag-and-drop interface. 
    1. Identify the datalist that you want to create; for example, a list of product types.
    2. Using Form Builder, create and design a "Product Type Form".  This will allow you to create a new product type.
    3. Create a new datalist using "Form Data Binder" and attach the binder with "Product Type Form". 
    4. Design the columns to be shown in the listing table by dragging relevant columns from the palette. 
    5. Design the search filters to be used in the listing table by dragging relevant columns from the palette.
  2. All datalists are automatically added with support for CSV, Excel, XML and PDF exports.
  3. Everything is a plugin. Data Binder and action elements are plugins.

Userview Builder (Revamped)

  1. Design and assemble a front end application for end-users by using the following elements:
    1. Form: create a menu item that is referenced to a form to allow the user to submit form data.
    2. HTML Page: create a menu item that is referenced to an HTML content page.
    3. Link: create a menu item that is referenced to any URL.
    4. List: create a menu item that is referenced to a datalist (tabular report).
    5. Run Process: create a menu item that is referenced to a process.
  2. Support for the concept of theme.
  3. When an application is published, the Userview can be accessed from Run Apps > Published Apps.
  4. Everything is a plugin. All the building blocks of a Userview are plugins.

User Management

  1. Ability to organize user group(s) into organizations. This flexibility is added to facilitate multi-tenancy models for SaaS providers.

System Structure (Enhanced)

  1. Streamlined to 1 datasource, instead of 5 in v2
  2. Datasource.properties renamed to app_datasource.properties in v3 so that advanced users can run v3 Beta and v2 simultaneously in the same Tomcat instance.
  3. In the /wflow directory, forms, plugins and xpdlImages folders are prefixed with app_ in v3 so that advanced users can run v3 Beta and v2 simultaneously in the same Tomcat instance.
  4. URL context renamed to /jw in v3, so the default localhost URL to Workflow Management Console v3 is http://localhost:8080/jw
  • No labels