Ivalua documentation that reflects your real configuration.
Docuvara connects to your Ivalua environments, extracts the configuration and documents it with templates built around Ivalua’s data model and functional concepts.
| Environment | Last extraction | Documentation |
|---|---|---|
| DEV | 2026-10-21 07:02 | Draft |
| UAT | 2026-10-20 18:40 | Changed |
| PREPROD | 2026-10-18 09:15 | Verified |
| PROD | 2026-10-21 09:14 | Verified |
Ivalua is powerful because it is configurable. That is also why it is hard to document.
The platform
- Complex workflows and approval chains
- Detailed user profiles and authorizations
- A rich data model that keeps evolving
- Many interfaces: APIs, flat files, SFTP
- Functional logic held in configuration
Its documentation, in practice
- Spread across projects and integrators
- Out of date after each release
- Hard to read for non-technical stakeholders
- Rebuilt by hand for every upgrade or audit
- Held by a few people who know the history
A template library for every layer of your Ivalua configuration.
Each template documents a layer of your configuration in a fixed structure, so documents are comparable across environments, versions and projects. A few of the templates in the library:
| Template | What it documents | Why it matters |
|---|---|---|
| Workflows | Workflow definitions, approval steps and conditions, business rules and thresholds, actors and escalation logic, dependencies with data and authorizations. | Understand the real approval logic, prepare workflow changes safely, support audits, reduce risk during upgrades. |
| User profiles and authorizations | Profiles and roles, functional permissions, access scopes and restrictions, how roles relate to workflows. | Transparent access control, audit-ready role documentation, easier role clean-up, fewer security and compliance risks. |
| Data model | Custom and standard objects, fields and attributes, types and constraints, dependencies with workflows and rules. | A clear view of functional data, safer configuration changes, better integration design, faster impact analysis. |
| Interfaces and integrations | Inbound and outbound APIs, SFTP flat files, data mappings, triggers and schedules, error handling. | Faster incident resolution, clear interface ownership, lower integration risk, easier onboarding of third parties. |
Also in the library
- Screen definitions
- Object statuses
- Process alerts and email notifications
- API documentation and interface mapping
Your own templates
Create new templates, duplicate an existing one or adapt it to your standards, to cover almost any documentation need.
Every document explains how to read it.
Ivalua configuration can be overwhelming. Each Docuvara document opens with a reading guide, so a buyer, an auditor and an integrator each know where to start.
How the documentation is structured
The logical organisation of your Ivalua documentation.
How configuration layers relate
The links between workflows, rules, roles and data.
Where to start, by role
An entry point for IT, functional teams, auditors and integrators.
How to use it for your goal
Upgrade preparation, audit, handover or day-to-day support.
Typical Ivalua projects, and who they serve.
Projects
- Ivalua version upgrades
- Audit and compliance preparation
- Handover between integrators
- Knowledge transfer between teams
- Rationalising a complex configuration
- Incident analysis and troubleshooting
People
- Ivalua customers, IT and functional teams
- Ivalua project owners
- System integrators and consultants
- Audit and compliance teams
See Docuvara on an Ivalua configuration.
No reverse engineering, no screenshots, no guesswork.