All components

SIFYBOX · OOD

Document workflow and organisation

SIFYBOX's flagship workflow component turns a form, document or request into a controlled case. It manages steps, roles, deadlines and audit and connects the case to the organisation's registries, finance, signing, storage and records systems.

Crayon story for OOD: Document workflow and organisation

Directly from the application

Take a look inside.

We use real application screens only. Published captures are cropped or anonymised so they do not contain personal or sensitive operational data.

A real OOD purchase-request form
OOD · Form

Purchase request

The real form keeps supplier, delivery, payment, line items and funding sources in one case.

A real OOD purchase-request transition definition
OOD · Definition

Purchase-request transitions and responsibilities

The definition shows source and target states, the user action and how the approver is selected.

An anonymised launchpad for OOD process agendas
OOD

A launchpad for real agendas

Users enter contracts, projects, signing and other workflows from one place.

A real OOD request workflow visualisation
OOD

A case workflow

States and transitions show where the case has been and which steps can follow.

From input to outcome

How OOD handles its input.

01

Input

Dynamic form and attachments

API and reference data

User identity and roles

02

Processing

Validates required data

Controls states, transitions, roles and deadlines

Creates tasks, notifications and subprocesses

03

Output

Decision and new status

Data for DOG, FS, EPK or CUL

Case audit history

Capabilities

What OOD provides.

  • 01State-aware configurable forms
  • 02Multi-step workflows and subprocesses
  • 03Roles, visibility and validations
  • 04Stable GUID and audit history
  • 05Reference data, registries and exchange-rate sources by deployment
  • 06Document and metadata hand-off to a supported records system

Where it is used

Typical scenarios

Invoices and purchase requestsContracts and internal policiesTravel and HR workflows

Who works with it

Roles

Operations specialistProcess ownerAdministrator and implementation partner

Connections

What it connects to

REST APIDOG · FS · ZSTEPK · CULEIS · eSSLARES, číselníky a další datové zdroje

Related components

Components can run independently or be combined into one solution for a specific workflow.

PreviousSOPHOSPilot for social-care providersNextDOGDocument generation