Automation and electronic identification
Automatable processes
Customisable automations at countless points of the platform — the task, the notification and the next step start on their own.
What does it solve?
BEFORE
- Someone has to remember the next step of the process: tell people, remind them, follow up.
- Every colleague does the same task slightly differently.
- Exceptions are handled informally: decided by phone or word of mouth.
AFTER
- The system starts the next step and notifies the owner.
- A standardised workflow — the same path for everyone.
- Exceptions are a defined branch too, logged and approved.
How does it work?
-
Capture the process
Record the steps, owners and deadlines as a template.
-
Set the trigger
What starts it: a document, an e-mail, a status change or a schedule.
-
Run the automation
Task assignment, notifications and document generation happen on their own.
-
Measure and fine-tune
Fix bottlenecks based on the statistics.
Capabilities
-
Condition-based branching
Data-driven paths, with exception handling.
-
Scheduled start
Recurring processes on a calendar.
-
Automatic notifications
E-mails and system messages to owners.
-
Processes started from templates
A new case in one click, with a ready sequence of steps.
What exactly is included?
The configurable elements of the feature and the process steps in detail.
- Conditions and branches — the process takes a different path depending on the data.
- Exception handling: a defined branch and approver for cases that deviate from the rule.
- Measurement: lead time and stopping points per step, for fine-tuning.
-
GOOD TO KNOW
Processes are customisable — they require configuration, not development.
The same engine runs document management, HR and finance approvals. Automations can be changed later without losing running cases.
-
WHERE DOES IT APPEAR?
Document management
Approvals HR processes Invoicing
1 / 2
A process editor based on configuration, not development Steps, conditions and automatic actions can be put together in the interface. Branches are based on the case data, so exceptions remain part of the process — running on a defined branch instead of by e-mail. Changes do not disrupt cases already in progress.
2 / 2
Measuring lead time step by step The start and end of every step are logged, so you can show where work stalls. The bottleneck can be fixed in the editor immediately, and the result is visible in the very next cases.
Tudja már, min változtatna?
Senior tanácsadóink 24 órán belül felveszik Önnel a kapcsolatot.
Kérjen demót