DMS integration¶

Admin → DMS groups the entry points of the Lurana DMS integration. The section appears only when the integration is installed and enabled; on a workspace without it, there is nothing to configure and no menu entry.

Page	Use it for
luranaDMS Config	The DMS connection and shared settings
Processes DMS	How individual BPM processes behave with DMS
Sync monitor	Synchronisation activity and errors
Debug	Diagnostic routes, for troubleshooting

What the integration does¶

It connects BPM cases with document management. Depending on the configuration, BPM can send documents to DMS, read case data from DMS, and show DMS views inside BPM.

The integration is a plugin: if it is disabled in Plugins, this section disappears even though its data remains.

Configure the connection¶

luranaDMS Config holds the connection details and the options the integration needs. Treat it as credentials: the user configured there decides what BPM can do in DMS, so use a dedicated account and the minimum access.

Configure it per process¶

Processes DMS decides how a given process behaves: whether it uploads to DMS, which document groups and types it uses, and what happens when the case is cancelled. Two processes can behave differently, so check this page before assuming a behaviour is global.

Follow synchronisation¶

Sync monitor shows synchronisation activity and the errors. When a document does not appear in DMS, this is the first place to look: it distinguishes "the queue is behind" from "the case was never sent".

The DMS side¶

This section configures the integration from BPM. The DMS application has its own documentation, including its Documents, Explorer, Administration, and API areas — see Lurana DMS.

Permissions¶

This section requires administrative permissions together with the integration's own permissions. See Permission reference.

Plugins — enabling or disabling the integration.
Roles — the permissions the integration publishes.
Lurana DMS — the product on the other side.