Welcome > Process Designer module > Document set

Document set

A document set is a group of related documents that can be managed either individually or as a single entity. You can specify in your process whether to use a document set.

Note TotalAgility only supports a document set in parent processes, case fragments and cases; it does not support processes that contain a document set as a subjob or embedded process.

Using a document set, you can do the following:

  • Define the type of document.

  • Restrict certain document types from display.

  • Configure basic or advanced rules for a document set so that a process can only continue once certain criteria are met. Configuring document set rules gives complete visibility to the status of the documents required to complete a process. You can halt the process if the required documents are not received. For example, halt the process at a stage until document 1 of type A and 2 of type B are received.

  • Specify which documents are involved in a process and provide the number of documents, document type, whether required or optional, and dynamic rules on metadata, such as paystubs for the last three months.

  • Specify the process on which a job is started at runtime when a document of the selected document type is uploaded.

  • Configure exceptions to raise at the specified interval when the document date elapses.

Note The Update Document Set user rights are required to update the runtime status for a document rule.

See Configure a document set.

TotalAgility provides document set control used to display the following:

  • Document set at runtime.

  • Summary of document types in the selected mode. The summary is displayed based on the mode of operation (Customer or Case Worker) selected at design time.

See Document set control.

Within processes, you can define conditions based on the document set or one of its document types. For example, you cannot send the application for approval until all document requirements have been met.

Set the document set properties as input (not output) to an activity. See Activity input and output.

When you skin a process, you can overwrite the rules associated with the document types.

When a process is exported and imported, the document set, associated extraction groups, and the Update Document Set functional access are maintained. When documentation is generated for a process, this data is included in the output.