Authorium lets project owners and admins create online forms that allow users to input any information required to complete projects, from the initial project request to submission forms filled in by external suppliers.
Project owners and admins can also define “custom variables” to populate forms and documents throughout their projects, enabling streamlined and reliable solicitation processes.
Topics in this section:
Adding a Form Builder Stage to a Project Template
Creating and Configuring Form Templates
Variables
The Form Builder Stage is a workflow stage where your team creates customized forms for gathering essential project information.
To add a Form Builder Stage, start from the Project Template Workflow screen.
Forms in Authorium are created from templates (just like projects and documents). Form templates can be either:
Specific to an individual Project Template
Global (reusable across multiple project templates)
To build a form within a Project Template, start from the Configuration screen, then do the following:
To create a Global Form (one that can be used across multiple projects), start from the Configuration screen, then do the following:
After creating a form template, it needs to be configured by adding different components. There are two main types of components:
Layout components configure a form’s appearance or organizational layout. Examples are a label field set, field set, panel, or tabs.
Basic and advanced components collect data from users. Examples are text, dropdown, radio buttons, date/time, or a user’s signature.
You should generally build your form’s layout first, then add input components. Each field of a form is highly customizable, with a number of settings.
To arrange the layout of your table, start from the Layout tab.
To add other components, start from the Form Builder Interface.
Under Display Settings, the input and display masks let you control how information is entered and displayed.
The input mask sets a predefined format which user input must adhere to, and changes the display to match.
The display mask does not affect the actual values which are entered, but does control how the user input is shown in the field.
Both use 9 to represent numeric input, a for alphabetical input, and * (asterisk) for generic alphanumeric input.
As an example, if we added an input mask of ‘(999) 999-9999’, the user would only be able to enter up to 10 digits into that form field (and they would appear in the format of a cell phone number.
However, if we mistakenly used that as a display mask (without an input mask), the user could enter letters as well as numerals, but would still see the numbers in the same format. So if the user typed ‘123abcd7e89 EFG 1234’ into our form, that would appear as ‘(123) 789-1234’ to the user, but the form field would receive the entire string, which would be a problem if we were expecting a 10-digit phone number.
Variables allow you to use information from other sources–such as responses to forms–across your project (i.e. in other forms and documents). This is useful for tracking and automatically populating various sorts of information, such as costs per unit, expected timelines, or results from evaluations.
There are two ways to map and define variables:
Project Data Mapping
Custom Variables
Project data mapping links form field inputs to variables, which can be used in other documents or other forms (for example, a responder’s input for cost per unit defines the “costPerUnit” variable.)
This feature is only available in project templates that contain forms.
In the data mapping interface, variables are grouped together by Workflow Stage
Only certain kinds of form fields can be mapped to variables (for instance text fields, numbers, and currency fields)
To set up project data mapping variables, start from the Configuration screen.
Custom variables are defined manually within a project, rather than being auto-populated from form input. For example, you could define inflation assumptions that would be applied throughout multiple parts of an RFP.
Custom variables are not linked to form fields.
They are not constrained by project stage (i.e., they can be used anywhere within a project)
They can be used to populate multiple form or document templates.
To add and configure custom variables to a project template, start from the Configuration screen and then:
To use custom variables in a document, start from the Project Template Workflow screen and then:
To use custom variables in a form, start by going to the Workflow tab and then:
Adding calculations components to a form lets you calculate values based on form inputs or other project / global variables. For instance, if a project has a strict limit on permitted costs per unit or overall expenses, you could set up a calculation component that looks at the relevant form responses and flags ones which are over budget.
In order for calculations components to appear in the user’s Form Builder workflow stage settings, the feature must be enabled at the organizational level.
To use calculations components in a form, start from the Project Template Workflow screen.