Description:

This step checks whether the DMS documents exist and retrieves the Document ID.

Usage:

Example:

Let’s build and execute the “DMSDocumentExistDef” example:

• Create a new process definition named “DMSDocumentExistDef” and open it in designer mode. 
• Drag a “updateVariables, DMSDocumentExist” step to the canvas.
• Connect the dots between the “Start” and other steps, as shown above. 
• Define a variable or global reference to store the document name and ID.
• Click the "updateVariables" step to configure its "Required" properties. Provide a name for the step.

• Click the "updateVariables" step to configure its "Optional" properties. Provide a variable or global reference to store the document name. Set “Has Expression” to “No” if the value is not a C# expression. Click the Save button. 

• Click the "DMSDocumentExist" step to configure its "Required" properties. Provide a name for the step. Click the button to select the DMS parent folder from the drop-down list. Provide the variable or global reference that contains the document name and stores the document ID. Click the Save button. Note: Click the "AI Predict" button to have Copilot add new process steps that match your process description. 

• Click the button to select the DMS folder from the drop-down list. A pop-up window is displayed for configuration. Alternatively, you can use the filter to select the folder or provide a variable or global reference that contains the DMS folder ID. Click to expand or collapse the DMS folders. Select the folder and click the Save button. 

• The “Logging” setting configuration is necessary for documentation and also measures workflow progress and completion percentage. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and then execute it. Render the process instance to note that the status is completed. Select the Items - Latest variables menu. As observed, the process step verifies that the documents exist and stores the “Document ID” in a variable or global reference. 

• On the DMS page, navigate and select the actual document used in this example. Click the ellipsis button for context features. Select the “Get URL” menu. 

• A pop-up window displays the document link, and the GUID matches the variable or global reference. 

Definition Sample:

You may download the sample definition(s) from the link here and later import them (drag-and-drop) to your FlowWright Process Definition (XML file) or Form Definition (HTML file) page. 

Note: Please verify and complete any missing configuration steps after import, such as file path references and database connections. Then, save the definition to confirm the changes. 

Click here to download the sample file.