Basic Configuration
With Opero Forms app you can configure forms from within Salesforce. Share them as a link or embedded within a web page. Opero Forms integrates with our Opero Signature, Payments, and Documents apps to support your business processes.
- Install & Authorize the App
- Set User Permissions
- Create a New Form
- Add Form Fields
- Manage Form Fields
- Publish a Form
- Pass or Pre-Fill Form Fields
Install & Authorize the App
- Go to the AppExchange listing for Opero Forms and click the Get It Now button.
- Follow the steps prompted to install the package in Production or Sandbox org.
- Once you have installed, go to the app launcher and open Opero Forms.
- Open the Forms Configuration tab.
- Click grant access. This will allow the Forms app to read your Forms insert Form Response records into your Salesforce org. You may revoke access at any time.
Set User Permissions
Each user will need the following permissions in order to be able to use the app properly:
- Access to Opero Forms app components. You can review all the app package components that users may need to access by going to Setup>Installed Packages>Opero Forms>View Components. This includes access to the Forms, Form Requests, and Form Responses objects and fields.
- If integrating with another Opero app, check the Basic Configuration article for that app to ensure that appropriate user permissions are set:
Create a New Form
- Go to Forms
- Click New Form. This creates a new Form record.
- Complete the Form details. These field settings include actions to execute after the form is submitted.
Field Name | Field Type | Description |
Form Id | Name/Autonumber | Unique Id of your form in the following format: F{0} |
Form Name | Text | Add a descriptive name for your form for easy reference. |
Header Image URL | Text | Specify the URL of a publicly available image to display at the top of the form, either as a direct URL or merge field code. |
Header Image Width | Number | Specify the form header image width in pixels. |
Header Image Height | Number | Specify the form header image height in pixels. |
Header Text | Text | The header is the large text displayed at the top of your form. Enter either the text you want displayed or merge field code, e.g., {!Account.AccountName}, to dynamically merge field values from the related record. |
Sub Header Text | Rich Text | The sub header is the smaller text that is displayed under the header. Enter either the text you want displayed or merge field code, e.g. {!Account.Description}, to dynamically merge fields from the related record. |
Form URL | Formula | This formula field populates the Form’s URL in the following format: https://form.operoapps.com/{org id}/{Name} You can share the link or embed it within a web page. |
Completion Action | Picklist | This picklist specifies what will happen after the form is submitted and the Form Response record is created. Options include: Display Message – The app displays the completion message specified in the field “Form.Completion: Display Message”. Goto URL -The app redirects to the URL in the field “Form.Completion: Redirect URL”. Document Action: Download File – The app triggers document generation with the Opero Documents app, then downloads the generated document. The user will see a completion message appear (specified in the field “Form.Completion: Display Message”) with a “Download File” button below the completion message. If pressed, the app will download the document. Document Action: Goto Google Doc – The app triggers document generation with the Opero Documents app. The user will see a completion message appear (specified in the field “Form.Completion: Display Message”) with a “View Document” button below the completion message. If pressed, the button will open the Google Doc (specified in “Form Response.Google Doc URL”). Document Action: eSign – The app triggers document generation with the Opero Documents app, downloads the generated document, then serves it immediately for signature (it is not emailed)*. The user will see a completion message appear (specified in the field “Form.Completion: Display Message”) with a “Sign Document” button below the completion message, which links to the eSign page. The document action that is specified for the document generation is configured to integrate with Opero Signature app. *If desired, you can create a Flow on the eSign Doc object that checks the status of the eSign Doc record and emails the signer to ask them to sign if not signed within a certain period of time. You would merge the esign link field into the email template. |
Completion Display Message | Rich Text | Enter a message to display after the form is submitted. Field type allows for text formatting and images. |
Completion: Redirect URL | Text | Enter a URL with merge field codes. Once the form is submitted, the app redirects to the URL that you specify, e.g. the URL to a Payment Form using Opero Payments app, another Form, or any other url. |
Completion: Document Action ID | Text | Enter the Document Action ID or the Salesforce record ID of the Document Action to execute after the Form is submitted. This feature requires the Opero Documents app. |
Enable Captcha | Checkbox | When selected, the app enables Captcha in order to protect your form from spam. |
Add Form Fields
Each form contains Form Fields. You can add up to 100 Form Fields to your Form. The list of all Form Fields related to a Form are listed in the Form Field related list. When you create a Form Field, you’ll fill out the following fields to specify information about the Form Field.
Field Name | Field Type | Description |
Field ID | Name/Autonumber | Unique Id of you your form in the following format: FF – {0} |
Form | Master-Detail (to Form object) | The Form Field object is on the detail side of a Master Detail relationship with the Form object. This field displays the Form Field’s related Form record. |
Field Number | Number | This is a read-only field that |
Field Label | Text | Add a descriptive name for your form for easy reference. |
Field Hint | Text | Use this field to provide guidance to the user filling out the form. |
Field Type | Picklist | Specify the Form Field’s field type. Options include: – Text – Text Area – Picklist – Checkbox – Date – File Upload |
Required | Checkbox | If selected, the Form Field will be required. If not selected, the Form Field will be optional. |
Picklist Values | Text Area (255) | If the Field Type is “Picklist”, enter the values with each value on its own line. |
Manage Form Fields
After creating a form, you can create, edit, delete, and reorder the fields that appear on the form from within the “Edit Form Fields” Visualforce page.
Create
To add a new field to your form, click the “+” icon at the bottom of the list of fields. Complete the field details then save by clicking the Save icon at top right.
Edit
To edit a field’s details, update the form field as needed then click the Save icon to save your changes.
Delete
To delete a field from the form, click the Delete icon at the top right.
Reorder
To change the order of the fields on your form, click anywhere on the box outlining the field details and drag it to a new position in the list of fields. The Field Number automatically updates to reflect the new position number.
Publish a Form
When you create a new Form record, a URL is displayed in the Form URL field. Access the form with this URL. To publish the Form, you can:
- Link directly to the Form URL from your website.
- Link directly to the Form URL in an email.
- Embed your form within a web page using HTML <iframe> element. Be sure to pass the URL params to the embedded form.
Pass or Pre-Fill Form Fields
To pre-fill values for a field on a form, use the URL params, e.g. “Field1”, “Field2”, … “Field100” of the field number matching the field you want to pre-fill. For example, to populate field number 1 in a form, you would add the field1 param to the Form URL.
Form URL:
https://form.opero.com/XulziYhYomB8s4dvLrsPM7xasU61ohHo05X5PQNGChM6dctvjtisdme5VQDsn7c6/mXXiV1nEVhVKoxhjxnKsPJvUBXEDkJm6mphlTORa
Form URL with field1 param added:
https://form.opero.com/XulziYhYomB8s4dvLrsPM7xasU61ohHo05X5PQNGChM6dctvjtisdme5VQDsn7c6/mXXiV1nEVhVKoxhjxnKsPJvUBXEDkJm6mphlTORa?field1=test
This could be useful if you are emailing a dynamic link to someone and dynamically merging a value to pre-fill. An example use case would be to send a link to a contact in order to confirm their contact information. The link will pre-fill all the fields that you currently have a value for. The contact would be able to view and edit as needed, then submit.