Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
  • Form and Document Actions functions for workflows are very similar to those for forms. The term "Form Actions" used on this page also refers to "Workflow Actions".
  • Forward to PayPal is not available in workflows, but can be configured following this documentation.
  • Document Actions that happen in between steps are known as Activity Doc Actions. See the Email & Webhook documentation for details.

Form/Workflow Actions

The Form/Workflow Action wizards help set up what the user sees when the form/workflow is submitted. You can access the Form/Workflow Action tab in the Guided Designer Settings mode.

...

You can only configure one Form action for a form/workflow. This is as designed.

Success

The Form Actions available on the Success tab are:

  • Display Message when User Submits Form

  • Forward users to a web page of your choice

  • Post data and forward users to your web page

  • Forward to Paypal to complete payment

Display Message when User Submits Form

After the user submits the form/workflow, the browser will display a standard  page with a text message. For example, the message might say, “Thank you for completing our form.” You supply the specific text in the Message field. This option works best for relatively brief messages. It can be tricky to enter or edit large amounts of text in the wizard's Message field, so for verbose messages consider creating a simple HTML page for your message and choosing the Forward User to your Web Page wizard.

...

  • Frame means inside the form's iframe
  • Parent means inside the form iframe’s immediate parent
  • Top means at the top of the page, regardless of how many parents are outside the iframe.

Forward Users to a web page of your choice

After the user submits the form/workflow, the browser will be redirected to another URL, which you supply in the  URL field. You must include the http:// prefix (e.g., http://myhost.com/thankyou.html). The project can have a Form Action Base URL which you set in the project properties. For example, you can have http://myhost.com/ in the project  baseURL and simply “thankyou.html” in the Form Action URL field.

...

Note

Forwarding users to a web page that is located in a different domain will not work.

Post Data and forward users to your web page

After the user submits the form, the browser will POST the user’s data to the URL you specify in the wizard’s URL field and display whatever is returned—the next page to display.

...

Note

Forwarding users to a web page that is located in a different domain will not work.  

Forward to Paypal to complete payment

When the form is submitted, users will be forwarded to Paypal to complete payment. This multi-step wizard guides you through configuration:

  • Paypal account login
  • Paypal invoice description based on form values
  • Paypal payment amount from form values

and more...

Paypal for Workflows

Workflows do not have a corresponding "Forward to PayPal to complete Payment" action. However, you can configure either the Workflow Action: Forward users to a webpage of your choice or a link control in an individual step to connect to PayPal from a workflow. 

...

Production: https://www.paypal.com/webscr/webscr?cmd=_xclick&business=<Paypal business name>&amount=<Payment amount>&item_name=<Payment Description>&currency_code=<Currency Code>&return=<Return URL>&cancel_return=<Cancel URL>&custom=<Custom Value>&invoice=<Invoice Value>&notify_url=<Notification URL>

URL Parameters
  • Paypal business name: Paypal business name. Typically, this is the email address you use to sign in to Paypal.

  • Payment amount: The payment amount.

  • Payment Description: The payment description is what your users will see when paying.

  • Currency Code: The currency code used in payment. Example: USD, CAD, INR

  • Return URL: A user will be redirected to this page after payment is complete. If you leave this blank, users will be redirected to a standard platform URL. 

  • Cancel URL: A user will be redirected to this page if payment is cancelled. If you leave this blank, users will be redirected to a standard platform URL.

  • Custom Value: PayPal will return this custom value in the IPN as well as the acknowledgement email.

  • Invoice Value: PayPal will return this invoice value (such as an Invoice Number) in the IPN as well as the acknowledgement email.

  • Notification URL: A notification URL. If you enter a URL here, PayPal will notify you using Instant Payment Notification. Please see the PayPal documentation for details.

Workflow Action: Forward Users to a Webpage of Your Choice

Open the workflow properties, and select the Workflow Actions tab. Click the Forward Users to a webpage of your choice radio button. Add the URL (configured like this example) to the URL field. After the last step is submitted, the user will be redirected to PayPal for payment processing.

...

Note

This example uses the raw share link for the workflow in the &return= and &cancel_return= URLs. These will redirect the user to a new instance of the workflow. 

Individual Step

If you need PayPal integration in specific step of a workflow, add a link control in that step with above URL and set return URL pointing back to current step of the workflow using built-in data. They can then submit the step and the workflow will continue as designed.

Example: https://www.sandbox.paypal.com/cgi-bin/webscr?cmd=_xclick&business=mycompany@gmail.com&amount=2&item_name={BMyDesc}&currency_code=USD&return=http://localhost:8080/frevvo/web/tn/{form.tenant.id}/u/{form.user.uuid}/app/{form.application.id}/flow/{flow.id}/current?typeId={flow.type.id}&cancel_return=http://localhost:8080/frevvo/web/tn/{form.tenant.id}/u/{form.user.uuid}/app/{form.application.id}/flow/{flow.id}/current?typeId={flow.type.id}&custom=123&invoice=123&notify_url

Error

These wizards optionally allow you to customize what the user sees if an error occurs. You can either display a message or forward users to a web page of your choice. The wizards behave exactly like the corresponding Form Action wizards above. The Display message can be customized to display the actual error that occurred by adding the special {_frevvo_root_cause_msg} template to your message text. This is helpful for debugging, especially if your are using  Online.

Display Message if an error occurs

Forward users to an error page of your choice

Document Actions

The document action wizards configure what happens to the entered data when a user submits your form/workflow. You can access the Document Actions tab in the Guided Designer Settings mode.

...

  • Send Documents
  • Send Data
  • Additional Email

Send Documents

Using this wizard you can:

...

Info

Doc action wizards are single select. If you set up one of the wizards then configure an action using a second wizard, the information configured on the first wizard will no longer display. This is as designed.

Let's say you want to send an email after your form/workflow is submitted but you are also using the Filesystem connector to save your submissions to a directory on a local server. You configure the Filesystem connector wizard to do this. Then your configure the Email data to a specified address wizard to send the email. If you return to the Filesystem connector wizard, after configuring the email wizard, the information that you entered on the Filesystem connector screens will no longer display. In this situation, you can use the email wizard on the Additional Email tab to configure your email

Do Nothing

This is the default option, which simply stores the data in ' submissions repository. (The other options also store the data in the repository but provide additional functionality.)

...

Note
The form's save property controls whether or not your form submission data is also stored in ' submission repository

Send Email

When the form/workflow is submitted,  will send an email message with the following selectable options attached. These include submission data,  an XML document, an image of the filled form/workflow, attachments uploaded to the form/workflow and any, all or none of the Generated Forms (mapped PDFs) associated with your form/workflow.

...

See Email Integration for further details.

POST data to your web application

When the form is submitted,  POSTs the document set to the specified URI and ignores any returned XHTML or redirect. This option may be used for additional processing of data. Use form action post if you want to both submit data to your URI and forward to a web page or display returned XHTML.

...

Info

If a form is configured to Post Data to a web application and it does not reach it's intended destination successfully, notifies the tenant admin of the failure via an email. If there are users given the workflow admin permission for the workflow, they will receive the email instead of the tenant admin.

Send to Google Drive

Insert excerpt
Save your documents to Google Drive
Save your documents to Google Drive
nopaneltrue

...

See Google Connector for full details. Also refer to the Leave Approval Workflow Tutorial for step by step instructions.

Send to File System

The Save to Filesystem wizard is used to connect forms/workflows to the frevvo Filesystem Connector. The connector saves submissions in a specified location and can be configured to create metadata files for importing your submissions into a document Management system.

...

Refer to the Filesystem Connector chapter for the installation and configuration details plus information about using the Save to File System wizard and generating metadata.

Send to SharePoint

Connecting your forms/workflows to your SharePoint site is easy with the Save to SharePoint wizard. Your tenant must be configured for SharePoint in order for this wizard to display.

...

Refer to the SharePoint Connector chapter for configuration details and more information on the Send to SharePoint wizard.

Send Data

Using these wizards you can:

...

The Send Data wizards enable you to manually set a URI to which the data will be sent when your form is submitted.

Do nothing

This is the default option. Selecting Do nothing will also clear the other options if they are set.

Post Submissions to a Google Sheet

 supports direct connectivity with Google Spreadsheets. This wizard allows you to save submissions directly into Google Spreadsheets. It also provides additional assistance in setting up the login to your Google account and in selecting the spreadsheet.

...

See the  Save your Submissions to a Google Sheet for details.

Manually set document URIs

Insert excerpt
Creating a Form Connected to your Database
Creating a Form Connected to your Database
nopaneltrue

...

See  the chapter on connecting to your database for all the details.

Additional Email Wizard

When the form is submitted,  can send an additional email message with optional XML document(s) , an image of the filled form, attachments and Pixel Perfect PDFs (referred to as Generated Forms), 

...

To use the wizard, click the Doc Actions section in the left toolbar and select the Additional Email Tab. See Email Integration for further details on configuring the content of the email.

How to set up Multiple Document Actions

It is important to remember that doc action wizards are single select by design. The Additional Email wizard can be used to send an email if you are configuring more than one doc action on a form/workflow. 

...

Set up the Save to Google wizard. Then use the Additional Email tab to configure the email to the IT department.

Using Templates in Form and Doc Actions

The values/entries in all doc action/doc URI wizards can be customized with data entered in the form/workflow using templates. The values set in the following Form Action wizards can be customized with data from the form:

...

Templates work the same way as documented above when used in Doc and Error Action Wizards.

Form & Doc Action Failure Notifications

An email notification is sent to all tenant administrators or the workflow administrator(s) (if configured) when a Form Action post, DOC URI or DOC Action fails and the submission does not reach it's intended destination. When the form/workflow is submitted, the user sees the message "Thank You! Your submission has been received." and then the appropriate admin is notified via email. The email is sent when the following Form/Doc actions are configured in a form/workflow:

...