A feature of low-code BPM is the ability to create and modify workflows and business processes. Ideally, a low code BPMS will include a visual workflow designer which is capable of automating all workflows and processes, including triggering the creation of associated tasks and notifications.
In most cases, this ability does not require specialist coding or development skills, unless there is a level of integration with other systems within the organization.
Essentially, the features you should expect will include:
A visual workflow UI with the capacity to create and modify simple and complex workflows.
- Automatic approval of workflows and business processes.
- The ability to allocate resources to complete the associated tasks which constitute the workflows, and to do this automatically.
- The automatic routing of tasks to assignees or teams, and of notifications to the appropriate supervisors and managers.
It is not enough to be able to create workflow processes – this is done all of the time – however the power of BPM is unleashed when it is the operations staff who actually wield the functionality of a BPMS. This means your business analysts, team leaders, operations staff, process improvement professionals are given the power to not only design workflows and business processes within the BPMS, but are also able to push them into the live, operational environment without the need to involve the IT department.
The workflow software should be simple and easy to use by non-technical staff, such that they can easily create and modify business processes. This removes the time lag many businesses must endure when operational staff identify a process improvement, but then must wait until IT or external specialist partners work on creating the code to execute the business process and make it live.
Process owners should be able to implement workflows quickly, not only creating them, but also changing them as required, without programmers or specialist coding skills.
The BPMS should therefore have extremely broad integration capabilities, an easy to understand and use set of workflow rules which allow for rapid change, and be permission based.
Managers spend a great deal of their time dealing with approval requests.
Automating approval requests involves: ensuring approvals are sent to the correct approver, automating emails, utilizing preset rules to approve or deny requests, and then route the task on to the next stage in the workflow.
The BPMS should therefore have the following as a minimum:
- Custom fields (which can be easily and quickly changed) to hold the information relevant to the process request.
- Automatically updates task and approval statuses.
- Automatically triggers email notifications and alerts.
- A set of preset rules to automate approvals and trigger appropriate responses when a request is denied, plus route approved requests to the next stage/person in the workflow.
A low code BPMS should have the ability to automatically create notifications and alerts, and then escalate the issue to the appropriate manager. In addition, the platform should also automatically route tasks which are on track to miss deadlines to staff with workload capacity, raise the alert level of the tasks and associated work, and create new tasks and assign them as required,
There should be:
- Missed milestone notification and automatic email alerts.
- Reassignment of tasks and resources to senior staff and/or managers automatically.
- Create and assign new tasks to managers to intervene where a project is in danger of going off track.
- Upgrade alert levels for projects and tasks automatically.