Origami Version 6.2.9: Smarter Telephony, Full Transparency, Precise Management

We are excited to introduce Origami Version 6.2.9 – a new release packed with meaningful enhancements in telephony, data management, information security, and operational control. In this version, we focused on capabilities that help organizations work in a smarter, more transparent, and more precise way: from intelligent PBX call summaries and outgoing call status feedback, through advanced file locking and smart duplicate detection, to report permission management and comprehensive audit trail logging.

In this article, you will find:
Telephony innovations – call summaries, success/failure indicators, and instance creation from unrecognized calls
New data management tools – duplicate detection by pointing field (Reference), default values for relation fields, import cancellation, and MOV file support
Security and transparency – report permission management, password-protected file locking, and advanced audit trail logging
Calendar upgrades – resource view and advanced filtering

Here are the key updates included in this release:

PBX Call Summary – Smart Documentation for Every Call

Instant access to call content summaries, directly from the PBX table

You can now view a Call Summary directly from within the PBX application. When the connected PBX supports and provides call summaries, the summary is passed through a dedicated Call Summary field, saved in the Call Logs table, and displayed inline. In each relevant call row, an eye icon appears that opens a Lightbox with the full summary content. A button for displaying the call summary has also been added to the Omni-Channel view, next to the recording button – so all information is accessible without switching between screens.

Step by step:

If the PBX connected to your system supports and provides call summaries, it passes them through a dedicated Call Summary field.
The summary is saved and displayed in the Call Logs table within the PBX application.
For calls that have a summary: an eye icon appears next to the call row. Clicking the icon opens a Lightbox with the full Call Summary content.
Additionally, in the Omni-Channel view, a button for displaying the call summary appears next to the call recording button – allowing you to open the summary in a Lightbox.

How to use:

The user can view the Call Summary of any call it was provided for, via the eye icon or the Omni-Channel button.
The full content can be viewed in a Lightbox without cluttering the main table.

Who is it for:

PBX users – customer service and sales teams.
Managers who monitor call content or want to extract key information for follow-up.

What it solves / Examples:

Enables detailed documentation and text records of calls over time.
Eliminates the need to open additional records or switch screens to view a call summary.
Example: A sales manager reviews a representative’s call summary and immediately understands what was agreed with the customer – without listening to the entire recording.

Outgoing Call (Click2Call) Success or Failure Indication

Immediate feedback on call status – directly from within the system

Now, when a user clicks the Call button on a phone field, the system displays a clear indication of the call status: if the call was sent successfully – a “Call sent successfully” notification appears; and if the call failed (Webhook returns an error) – a “Call failed” notification appears. This way you can know in real time whether the call went through as planned.

Step by step:

The user clicks the Call button on a phone field in the system.
After sending the call: if the call was sent successfully → a notification appears: “Call sent successfully“. If the call failed (Webhook returns an error) → a notification appears: “Call failed“.

How to use:

The user clicks the Call button on a Phone Field.
Receives immediate feedback on the success or failure of the action, provided the system supports it (Desktop with PBX App running).

Who is it for:

System users who make calls through phone fields.
Sales and customer service teams.

What it solves / Examples:

Provides immediate feedback on call status – no need to guess whether it went through.
Example: A sales rep clicks a customer’s number, gets “Call sent successfully” and knows the call is on its way. If they get “Call failed” – they know to check settings or try again.

Create a New Instance from an Unrecognized Call

Open a new record with one click – directly from an incoming call

When an incoming call is received from a number not recognized in the system, a new button now appears: Create Instance. Clicking the button opens a new instance creation window, with the Phone field automatically populated with the caller’s phone number. This allows you to open a new customer record during the call – without any unnecessary typing.

Step by step:

When an incoming call from an unrecognized number is received, a new button appears: Create Instance.
The user clicks the button.
A new instance creation window opens for the relevant entity.
The Phone field in the new instance is automatically populated with the caller’s phone number.
The user completes the remaining fields as needed and saves the instance.

How to use:

Users can create a new instance directly from the incoming call without needing to re-type the phone number.
The button appears only when the calling number is not recognized in the system.

Who is it for:

Customer service teams, call centers, and sales teams.
Users who want to shorten processes and open a customer file alongside a new incoming call.

What it solves / Examples:

Enables rapid creation of new records for unrecognized calls.
Saves time on phone number entry.
Example: A potential customer calls the support center for the first time – the agent clicks Create Instance, the number is auto-filled, and the customer card opens immediately.

Duplicate Detection by Pointing Field (Reference)

Prevent duplicate records based on values from linked entities

You can now configure duplicate detection based on a Reference field – a pointing field that references a value from another entity. The system will identify duplicates based on the linked value and alert you when creating duplicate records. This allows you to prevent duplicates not only by internal fields, but also by data from other entities.

Step by step:

The user goes to the entity settings in the system.
Navigates to the duplicate field settings.
Selects the Reference field (the pointing field) as a duplicate field from the list.
Saves the settings.

How to use:

After configuration, the system will identify duplicates based on the selected Reference field and alert you when creating duplicate records.

Who is it for:

Users who work with pointing fields and want to prevent creating duplicate records based on values from linked entities.

What it solves / Examples:

Prevents duplicate orders based on an order number from an external entity.
Prevents duplicate contacts based on a phone number from a linked customer.

Default Value for Relation (Link) Fields

Automatic population of link fields – saving time and preventing errors

You can now set a default value for Relation fields, just like text or selection fields. The user selects an instance to serve as the default, and when creating a new instance – the field is automatically populated. The value can be manually changed at any time.

Step by step:

The user goes to the Relation field settings.
Configures the fields for linking (“Select from fields”).
Sets a “Default Value” (like text or selection fields).
Selects an instance to serve as the default.
Saves the settings.
When creating a new instance, the field is automatically populated with the selected value.

How to use:

The user pre-defines a fixed value for the Relation field.
Every time a new record is created, there is no need to manually select the value – it is already filled in.
The value can be changed manually if needed.

Who is it for:

Users managing entities with recurring fixed values.
Teams looking to streamline data entry and prevent errors.

What it solves / Examples:

Saves time on repetitive data entry.
Reduces errors in selecting instances in Relation fields.

Cancel Data Import

Real-time control over the import process – instant cancellation with one click

From now on, when importing data into the system, a Cancel button is displayed below the Loading bar. Clicking it stops the import from the current point – data that has already been loaded is saved, but the process will not continue. Note: no Rollback is performed on data that has already been completed.

Step by step:

The user begins a file/data import process in the system.
Below the Loading bar, a “Cancel” button is displayed.
The user clicks the Cancel button to stop the import.
The import stops from the current point – data already loaded remains in the system.
The import process will not continue, but no Rollback is performed on data already completed.

How to use:

A user who realizes there is an error or wants to stop the import process can click Cancel.
Data completed so far is saved automatically.
No additional actions are needed – cancellation is done with one click.

Who is it for:

Any user importing data or files into the system.
Teams that want real-time control over the import process.

What it solves / Examples:

Enables immediate stopping of a long or erroneous import process.
Prevents unnecessary loading of incorrect or unwanted data.
Example: A user starts importing a customer list, realizes certain fields are missing – clicks Cancel and the import stops, with all customers already loaded saved.

MOV File Upload Support

Upload iPhone videos directly to the system – no conversion needed

You can now upload video files in .mov format directly to the system, without any prior conversion. The file is saved and displayed in the system like any other video file. This feature solves the common problem faced by iPhone and iOS users who record videos in MOV format and could not upload them directly.

Step by step:

The user uploads a video file to the system (e.g., through a file field).
Files in .mov format can be selected and uploaded without errors.
The file is saved and displayed in the system like any other video file.

Who is it for:

Users who work with video files from iOS devices.
Teams that manage video content or field-captured files.

What it solves / Examples:

Solves the issue of lacking support for a common format (MOV).
Saves time on file conversion before upload.
Example: A user records a video on their iPhone and uploads it directly to the system without converting to MP4.

Lock Files with Password via Workflow

Dynamic protection for sensitive files – only when needed, only based on the conditions you define

A new Workflow action is now available: Lock File. This action allows you to lock a file with a password dynamically – based on triggers or conditions you define. If the file is a PDF, it is locked directly with a password. For other file types, a password-protected ZIP file is created. The lock is one-way: once a file is locked, the password cannot be changed and the protection cannot be removed.

Step by step:

The user creates or edits a Workflow.
Defines when the Workflow will run (Trigger).
Adds a new Action: Lock File.
Selects the file field to lock and the password source field.
When the Workflow runs: if it is a PDF → the file is locked with a password. If it is another file type → a password-protected ZIP file is created.

How to use:

The user controls when the file is locked, based on conditions or triggers in the Workflow.
Files can be uploaded, deleted, or replaced as long as the Workflow has not run.
Once the file is locked, the protection cannot be changed or removed.

Who is it for:

Users who need dynamic control over file security.
Teams working with sensitive documents who want to apply locking only under specific conditions (e.g., after approval, a certain status, etc.).

What it solves / Examples:

A contract document is locked only after its status changes to “Approved”.
Example: A PDF contract is sent to a customer and simultaneously locked with a password – the customer needs the password to open it, and the file cannot be modified afterward.

Report Permission Management

Precise control over who can view, run, create, and edit reports

A new section has been added to entity settings: Report Permission Settings. You can now define exactly which user groups can run and download reports, and which can create and edit them. Permissions are enforced by each user’s group, enabling a clear separation between viewers and editors.

Step by step:

The user goes to entity settings → Entity Settings.
Scrolls to the new section: “Report Permission Settings”.
Checks the Apply Report Permission checkbox.
Adds each relevant user group to: Run and download reports or Create and edit reports.
Saves the settings.

Who is it for:

System administrators managing access permissions for information and reports.
Organizations that want to separate users who can view reports from those who can edit and create them.

What it solves / Examples:

Enables precise control over report access at the entity level.
Example: The management team can only run and download reports, while the analytics team can also create and edit reports.

Audit Trail Logging – Failed Login Attempts and Password Changes

Full transparency on access attempts and sensitive actions

From now on, every failed login attempt is automatically recorded in the Audit Trail, including the IP address of the person who tried to log in. Additionally, password changes – whether by the user themselves or by an administrator – are also fully documented in the Audit Trail. This gives system administrators full transparency over every sensitive action.

Step by step:

A user attempts to log into the system with their email/username.
If the login fails: if the email exists in one account → the event is recorded in that account’s Audit Trail. If the email exists in multiple accounts → after selecting the account, the event is recorded in the selected account’s Audit Trail.
In case of a password change (by the user or an administrator): the action is automatically recorded in the Audit Trail.

Who is it for:

Information security and IT teams.
System administrators who need monitoring and oversight of user activity.

What it solves / Examples:

Provides full transparency on unsuccessful access attempts.
Enables identification of hacking attempts or suspicious activity.
Example: A user tries to log in with an incorrect password → a “Failed login attempt” is recorded with IP and timestamp.

Audit Trail Logging – Quick Export Actions

Full tracking of data exports from the system

From now on, every Quick Export action is automatically recorded in the Audit Trail. When a user exports data from a view or list, the event is fully documented – including the fields, selected filters, and the user who performed the export. This allows system administrators to track every data export and ensure proper use of data.

Who is it for:

System administrators and information security teams.
Organizations that need oversight over sensitive data exports.

What it solves / Examples:

Provides transparency on data exports from the system.
Example: A system administrator sees in the Audit Trail that a specific user exported 50 records from the “Leads” entity with all contact details – and can verify whether the export was justified.

Resource View in Calendar – Filtering, Selection, and Auto-Fill

Smart event management by resources – directly from the calendar view

Significant upgrades have been added to resources in the calendar. You can now display a resource list in the general calendar view, filter events by a specific resource, and when creating a new event in filtered mode – the resource field is automatically populated based on the selected resource.

Step by step:

The user goes to entity settings → View category → Calendar view tab.
Checks the checkbox “Display resources list in general view“.
Resource selection now appears as a source option in the calendar.
Events can be filtered by a specific resource in the calendar view.
When creating an event in filtered mode, the resource field is automatically populated based on the filtered resource.

Who is it for:

Calendar managers and teams that use different resources.
Users managing events and instances with unique resources.

What it solves / Examples:

Enables quick filtering of instances by resource.
Example: Selecting meeting room “Room A” → only events associated with this room are displayed → creating a new event automatically fills in the resource field.

In Summary

Version 6.2.9 continues to move Origami forward as a platform that gives organizations more control, more transparency, and greater intelligence – without compromising ease of use or the ability to build tailored processes simply. Whether you are looking to upgrade your telephony experience, strengthen system security, streamline data management, or improve calendar display and control – this version introduces meaningful enhancements worth exploring.

We are excited to keep evolving Origami alongside the real needs of the organizations that rely on it every day.