Live Processes

<< Click to Display Table of Contents >>

Navigation:  Bizagi Work Portal >

Live Processes


Bizagi lets you create and manage non-complex processes directly in the Production Environment and through the end user's Work Portal.

With Live processes, process owners can build and launch simple process applications created with no coding effort.


This feature is useful for non-complex, day-to-day manual processes when formal process architecture oversight is not required.

The tool is oriented to non-technical users, so they can create an easy and ready-to-use executable Bizagi Process.


Why Live Processes?

Within enterprises today there are hundreds of low level manual processes that could and should be streamlined.

Most of the time these processes are viewed as being “too small” to be addressed by the IT/processes team but could deliver significant benefits to the business if automated, providing efficiency, control, governance and agility.


Without automation, these processes remain paper-based, in email or in a spreadsheet. Continuous manual maintenance incurs costs and risks and reduces operational agility.

Live Processes offer an extremely intuitive yet powerful approach to automating these processes in the run-time environment They require no input from IT, no deployment and no prior development experience.


Using Live Processes

Here is how you would work with Live Processes:

1. Access the Bizagi Work portal in the Production environment.

2. Design a new process using the Live Processes management options.

3. Promote your process when it is ready (publish it after having verified it behaves as expected).


Explicit benefits

Live Processes bring the following benefits:


Achieve fast results

You can quickly and effectively create and publish to production non-complex processes, with no deployment required.


Code-free forms

Build user forms with a drag and drop interface that lets you include attributes and controls – it’s very simple.


Easy updates and changes

You can easily make changes to your process and publish them quickly.


In the table below, note the differences between building processes with Live Processes, and the traditional way that uses Bizagi Studio.

These differences reflect faster results and involving less resources (a fast track) with Live Processes, regarding a process's time to market:



Build the process

Deploy for testing

Adjustments, iterative round-trip modeling

Deploy for production*

Traditional process life cycle

On a machine where Bizagi Studio is installed

Perform a Studio deployment to a different environment (coordinate and plan with the team)

Make changes in the Studio's Development environment and re-deploy

Perform a Studio deployment, while planning for maintenance downtime

Process life cycle with Live Process

Using a browser having access to the production Work Portal

Change the initial Draft state of the process to Pilot

Change the Pilot state to Draft, make changes and change it back to Pilot

Change the Pilot state of the process to Published


* You should always communicate and coordinate your deployment, and plan it for non-busy hours. Take proper precautions such as making backups just as with the traditional process life cycle. However, the actual process roll-out to production will cause absolutely no downtime for the Work portal.


Further information

To learn how to get started with Live Processes, refer to Designing Live Processes.