Origami Version 6.3.3: Record-Level Audit Log, Support Screen Upgrade, and More

Version 6.3.3 brings a series of significant improvements across the platform: a new record-level Audit Log widget, a complete overhaul of the Support screen, mobile tile view, automatic call recording link storage, and dozens of field-driven improvements.

Excel File Import – XLS and XLSM Support

Until now, importing files into Origami only supported XLSX and CSV formats. Starting with this version, XLS and XLSM files can be imported directly — no prior conversion needed.

Step by Step

  1. The user opens the Import window.
  2. When selecting a file, all of these formats are now supported: .xlsx, .csv, .xls, .xlsm
  3. The user uploads the file without needing to convert it to XLSX first.
  4. The system reads the file and runs the standard import process.
  5. For .xlsm files, only data is imported — macros are not executed.

Main Uses

  • Importing legacy Excel files without any format conversion.
  • Streamlining data migration workflows that previously required a manual conversion step.

Who It’s For

  • Users working with older Excel file formats (XLS/XLSM).
  • Data teams importing exports from external systems.

What It Solves

  • Previously, XLS and XLSM files had to be manually converted to XLSX before import — an unnecessary extra step that slowed down the workflow.
  • This update removes that friction entirely.

Examples

  • Importing a CRM export in Excel 97-2003 (.xls) format directly, without any pre-processing.
  • Uploading a macro-enabled workbook (.xlsm) — data is imported cleanly, macros are ignored.

Support Area Upgrade

The Support screen has been redesigned from the ground up: a cleaner interface, renamed from “Inquiries” to “Support,” the ability to set multiple notification email addresses per ticket, and a new option to open a ticket directly from the entity instance view.

Step by Step

  1. The user navigates to the Support module.
  2. The redesigned screen presents a clean, intuitive layout.
  3. An admin configures multiple email addresses for ticket notifications.
  4. A new button allows opening a ticket directly from the entity instance view.
  5. All configured addresses receive updates whenever the ticket status changes.

Main Uses

  • Managing support tickets with multiple notification recipients.
  • Opening tickets without leaving the record context.
  • Centralizing the entire support workflow into a single screen.

Who It’s For

  • System administrators.
  • Users who open and manage support tickets.
  • Organizations that need to notify multiple contacts on ticket updates.

What It Solves

  • The workflow is now unified and intuitive — no more switching between screens.
  • The term “Inquiries” didn’t clearly communicate that this is a ticketing system.
  • Previously, only one email address could be configured for notifications.
  • This update unifies the entire workflow into one screen and allows multiple recipients per ticket.

Examples

  • A fault ticket can now notify both the IT manager and the support representative simultaneously.
  • An admin can attach email addresses to a ticket — including non-admin system users and external contacts who don’t have system access at all. Everyone attached receives notifications on every ticket update.
Redesigned Support screen

Tile View on Mobile

Tile view is now available on mobile. Users can switch between table view and tile view directly from the mobile app — just as in the desktop version.

Step by Step

  1. The user opens any entity on mobile.
  2. A toggle appears at the top of the view to switch between table and tile views.
  3. The user selects Tile View.
  4. Records are displayed as tiles with fields shown according to the configured tile layout.
  5. The selected view is preserved as the user navigates.

Main Uses

  • Browsing records in tile format on mobile for a more visual experience.
  • Field teams accessing records visually from phones or tablets.

Who It’s For

  • Mobile users who prefer visual card-style browsing.
  • Field teams accessing the system from smartphones or tablets.

What It Solves

  • Tile view was only available on desktop. Mobile users were limited to table view — less comfortable for visual browsing.
  • Now tile view is available on all devices.

Examples

  • A sales rep browsing customer cards in tile view from the mobile app.
  • A field technician viewing service records as tiles on a tablet.
Tile view screenshot

Improved Search in the Record-Level Audit Log

When searching the Audit Log at the record level, only matching results are now displayed — instead of showing the full log with color highlights as before. A more focused, faster, and user-friendly experience.

Step by Step

  1. The user opens a record instance.
  2. In the Audit Log widget, the user types a search term.
  3. Only entries that match the search are displayed.
  4. Non-matching entries are hidden entirely — not grayed out or highlighted.

Main Uses

  • Quickly locating specific changes in a record’s history.
  • Filtering audit history without visual noise.

Who It’s For

  • System administrators, team leaders, or anyone responsible for tracking record-level changes.

What It Solves

  • Previously, searching the record-level Audit Log showed the full log with matching entries highlighted in color — making it harder to scan long histories.
  • Now, only relevant results are shown, making it much faster to find what you’re looking for.

Examples

  • Searching for a specific field update in a customer record with hundreds of history entries.

Optional Phone Number Format Validation

Phone number format validation can now be turned off at the field level. When disabled, records can be saved with non-standard phone numbers without blocking the save process.

Step by Step

  1. An admin opens the settings for a phone-type field.
  2. A new toggle is available: “Validate phone number format.”
  3. When turned off, users can save any value in the phone field without format restrictions.
  4. When turned on (the default), standard validation behavior applies.

Main Uses

  • Handling data that includes non-standard phone numbers — extensions, internal codes, or international formats.
  • Allowing flexible phone data entry without system-level restrictions.

Who It’s For

  • Admins configuring entities with phone fields.
  • Organizations that need flexibility in how phone numbers are stored.

What It Solves

  • Allows saving records even when a phone value doesn’t conform to standard format — without blocking the save.
  • Provides per-field flexibility to match organizational needs.
  • Enables matching between phone numbers saved in different formats.

Examples

  • An organization storing internal extension numbers in phone fields can disable validation and save those values without errors.
  • Importing contacts with mixed phone formats from an external system without triggering validation errors.
Phone number validation settings

Configurable KPI Count Per Row — at Instance Level

The KPI widget at the instance level now supports a new option: choose how many KPIs to display per row. Just like it works on dashboards — now available at the record level too.

Step by Step

  1. The user edits a KPI widget at the instance level.
  2. A new setting is available: “KPIs per row.”
  3. The user selects 1, 2, 3, or 4 KPIs per row.
  4. The widget layout updates to reflect the selection.

Main Uses

  • Customizing KPI widget layout for different screen sizes and record types.
  • Matching dashboard aesthetics at the record level.

Who It’s For

  • System admins and screen designers configuring instance pages.

What It Solves

  • Previously, the number of KPIs per row in an instance widget was fixed and couldn’t be changed.
  • Now the layout is fully customizable — just like on the main dashboard.

Examples

  • A customer record with 4 KPIs displayed 2 per row for a compact layout.
  • A project record with 3 KPIs shown in a single row for a clear overview.
KPI widget per row configuration

Save Invoice as Draft on API Error

When a tax authority API error occurs during invoice submission, the invoice is now saved as a draft instead of being deleted. The user can return to it, update the details, and try again.

Step by Step

  1. The user creates an invoice and submits it.
  2. The tax authority API returns an error.
  3. Instead of losing the data, the system saves the invoice as a draft.
  4. The user reopens the draft, fixes the issue, and resubmits.

Main Uses

  • Recovering from temporary tax authority API failures without losing invoice data.
  • Preventing the need to re-enter invoice details after a failed submission.

Who It’s For

  • Finance teams and users who issue invoices through the system.

What It Solves

  • Previously, when the tax authority API returned an error, the invoice was deleted after the error was closed and all entered data was lost.
  • Now, in case of an error, the invoice is saved as a draft — the user can return to it, update the details, and try again.
  • If the tax authority service is unavailable, users won’t need to recreate the invoice from scratch — it will be saved as a draft and remain available for follow-up.

Examples

  • Invoice submission failed because the tax authority was temporarily down — the invoice is automatically saved as a draft, ready to resubmit once the service is back.

“Update Field” Action for the On Instance View Trigger

The Update Field action is now available for the On Instance View trigger. This enables automatically updating fields every time a user opens an instance — and opens up new automations that weren’t previously possible.

Step by Step

  1. The user creates or edits a Workflow.
  2. Selects the On Instance View trigger.
  3. When choosing actions, the Update Field action is now also available.
  4. The user configures which field to update and the desired value or formula.
  5. Every time an instance is opened via the On Instance View trigger, the field updates according to the Workflow configuration.

Main Uses

  • Automatically updating a “Last Viewed” timestamp when a record is opened.
  • Tracking which user last viewed a record.
  • Triggering field updates based on view events.

Who It’s For

  • System admins and Workflow designers.

What It Solves

  • Previously, the Update Field action couldn’t be combined with On Instance View, limiting automation possibilities.
  • Now, any field can be updated automatically when a record is opened.

Examples

  • “Last Viewed” date field that updates automatically when a record is opened.
  • A “Viewed By” field that captures the name of the last user who opened the record.

Iframe Widget Height Configuration Options

The Iframe widget now supports height configuration: choose between the widget’s default height or a fixed custom height — for a better fit with different content types.

Step by Step

  1. The user edits an Iframe widget in the Visual Editor.
  2. A new setting is available: Height mode.
  3. Options: Default (matches widget height) or Fixed (set a specific pixel value).
  4. The widget displays content at the configured height.

Main Uses

  • Adapting the Iframe display to different content types that require specific heights.
  • Embedding external pages or dashboards at a precise, fixed size.

Who It’s For

  • System admins and screen designers.
  • Users embedding pages or external systems via Iframe.

What It Solves

  • Previously, the Iframe height was always determined by the widget height — which didn’t suit all content types.
  • Now, you can choose the widget’s default height or set a fixed height in advance.

Examples

  • Embedding an external system with a fixed layout that requires a specific pixel height.
  • A dashboard embedding an external report at exactly 800px height for a consistent display.

Extended Phone Number Mapping in PBX Integration

The PBX integration now supports mapping multiple phone fields to incoming call matching. When a call comes in, the system searches all configured phone fields — increasing the chances of finding the right record.

Step by Step

  1. The admin opens the PBX connection settings.
  2. In the field mapping configuration, multiple phone fields can now be selected.
  3. When an incoming call arrives, the system searches all configured phone fields for a match.
  4. If a match is found in any field, the record is identified and the call is linked to it.

Main Uses

  • Handling contacts with multiple phone numbers (work, mobile, home).
  • Improving call matching accuracy when numbers are stored across different fields.

Who It’s For

  • Admins managing PBX integration.
  • Organizations with multiple phone numbers per contact.

What It Solves

  • Previously, PBX matching was limited to a single phone field. If a contact had multiple numbers, only one would be checked — reducing match rates.
  • Now, multiple fields are searched simultaneously, significantly improving identification accuracy.

Examples

  • A customer with both a mobile and office number — incoming calls from either number now match to the same record.
PBX phone number mapping

Audit Log Widget at Record Level

The Audit Log has moved to the record level: you can now add an Audit Log widget to any instance page, view the complete change history of a record from within it — who changed what and when — and filter by columns and conditions of your choice.

Step by Step

  1. The system admin adds the Audit Log widget to the instance page using the Visual Editor.
  2. In the widget settings, select which columns to display and in what order.
  3. Define which filters are available to users, and set fixed filters applied on widget load.
  4. When a user opens a record, the Audit Log widget displays all changes made to that specific record.
  5. The user can filter by user, date, action type, or any other configured column.

Main Uses

  • Viewing the complete change history of a specific record.
  • Filtering changes by user, date, or action type.
  • Configuring which fields appear in the audit view per record type.

Who It’s For

  • System admins, team leaders, compliance officers, and anyone responsible for tracking changes.

What It Solves

  • Previously, viewing a record’s change history required navigating to the main Audit Log screen or clicking the clock icon at the top of the instance.
  • Now the full audit history is embedded directly within the record — with configurable columns, filters, and display options.
  • The Audit Log data can also be viewed as part of the environment dashboard.

Examples

  • A sales manager reviews all changes to a deal record directly from within the record.
  • A support team sees every status change on a customer ticket in real time.
  • Setting a fixed filter to show only “Update” actions, so users see only relevant changes.

Save Incoming Call Recording Link to Record

When the PBX returns a recording link for an incoming call, Origami can now automatically save that link to a designated field in the matched record — no manual action required.

Step by Step

  1. The admin configures a dedicated URL-type field to store call recording links.
  2. In the PBX connection settings, the admin maps the recording link field.
  3. When an incoming call ends and the PBX returns a recording link, the system saves it automatically to the configured field.
  4. The link is saved only in records where a match was found.
  5. Note: at this stage, the feature supports inbound calls only.

Main Uses

  • Automatic storage of call recordings linked directly to customer records.
  • Quick access to call recordings from within the record.

Who It’s For

  • Sales teams, support teams, and any team handling inbound calls.

What It Solves

  • Previously, call recordings had to be manually located and added to records.
  • Now, the recording link is stored automatically when the call ends — saving time and ensuring no recording is missed.

Examples

  • A customer service agent can listen to the recording of an incoming call directly from the customer record, without searching through a separate call log.
Call recording link field

Country Code Selector for Web Form Phone Fields

Phone fields in Web Forms now include a country code selector — just like phone fields in the system interface. When editing an existing record, the previously saved country code is shown automatically.

Step by Step

  1. A user fills out a Web Form that includes a phone field.
  2. A country code dropdown now appears next to the phone input.
  3. The user selects their country code (e.g., +1, +44, +972) and enters their number.
  4. When editing an existing record, the saved country code is displayed automatically.
  5. Existing records without a saved country code default to +972.

Main Uses

  • Collecting international phone numbers through Web Forms.
  • Ensuring consistent phone number storage with country codes.

Who It’s For

  • Web Form users.
  • Organizations receiving inquiries from contacts in different countries.

What It Solves

  • Previously, phone fields in Web Forms didn’t allow selecting a country code — unlike the phone fields in the system interface.
  • A user from the US selects +1, a user from France selects +33 before entering their phone number.
  • When editing a record, the number is shown with the country code it was saved with.
  • Existing records without a saved code default to +972.

Examples

  • A contact form collecting phone numbers from international leads now allows each contact to select their own country code before entering their number.

In Summary

Version 6.3.3 continues Origami’s philosophy: every update is designed to save time, increase transparency, and give teams greater control — without adding friction to existing workflows. Whether you’re managing support, working from mobile, importing data, or need record-level audit tracking, this version delivers practical tools you can put to work today.