Question & Answer
Question
Is there any built-in way that a PE workflow can detect if an attachment is null?
Cause
A user gets "Unable to use the specified VWAttachment library type 0 to determine the loading class that implements the operations." error with the Component Manager step. This error occurs because a CE_Operations operation requires a document attachment during runtime to do its operation, but the attachment is invalid/null or not available. In this scenario, the affected work item would be sent to the malfunction queue. If you do not override the default malfunction submap in your workflow, the affected work item would be sent to the Conductor queue as it is the default malfunction queue.
Answer
To check if the attachment is null, you can carry out the following steps:
- Declare the following two fields in your workflow as follows :
blank_att - Attachment
EMPTY_ATTACH_CONST - String - In the launch step, assign the EMPTY_ATTACH_CONST the value of the attachment as follows:
EMPTY_ATTACH_CONST = blank_att - Then, when you do conditional routing later, you can just compare the CE_Operations attachments to this EMPTY_ATTACH_CONST.
For example, if you CE_Operations uses an attachment field named 'document_field1'. Then, the Conditional Routing expression would be:
document_field1 = EMPTY_ATTACH_CONST
See the attached related sample workflow.
searchforonetest.pepWas this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21640823