System and Document Actions in v5.2

Building Lifecycle Applications for v5.0



DocuNECT has the ability to manage system-wide actions and document level actions. The following screenshot shows the Actions page in the designer that allows you to switch between both types. There are no built-in system actions as this is exclusively used with Lifecycle Applications. There are a number of built-in document actions.

actions.png

Document Actions

DocuNECT has a number of document actions built into the system, as well as allowing for custom document actions to be created.

Built-In Document Actions

The following list details the built-in document actions.

Building Lifecycle Applications for v5.0



DocuNECT has the ability to manage system-wide actions and document level actions. The following screenshot shows the Actions page in the designer that allows you to switch between both types. There are no built-in system actions as this is exclusively used with Lifecycle Applications. There are a number of built-in document actions.

actions.png

Document Actions

DocuNECT has a number of document actions built into the system, as well as allowing for custom document actions to be created.

Built-In Document Actions

The following list details the built-in document actions.

Field Name Description
Create Document Document is created.
Open Document Open the document.
Download Document Download the document.
Edit Document Edit the document's index values.
Checkout Checkout the document.
Checkin Checkin the document.
Undo Checkout Undo checkout.
Delete Version Delete a document version.
Email Document Send the document by email.
Email Document Link Send the document link by email.
Move Document Move the document to another batch.
Request Action Request a custom action for document.
Delete Document Delete the document.
Add Comment Add document comment.
Add Annotation Add document annotations.

The following list details the built-in document workflow actions:

Field Name Description
Approve Task Approve a document related workflow task.
Reject Task Reject a document related workflow task.
Complete Notification Confirm the receipt of a document related workflow notification.
Confirm Signature Confirm the signature on the document in a workflow task.
Complete Routing Complete the document related workflow.

The following list details the built-in document indexing and classification actions:

Field Name Description
Escalate Document Escalate the document during indexing.
Verify Document Verify the document's index values.
Index Document Index the Document.
Change Cabinet Move the document to another cabinet.
Indexes Accepted Indexes accepted by the user.
Classify Document Classify the document.
Lifecycle Processing Automate document updates through the lifecycle.

Hooking into An Existing Document Action

If you wanted to write a custom process to update a third-party system with document index data that has been changed. By default the built-in document actions do not trigger a request, so you would need to edit the action and set the Trigger Action Request to Yes. The following screenshot shows the action page. Note, all fields a disabled except the Trigger Action flag.

editindexesaction.png

Changing the Trigger Request flag to Yes will create a request in the documentactionrequest object accessible by via the API. A Custom Content Connector can then be developer to process the transactions and perform the necessary function.


System Actions

System actions follow the same principle but are system-wide and not document related.

Hooking into An Existing Document Action

If you wanted to write a custom process to update a third-party system with document index data that has been changed. By default the built-in document actions do not trigger a request, so you would need to edit the action and set the Trigger Action Request to Yes. The following screenshot shows the action page. Note, all fields a disabled except the Trigger Action flag.

editindexesaction.png

Changing the Trigger Request flag to Yes will create a request in the documentactionrequest object accessible by via the API. A Custom Content Connector can then be developer to process the transactions and perform the necessary function.