Form Processor Node
This node is available for GlobalCapture and GlobalAction workflows and can be downloaded from the Square 9 Solutions Delivery Network.
This node is a simple way to initiate a GlobalForms process and pass it data. More complex GlobalForm initiation processes can by created using the iPaaS node. Check our our iPaaS knowledge base article or reach out to your Square 9 representative for more information about capabilities.
You will need enough form licenses to support whatever supplemental processes are required when using this node.
From a GlobalCapture workflow, trigger a a new form submission or delete an existing form submission. Choose what fields from a workflow get sent into specific form components. Documents from a capture process can also be attached to the submission.
Forms Processor Node
Node Properties
Form Process Node Settings
Title
The Title of your node should be brief but descriptive about the form being created or deleted. Titles are important when revisiting workflows in the future and when migrating workflows. The title of the node will be displayed when resolving conflicts during imports.
Description
The Description of your node should provide notes about this node. This could include information about intended use, form being created or deleted, the data being passed, the step of a larger process, etc. Descriptions can be very useful when revisiting workflows in the future.
Data Validation
Data Validation is only available in GlobalCapture.
The Data Validation checkbox is enabled by default to enforce Data Types or Length settings for Fields. When enabled, if data does not meet the type or length settings for the field, the process will error on this node.
GlobalForms URL
A valid GlobalForms instance is required. Provide the address, with no trailing slash, in the GlobalForms URL field. Your URL should look similar to those below:
Cloud: https://myinstancename.mysquare9.com:5454
On Premise: https://domainNameOrIPAddress:3001
Form Name
This is the name of the form to be created or deleted and is represented by the Path property in GlobalForms.
The Path property can be found at the top of the form on the Edit Form tab.
GlobalForm Path Property
User and Password
Used to notate a user that has administrator permissions to GlobalForms. This user will need to have access to the form indicated in the Path.
Create Submission
Attach Document to Form Submission
Attaches the document currently moving through the capture process to the newly created GlobalForms submission.
Add creator permissions for user:
This is the Name of a user who the submission will be created on behalf of, as if the user submitted it themselves.
This needs to be in the form of an Email address.
This field does accept S9 Notation.
The creator MUST exist as a user in GlobalForms.
Process Fields
The GlobalCapture process fields that contain data from the capture process. This data can be used to populate data on the newly created form by linking the process field to the API Key.
Create Submission
Form API Keys
The unique identifier for each component on a form. This can be found under the Property Name on the API tab of the component settings window.
GlobalForms Component Settings Window
Delete Submission
Submission ID
The Submission ID is a unique ID given to each GlobalForms submission. This field accepts S9 Notation.
The Submission ID of the form currently being processed can be accessed using {SUBMISSIONID}.
If the Submission ID is left blank, no submission will be deleted.
Delete Submission
Outputs
Submission Processed
The Forms Processor node successfully achieved the desired action of form creation or deletion.
Submission Processed
Submission Processing Failed
The Forms Processor node was unsuccessful in creating the new submission or deleting the indicated submission.
Investigate the issue by selected the Forms Processor node from the History tab of the process drawer in GlobalCapture Validation.
Submission Processing Failed
Process History
Uses
Use cases revolve around scenarios where one workflow process needs to start another.
Generating a PO when there is none present for an invoice and feeding the data from the invoice into the PO to start the request.
