Users and permissions
We handle identity synchronisation, groups and access configuration. The design also covers account changes and unavailable identity sources.
ELO extensions for repeatable tasks
Avoid solving the same user, access and document operations repeatedly. We develop components for ELO automations and business applications.
Metadata and document operations
Components can check data, process document batches or prepare the next operation. Batch processing includes result tracking and exception handling.
Custom steps in ELO Flows
Extensions become reusable automation steps. We document configuration, permissions and dependencies for deployment.
Development with clear documentation
Each delivered extension needs an owner and an update procedure. These are prepared alongside the functional solution.
Frequently asked questions
How do workflow and ELO Flows differ?
We use workflow mainly for user tasks, handovers and decisions. ELO Flows connects automation and integration steps. They can complement each other according to the process and available components.
What does ELO Metadata 2.0 add?
It supports structured data models and reusable parts through aspects. This helps align data across applications. The model still needs to fit users' work and the interfaces that depend on it.
Who can see sensitive documents?
Access is configured by role, group and application. Checks should include previews, exports, service accounts and role changes. Hiding a menu link is not an access control.
Are all demonstrated modules included in the base licence?
Licensing and delivery scope are defined in the proposal. Distinguish the ELO platform, custom modules, integrations and third-party services. Demonstrated functions are mapped to specific items when preparing an offer.
What happens when a connected system is unavailable?
The integration should record failure, distinguish temporary issues and support safe retry. Depending on the scenario, use a queue or a controlled error response. Keep track of what has already been processed.
What should system handover include?
Configuration, interfaces, roles, operating procedures and custom-extension documentation, as well as the application. Agree administrator access, backup, support and upgrade arrangements in the requirements.