Origami Version 6.3.1A: Smarter Web Forms, Flexible Import & Full Audit Transparency

Version 6.3.1A brings focused upgrades across three key areas: web form management with full control over availability and usage, expanded audit capabilities including IP address logging and report action tracking, and meaningful improvements to data import and file management. Every update shortens processes and increases transparency — without adding complexity.

In this article:

Web Forms Management – new columns, submission counter, input limits and time limits
Audit Log upgrades – IP addresses, report action tracking
Reference fields when creating an instance – linked data in real time
Select files from System Storage – reuse existing files
Partial import – import valid records, fix the rest

Here are the key updates in this version:

Web Forms Management – Full Control Over Availability and Usage

New columns, submission counter, input limits and time limits – all from one management screen

The web forms management screen has been comprehensively upgraded. You can now manage each form with full control over who uses it, how many times, and until when — directly from the main table.

Step by step:

The user opens the Web Forms management screen.
The table now displays new columns: Copy Snippet, Form Name, Status, Submission Counter, Input Limits, Time Limit, Creation Date, Form Creator.
Status management: each form can be activated or deactivated via the Status column. The status changes automatically to Inactive when a limit is reached.
Submission Counter: displays the number of submissions per form, with an option to reset (Reset).
Input Limit: set a maximum number of submissions. When the limit is reached, the form automatically becomes Inactive.
Time Limit: via Activity Control, set a date and time at which the form will automatically stop accepting submissions.

Who it’s for:

System administrators and teams managing web forms.
Teams who want to control usage volume and form availability.

What it solves / examples:

Prevents receiving registrations beyond a desired limit — automatically, without manual intervention.
Example: an event registration form capped at 100 attendees — once 100 is reached, the form automatically becomes Inactive.
Example: a workshop registration form — automatically closes on 15/04/2026 at 12:00.

IP Address in the Audit Log

An added security layer – every action tracked with its origin

Every action recorded in the Audit Log now includes the IP address of the user who performed it. System administrators get a complete picture — not just what was done and who did it, but also from where.

Step by step:

A user performs any action in the system (login, export, data change, etc.).
The action is recorded in the Audit Log along with the user’s IP address.
A new column appears in the Audit Log table: IP Address.

Who it’s for:

IT teams and information security teams.
System administrators who need detailed tracking of user activity.

What it solves / examples:

Enables detection of access from suspicious or unauthorized locations.
Example: a user exports data — the Audit Log shows both the action and the IP address from which it was performed.

Audit Log for Report Actions

Full transparency on report creation, editing, running and exporting

Report actions — creation, editing, running, exporting and deletion — are now fully logged in the Audit Log, including the report name. System administrators can track exactly who did what and when.

Step by step:

A user performs an action on a report (create, run, export or delete).
The system logs the action in the Audit Log with the report name and action details.
System administrators can view the records and see a full breakdown.

Who it’s for:

System administrators and information security teams.
Organizations that require full documentation of report-related activity.

What it solves / examples:

Provides full transparency on report usage and helps prevent unauthorized access to sensitive data.
Example: a user runs a report with specific filters — the action is logged with all details and can be audited at any time.

Reference Fields When Creating an Instance

Linked data in real time – before you even save

When creating a new instance and selecting a value in a Relation field, the linked Reference Fields immediately display the relevant data — in real time, before the instance is saved. Less guesswork, more confidence when entering data.

Step by step:

The user opens the Create Instance screen.
They select a value in a Relation field.
Immediately after selecting — the linked Reference Fields populate with the relevant data.
The user can see the linked information at the point of entry, before saving the instance.

Who it’s for:

Any user filling in forms with relation and reference fields.
Teams working with entity relationships who want to see connected data in real time.

What it solves / examples:

Enables informed decision-making at the point of data entry.
Example: when selecting a doctor — the linked clinic is displayed immediately at the fill stage, without needing to save first.

Select Files from System Storage

Reuse existing files – directly from any file upload field

File upload fields now support two options: upload from your computer as usual, or select from files already stored in System Storage. A dedicated lightbox with two tabs makes navigation simple — and only files matching the field type are shown.

Step by step:

The user clicks on a file upload field icon.
A lightbox opens with two tabs: Upload File and Select from System Storage.
Upload tab: drag & drop or browse from your computer, with a preview before uploading.
System Storage tab: a list of existing files in the system, in table or icon view. Select a file and attach it to the field.
Only files matching the field type are shown and available for selection.

Who it’s for:

Any user who uploads files to the system.
Teams working with existing files who want to reuse them without re-uploading.

What it solves / examples:

Saves time — no need to locate files on your computer when they’re already in the system.
Reduces errors by showing only files compatible with the field type.
Allows attaching files without saving them again to local storage.

Partial Import – Import Valid Records, Fix the Rest

No more all-or-nothing – import what’s valid, correct what isn’t

When importing a data file and the system detects invalid records (those missing required fields), you no longer need to cancel everything and start over. Export the problematic records for correction and continue importing only the valid ones.

Step by step:

The user starts an Import process for a file.
The system identifies records with missing required fields and marks them as Invalid Records.
A “Wrong Records” section appears with three action options: Cancel Import — cancel the entire import process | Export Invalid Records — export the invalid records to Excel for correction, preserving the original file structure | Proceed with Valid Data — continue the import with only the valid records.

Who it’s for:

Users who import data from external files.
Teams working with large datasets who want control over data quality.

What it solves / examples:

Prevents creating instances with missing or incorrect data.
Allows fixing data before re-importing — without losing what already worked.
Example: a file with 100 records, 10 of which are missing a required field — the 10 are not imported, and the user can export them for correction and continue with the 90 valid ones.

In Summary

Version 6.3.1A continues Origami’s approach: every update is designed to save time, increase transparency, and give teams greater control — without adding friction to existing workflows. Whether you’re managing web forms, importing data, or need a higher level of audit coverage, this version brings practical tools you can start using today.