If this workflow uses Web Services operations that might include incoming attachments, specify a folder in your object store or library where these files will be stored.
To enable error checking for XML messages, select Verify messages at runtime.
When this option is enabled, the following messages will be verified against the schema in the WSDL:
Since this option can be set in FileNet® workflows that contain Invoke functions and workflows that contain Receive functions, the table below outlines when verification will occur.
Invoking workflow | Receive workflow | Result |
---|---|---|
Yes, verify messages | Yes, verify messages | Invoking workflow verifies both the outgoing message to the web service, and the incoming message from the reply. If the web service is provided by an external source (not a FileNet workflow), the invoking workflow verifies both the outgoing and incoming messages. Receiving workflow verifies the incoming (invoking) message. See note below. |
Yes, verify messages | No, don't verify | Since the receiving workflow will not verify the message, the invoking workflow does not verify. |
No, don't verify | Yes, verify messages | Invoking workflow does not verify either the outgoing or incoming messages. Receiving workflow verifies the incoming message. |
No, don't verify | No, don't verify | Neither workflow verifies the messages |
If the message contains an 'attachment by value', or if the message is RPC style, the message is not verified.
By default, this option is enabled except for workflows developed using previous versions of Process Designer. This allows previously defined workflow to continue to run, even if a schema is not valid.
When this option is not enabled, any errors in XML messages will go undetected until a process attempts to use the data, then the web service might generate a fault, or a process might generate an exception or end in an unpredictable manner.
While you are developing a workflow that provides a web service, a workflow with Receive and Reply system functions, you will usually revise the Receive and Reply operations a number of times—the input and output parameters for the Receive and Reply operations can change with each revision of the workflow. During this development period, you should not select the Finalize existing web services operations option.
If you develop a separate workflow that invokes this web service during this development phase, the partner link in the invoking workflow identifies a specific version of the workflow that provides the web service. This ensures that the input and output parameters match between the web service and the invoking process. When you modify the workflow with the Receive and Reply system functions, you must update the partner link in any processes that invoke those web services if you want to invoke the latest version of that web service; you might also need to update input and output parameters if they have changed in the latest version of the web service.
When you are satisfied with the input and output parameters of Receive and Reply operations in a workflow, you can optionally finalize the web services in the workflow by selecting the Finalize web services operations option on the Web Services General tab. This has the following effects:
TIP While you cannot change existing Receive and Reply operations, you can add new Receive and Reply system functions, but the input and output parameters for these new web services will be final after you transfer the workflow definition.
To finalize the input and output parameters of existing Receive and Reply operations:
This option takes effect when you transfer the workflow definition.
After you enable the Finalize option and transfer the workflow providing the web services to workflow system, you can update the Partner Links in any workflow that invokes these web services so that it will run the latest version. If you subsequently make other changes in the workflow definition that contains the Receive and Reply system functions, any invoking partner links will always run the latest version.
CAUTION After you transfer the workflow definition with this option enabled, you cannot disable this option in the workflow definition.