Feedback

Give the possibility to select a certain number of elements and change the value of a custom field in bulk.

It would be very useful to build a set of custom fields (for example “Backup Parameters”, containing frequency, destination, type, etc.) and save it as a callable section in multiple entities, for example in assets and systems. This would avoid the work of re-creating the section and all its fields, reducing the chances of error.

Custom fields can only be duplicated within a section of an entity. By entity we mean risks, processes, systems, assets, and so on. A custom field defined for assets, however, could also be useful for systems. At the moment it is necessary to recreate the same field from scratch, with its values and attributes, in the second entity. It would be much faster and less error-prone to be able to duplicate it.

A calculated custom field shows only the string associated with the resulting value, even if you associate a color with each result range and even if you activate additional options to show the numeric value and color. I suggest removing this limitation in order to improve the informational content of the summary tables in which that custom field appears.

I would like to have the ability to integrate third-party APIs with Formalize. For example, for Evidence objects, I would like to configure an API endpoint URL and its response format, map the returned fields to evidence attributes, and define how frequently the object should be refreshed and updated.

We’re adding the ability to stop recurring tasks while keeping their full history intact. This will make it easier to manage recurring activities that are no longer needed, without affecting records of past work. By preserving completed occurrences while stopping future ones, you’ll maintain a clear audit trail and accurate visibility into what has already been done.

Make it possible for the options when making a custom field to be in alphabetical order. Maybe next to the required option. You could tick a box that has alphabetical order as an option. Thanks!

Please introduce an option to control which authentication methods are available to users at the time of user creation. Administrators should be able to specify whether a user can log in via Local authentication, SAML, or both. Allowing users to create and manage a password directly within Formalize for Local login is not inherently insecure. Providing this flexibility would allow organizations to: Assign both Local and SAML authentication to users who require dual access. Restrict certain users to SAML-only login where appropriate. This enhancement would improve administrative control, reduce friction during onboarding and offboarding, and better align authentication methods with organizational policies.

We are adding the ability to approve versions of evidence before making them valid

We’re enabling your tools and systems to interact directly with evidence in our platform via Open API. This means you can automate evidence collection, submission, and management, and cut down on manual work.