|
There are three icons at the top of the Forms and Workflows home page:
Forms and Workflows in the list can be identified by their icons:
To the right of each form/workflow name there is a Form/Workflow Action Menu, which provides the following options:
Searchable Fields are fields in your form/workflow that can be used to search submissions and tasks. The designer designates which controls should be set up as Searchable fields.
Adding or deleting Searchable Fields at any time will immediately take effect for future submissions, but not for past submissions. Designers, tenant or superuser administrators or any user given the permission to edit can initiate a Refresh Searchable Fields process for a particular form/workflow to reflect the changes made to the Searchable Fields in previous submissions.
For example, let's say you have an Invoice form with the First Name and Last Name fields set up as searchable fields. You can search existing submissions or tasks by setting up a filter using the data in these fields..
Your users have requested the ability to search submissions and tasks by product name in addition to the First and Last name of the customer. You must add the Product Name field to the list of Searchable Fields in your form.
Add the Product Name control in your form to the Searchable Fields list using the Setup Searchable Fields wizard.
Follow these steps to run the Refresh Searchable Fields process.
Run the Refresh Searchable Fields Process |
Once the Refresh Searchable Fields process for the form is completed, the Product control and the associated data displays as a column in the Submissions Table.
The Refresh Process can be stopped or abandoned once started.
Once you have initiated the Refresh Searchable Fields process, the UI allows for the job to be stopped or aborted. The process can be stopped if it is in the STARTING or STARTED state.
You will notice a Stop column in the row in the table for the process that was started. To stop the job:
When the Refresh process runs, tables that store the state of the process are created in the frevvo database. By default, if a process were to fail or be stopped, starting it again would restart the failed/stopped job from where it failed/stopped.
To restart a Stopped/Failed refresh process, simply start the batch job again with same tenant and it will resume the last stopped job.
To prevent the last stopped job from restarting, change the status to Abandoned.
The Refresh Searchable Fields process must be stopped to mark it as abandoned. This prevents it from being restarted. You may want to abandon a batch job if it failed and restarting it would result in another failure. Abandoning the batch job allows you to start over again with a new process. The process cannot be abandoned if it is in the STARTING or STARTED state.
When you stop a Refresh process, you will notice Stop and Abandon columns in the row in the table for the process that was started. To abandon the job:
You can attach a thumbnail icon to a form/flow by clicking the Thumbnail icon in Form/Workflow Action Menu. Select one of the icons provided by
or upload your own. The icons will display when you access your forms/flows from a
space on mobile devices (iPhone and iPad) mobile devices. See below. If you do not specify an icon for your form/workflow,
will display a default thumbnail where required.
In the Thumbnail feature you will see a list of icons provided by .
If the form/workflow does not have an icon assigned the Current thumbnail section of the screen will display the message "You have not specified a thumbnail for this form/flow. Please select one or upload your own thumbnail. If you do not specify one, frevvo will display a default thumbnail where required." Once you select or upload a thumbnail, the Current thumbnail section will update with that icon. You will not be able to delete the current thumbnail once it has been assigned but if you update the form/workflow icon by selecting another one from the list or by uploading an image file, the updated icon will be reflected in the Current thumbnail section.
If thumbnail changes are not reflected immediately, refresh the screen. |
Forms in the Development state have a watermark. Change them to Production to remove the watermark. The Deploy/
Undeploy icon on each form/workflow toggles this state. Your license key controls the number of forms that can be set to Production. Deployed forms and workflows appear in the list with a
flag icon beside their name.
The deployment state defaults to Development irrespective of the default deployment state set by your license key and by your tenant admin for the following scenarios:
To manage production forms/workflows go to your My Account: Manage Production forms page. See managing production forms for more information
When you delete a form/workflow by clicking the Delete icon the form/workflow is permanently removed and cannot be restored. The delete operation also deletes all submissions from
' submission repository and any saved in process form/workflow instances.
Before deleting you may wish to download a copy of the form/workflow by clicking the Download icon. See this topic for information on deleting projects.
If your goal is to update your form/workflow to a new version that you had previously downloaded or to revert to an older version previously downloaded, do not first delete the form/workflow since this removes all associated saved/submitted/pending form/workflow instances. Instead leave the original as it is and upload the version from disk by clicking the Add Content icon and selecting
Upload a Form or Workflow. A dialog will display that lets you:
When uploading a form/workflow with the same ID as an existing form without checking Replace, a copy will be created and the designer will see an error message: "The form/workflow that was uploaded matches the id of one that already existed so a copy was made. If you intended to replace the existing form/workflow, delete the form you just uploaded and upload it again but check off the ‘Replace’ option." When uploading a form with Replace checked that is currently being edited by another user, the designer will see this error message: "This form is currently being edited by <user@tenant>. Please try again later." |