Improvement to the ‘share’ submission automation

The automation feature allows admins to automate their workflow with logic-based actions. The share action within automations now includes the option to select a specific admin to share a submission with. The admin selected will be notified that a new submission has been shared with them. The notification will include a link to the submission on the admin side of the system instead of the end user side. To create automation, navigate to “Edit form” >> “Automations” >> “Add automation”.

Bug fixes

• Fixed an issue where the ‘view changes’ link in the timeline was not working for anonymous forms
• Fixed an issue where certain scoring fields were not working when only two options existed
• Fixed an issue where users were landing on a login page with the message “Submission deleted” even though it wasn’t

Submission timeline redesign and improvements

The timeline feature is essential for tracking submissions through their lifecycle. It tells you what changes were made, who made them, and when. As such, we’re happy to deliver a new and improved timeline experience that will be even more reliable and easy to use.

1. Tracking changes just got a whole lot easier. All changes to a submission will create an update event on the timeline and clicking the “view changes” link will now display an easy-to-read list of the changes made.
2. When an automation or reminder triggers a submission it will create a new event on the timeline. Those events now display a link back to the specific automation or reminder the event was created for. This means you can easily track down the automations that may not be working as intended.
3. We’ve made various behind-the-scenes improvements to ensure the reliability of the timeline event creation and order.
4. Automations using the “webhook” action will create a webhook event on the timeline that includes the webhook status.

New public API added

We’ve added a new public API for updating the value of a user lookup field. API documentation can be viewed in the ‘Configuration’ page of your Omnitrack system.

Penetration test completed

As part of a periodic security tests routine, VinciWorks regularly performs penetration tests by independent security companies who conduct both a grey-box and black-box review. The goal of these tests is to simulate an external invasion of VinciWorks’ infrastructure and application levels, in order to examine the soundness of the existing security and defence methods and to locate weaknesses in the communication, application, database and operating system levels that are available to potential attackers.

Bug fixes

• Fixed an issue where the user’s page was not displaying the correct information under the ‘added via’ column
• Fixed an issue where some anonymous forms were redirecting to the login page

Improved experience for new users

When a new user logs in for the first time they will be directed to an account activation page instead of the standard login page. Clicking the ‘Activate my account’ button will trigger an email to the user’s inbox and they can set a password from there.

Improved warning messages on the form builder

The form builder now has a clear warning message to users about which fields are being used in conditional logic. The warning message will appear when a user tries to delete a field that’s being used in conditional logic. 

Scoring fields

We’ve added a new field type which allows users to create dynamic scoring fields in their forms. For example, you could create a risk assessment form that asks a series of risk related questions and generates a score based on a user’s responses.

There are a few steps to take in order to create a scoring field in your form.

Step 1 – Add a scoring field to your form by going into “Edit form” >> “Add question” >> scroll down to the complex field section and select “Scoring field”.

Step 2 – Build an equation using existing fields from your form. The scoring feature allows you to add/subtract/multiply/divide by the value of two or more existing questions in your form. For example, if you have fields called “Risk likelihood” and “Risk impact” you could multiply the value of those two questions to get a final “Risk score”.

Step 3 – The final step for building a scoring field is to assign a number value to each option in the questions you are using in the equation. For example, if the “Risk likelihood” question gives the user options to select High, Medium, Low then you’ll need to assign a number value to each of those options.

To assign values, go to the question and click the ‘Settings’ cog on the field. Navigate to the ‘Scoring’ tab and fill in a value for each option.

You’re all set! You’re scoring field will now calculate dynamically as the form is filled in.

Bug fixes

• Fixed an issue where some clients could not see the ‘Form admin’ role on the users page.