Document set

A document set is a group of related documents that can be managed either individually or as a single entity. You can configure a document set in your process, case definition, and case fragment.

Using a document set, you can add documents and define document rules to the document set and determine whether the document set is valid. For example, you cannot send the application for approval until all document requirements have been met.

A document set rule gives complete visibility to the status of the documents required to complete a process. For example, a document set rule can be used to halt the process at a stage until documents 1 of type A and 2 of type B are received.

When the document set is turned on, you can use the document set properties (read-only) when configuring a decision, activity, and exit condition. You can make use of the Valid (Bool) and Comment (String) and Count properties of the document set within the variable selector. If a document set within a case definition is turned on, you can access the document set properties in a decision for the case fragment (Case document set). For example, you can use the Valid property in a decision or use the Comment property as an input to a manual activity that is requesting more documents from the customer.

A document set is not supported in a synchronous process. You cannot use a document set enabled process/case as an embedded process or subjob.

On upgrading TotalAgility from 7.8.0 or importing a process that makes use of the document set (from TotalAgility 7.8.0):

A message displays stating the process contains unsupported nodes and you are not allowed to save/release the process until the unsupported nodes are removed.
When you execute a process containing these nodes, it will fail.
Document set fields used within the document type rules and activities do not work at design time and runtime.

How to: configure a document set