Origami Version 6.3.5: Advanced AI Automation, Vision That Builds Workflows, Payments, and More

Version 6.3.5 is a release about smarter automation and money coming in. AI Automation got a deep upgrade with model selection, Context from related records, and structured responses. Vision no longer just understands workflows, it builds and updates them from a Prompt. A full payments system was added with payment links and payment gateway connections, along with an appointment scheduling app, a KPI field that aggregates data from linked records, and invoice export straight to Hashavshevet. And as always, dozens of smaller improvements that came from the field.

AI Automation: Model Selection, Full Context, and Structured Responses

The AI Automation action in Workflows has gone through a deep upgrade. Instead of a hard-coded model and a single text answer, you can now choose a provider and model from the list of models in the system, build Context from related records and files, and get a structured response mapped into different fields on the record. That is the difference between AI that returns text and AI that feeds the business process.

Step by step

Go to the Workflow settings and add the AI Automation action.
Enter the Prompt that describes what you want the AI to do in the instruction.
Choose the AI provider and Model from the list of models available in the system (those with a valid token attached in the system preferences).
Choose the advanced level option instead of the basic one.
Define what information will be included in the Context:
- Data from the current entity.
- Data from other entities.
- Static files defined as input.
For data from entities, you can define filter conditions on the records that will be sent to the AI.
Choose how the result is returned:
- Simple – a single text response.
- Structured – several values mapped to different fields on the record.
Save the Workflow settings.
When the Workflow runs, the system collects the data that was defined and assembles it into a Context.
The system sends the Prompt and the Context to the selected model, including files if needed, in a way that does not expose them publicly.
The system checks and validates the AI response.
In Simple mode, the result is saved in the field defined as text.
In Structured mode, the returned values are mapped to the matching fields and can be used later in the Workflow.
In case of an invalid response or an error, the system performs Validation and saves the relevant information to Logging/Audit for troubleshooting.

Main uses

Automatic analysis of records using AI.
Combining information from the current record together with information from related records.
Summarizing business information from several sources.
Extracting structured information from text.
Classifying or enriching records.
Producing several values from an AI response and saving them in different fields.

Who it’s for

Solution Builders – who build business Workflows and want to integrate AI without developing Custom Code.
CRM managers – who want to enrich and analyze records automatically using information from the record and from related records.
Sales and Operations teams – can use AI to analyze deals, contacts, tasks, and related data.
Service and support teams – can analyze Tickets and customer history and generate structured information for further handling.
Process and automation managers – can use AI results as input for additional Workflow actions.
Implementation specialists – can adapt the AI model and the Context to different business scenarios instead of being limited to a fixed model.

What it solves / examples

Rigid, aging models
Before: the old action used models that were predefined in code.
After: you can select a Provider and Model from a Registry, so models can be updated and added without changing the Workflow itself.
AI based only on the current record
For example, when analyzing a Deal you can send the AI not only the deal details but also the related Contact, Tasks, or Tickets.
Summarizing information from several sources
For example: a Workflow receives a Deal, pulls the deal and its related activity records, and asks the AI to produce a summary of the deal status and the next actions.
Working with private files
You can attach a file as part of the Context sent to the AI without making it a public file just for the sake of processing.
An AI response that is not useful for automation
Before: the old action mainly wrote a single response into a single field.
After: in Structured mode you can ask the AI to return several values and map each one to a different field.
For example – Ticket classification
A Workflow can send the AI the Ticket details, the request history, and an attached file. The AI can return a structure such as:
- Priority
- Category
- Suggested Resolution, and each value is saved in the matching field.

Vision Builds the Workflow for You: Creating and Configuring from a Prompt

Until now Vision knew how to understand existing workflows. From this version it builds them too. You describe in natural language what the process needs to do, and Vision identifies the Actions, fields, and settings, asks for approval on field mapping where needed, and makes sure every Action matches the Trigger that runs it.

Step by step

The user goes to Vision.
The user describes through a Prompt the Workflow they want to create or change.
The user specifies the actions, fields, and logic the Workflow needs to include.
Vision analyzes the request and identifies the required Actions, Fields, and settings.
When the Workflow requires field mapping, the user is asked to approve or complete the relevant field mapping.
Vision creates and configures the Workflow according to the instructions received.
The system verifies that every Action matches the Trigger that runs the Workflow, and prevents unsupported configurations.
The user can review the Workflow that was created and verify that the actions, fields, and connections were configured as required.

Main uses

Creating Workflows using natural language instructions instead of manually defining every step.
Configuring Actions and Triggers using Genie AI.
Copying or converting Workflow components while preserving correct field mapping.
Creating Repeatable Groups as part of a Workflow.
Configuring complex Workflows that include several Actions and fields.
Preventing invalid Action configurations according to the type of Trigger.
Helping users who are not deeply familiar with the Workflow structure and the Actions available in the system.

Who it’s for

System administrators – for quickly creating and configuring Workflows without needing to define every component manually.
Implementers and Implementation specialists – for building automated processes for customers using a Prompt.
Automation developers – for creating complex Workflows and saving manual work on configuration.
Business users – who want to describe the desired process in natural language and receive a matching Workflow.

What it solves / examples

This capability allows Vision not only to understand an existing Workflow, but to create and configure a new Workflow from a Prompt. In addition, it handles issues that could make an AI-generated Workflow invalid or unworkable.
Example 1 – Creating a Workflow from a Prompt:
The user asks Vision to create a Workflow so that every time a new record is created, the system copies certain values into other fields and performs an additional action. Vision identifies the required Actions and configures the Workflow.
Example 2 – Field mapping:
The user asks to copy information from one field to another. Vision does not assume the field mapping automatically when approval is required, but asks the user to confirm which source field matches which target field.

Vision Updates Too: Editing Existing Workflows in Natural Language

The natural next step. Instead of creating a new Workflow every time something changes, you pick an existing process, describe the change, and Vision updates it in place while preserving the rest of the settings. Adding an Action, changing field mapping, or changing the condition that triggers the process, all from a single Prompt.

Step by step

The user goes to Vision.
The user selects an existing Workflow they want to change.
The user describes through a Prompt the change they want to make to the Workflow.
Vision analyzes the existing Workflow and identifies the components that need to be updated.
Vision suggests or performs the required changes according to the instruction, while preserving the rest of the Workflow settings.
If the change requires field mapping or additional information, Vision asks the user to complete or approve the required details.
The user approves the changes.
The system updates the existing Workflow according to the Prompt, instead of creating a new Workflow.
You can also create workflows together with a new entity.

Main uses

Updating existing Workflows using natural language instructions.
Adding, removing, or changing Actions inside a Workflow.
Changing the settings of existing Actions.
Changing field mappings.
Adapting an existing Workflow to a new business requirement.
Making changes across several steps of a Workflow without needing to go through all the settings manually.
Fixing or adapting an existing Workflow without creating a new Workflow.

Who it’s for

System administrators – for quickly updating existing processes, without going through all the Workflow settings manually.
Implementation specialists – for adapting existing Workflows to different customer needs.
Automation developers – for making quick changes to existing processes.
Business users – who want to describe a desired change in natural language instead of knowing the full technical structure of a Workflow.
Operations teams – for adapting existing processes when work requirements change.
Support teams – for fixing or adapting existing Workflows according to a need that came up during work.

What it solves / examples

This capability extends what Vision can do, from creating new Workflows to editing and updating existing Workflows. The user does not need to create a new Workflow every time a change is required, and can make adjustments directly through a Prompt.
Example 1 – Adding an action:
The user asks Vision: “Add sending an Email after the record is updated.” Vision identifies the existing Workflow and adds the Action in the right place.
Example 2 – Changing an existing Action:
The user asks to change an Action so that instead of updating one field, it updates another field. Vision identifies the relevant Action and updates its configuration.
Example 3 – Changing logic:
The user asks to change the condition under which the Workflow runs, for example: “Run the process only when the status changes to Approved.” Vision updates the existing logic accordingly.

Payments: Payment Links and Payment Gateway Connections

Origami collects money now. The new Payments app connects to payment providers such as Cardcom, Pelecard, and Tranzila, generates a payment link from a Workflow, sends it to the customer as a branded payment page that requires no login to the system, and updates the record automatically the moment the payment goes through. With amount and currency verification, duplicate charge prevention, and a Simulator for testing before you go live.

Step by step

For the system administrator / implementer

Create a new page of the application type.
Go to the Payments app and configure a connection to one of the supported payment providers, such as Cardcom, Pelecard, or Tranzila.
Configure the required connection settings for the account/terminal.
You can use the Simulator for testing, or a real Gateway connection for actual processing.
Configure a Workflow that generates a Payment Link for a business record.
The system creates a payment link and saves it on the relevant record.
Send the link to the customer through the appropriate channel.
The customer opens the link and reaches a branded Origami payment page.
The customer enters the payment details and completes the transaction with the payment provider.
The system verifies the payment against the Gateway and makes sure the amount and currency match the payment request.
After a successful payment, the payment status is updated and the system can update fields on the original record using the On-paid settings.
The system administrator can track the transactions and KPIs from the payments Dashboard.
In case of a retry or a duplicate callback, the system identifies the event and prevents a duplicate charge/update.

Main uses

Creating Payment Links and sending them to customers.
Receiving payments through external payment providers.
Support for several Payment Gateway connections.
Tracking payment requests and transactions.
Automatic update of the CRM record after payment.
Preventing a duplicate charge in case of a callback or a retry.
Verifying that the amount and currency paid match the payment request.
Using the Simulator for testing before working with a real Gateway.
Displaying payment and transaction data in a Dashboard.
Support for public payment pages that do not require the customer to log in to Origami.

Who it’s for

Businesses that receive payments from customers – create payment links and send them to customers instead of collecting manually.
Sales teams – can send the customer a payment link directly from within the sales process.
Service and operations teams – can track payment statuses and update the customer record accordingly.
Finance / Billing managers – get documentation of requests and transactions and tracking of completed payments.
Solution Builders – can build automations that respond to a payment, for example updating a status, a field, or a business figure after payment.

What it solves / examples

Collecting through a payment link
For example, a sales rep creates a Payment Link for a transaction of 150 NIS and sends it to the customer. The customer pays through the payment page, and the transaction is recorded in the system.
Automatic update after payment
After the customer has paid, the original record can be updated automatically, for example changing Payment Status to Paid.
Preventing a duplicate charge
If the payment provider sends the same event more than once, the system identifies that the event was already handled and does not perform the actions on the transaction again.
Protection against amount tampering
If someone tries to change the payment amount during the payment process, the system compares the amount paid to the original amount and prevents accepting a payment that does not match the request.
Testing the connection before Production
An administrator can use the Simulator to test the entire link creation and payment process before connecting to a real Gateway.
Working with different payment providers
You can configure connections to different providers, so the system is not dependent on a single payment provider.
Payment without logging in to Origami
The customer receives a public payment page and can complete the payment without needing an account or a Session in the system.
Full example:
A service company sends a customer an invoice for 150 NIS. A rep creates a Payment Link from Origami and sends it to the customer. The customer opens the link, pays using Cardcom, and the system verifies that the transaction was indeed made for 150 NIS. After the payment is approved, the transaction is marked as Paid, the original record is updated according to the On-paid settings, and the transaction appears in the Payments Dashboard.

KPI Field: The Aggregated Figure Sits on the Customer Record

How many orders does this customer have? How much revenue did they bring in this year? Until now the answer lived only in the KPI Dashboard. The new KPI field calculates a count or a sum from linked records and saves the value on the parent record itself, so you can filter by it, sort by it, export it, and run Workflows on it. The value updates automatically when the child records change.

Step by step

Go to edit a field group and create a new field of the KPI field type.
Select the entity that has a link field to the current entity, on which you want to perform the aggregation. That is, the child entity from which you want to calculate the figure, for example Orders.
Select the link field to the entity where we are creating the field. That is, the link field that connects the child record to the parent record, for example Client.
Select the type of calculation you want to perform:
- Count – the number of records linked through the link field we selected.
- Sum – the sum of a numeric field (a text field in numeric value format only) in the linked records.
In the case of Sum, select the numeric field on which the calculation will be performed, for example Amount.

The selection is made from text fields with a numeric value. That is, if you want to sum the cost of expenses across all the orders the customer placed, you need to make sure that in the Orders entity, the field showing the expense for each order is a text field formatted as a numeric value only.

Choose whether to include records that are in the archive (in the child entity, the entity on which the aggregation is performed).
Save the field.
The system calculates and saves the value automatically.
When the child records change, the value updates automatically after asynchronous processing.
The user can use the value like a regular numeric field – view it, filter, sort, export, and use it in Workflows.
The field itself is Read-only and cannot be edited manually.
If there are not enough Workflow Operations for recalculation, the last value is kept and the field is marked as Stale, without blocking the saving of the child record.

Main uses

Counting child records – for example the number of orders of a customer.
Calculating an aggregated sum – for example total revenue from all the orders of a customer.
Filtering and sorting by an aggregated figure – for example displaying customers with revenue above 100,000 NIS.
Using the figure in Workflows – for example running a process when the number of orders of a customer passes a certain threshold.
Exporting data – bringing rollup data into reports and exports from tables.
Using it in documents and the API – the value is saved as part of the parent record and can therefore be consumed outside the KPI Dashboard as well.

Who it’s for

Solution Builders / Implementers – who want to build relationships and calculations between entities without writing code.
CRM and sales managers – who want to see aggregated figures on the customer record, such as the number of deals or Total Revenue.
Operations managers – who want to manage parent records by figures accumulated from sub-records.
Service team managers – for example seeing how many open/historical tickets are linked to a customer.
Users who work with tables and reports – can filter and sort by the aggregated value, unlike the KPI Dashboard which performs a live calculation only.

What it solves / examples

Total sales per customer
Before: you could see a sales KPI in a Dashboard, but there was no saved value on the customer record.
After: you can create a KPI of the Sum type on Orders → Amount, and the sum is saved directly on the customer.
Number of orders per customer
Create a KPI of the Count type connected to Orders. If a customer has 27 orders, the KPI field will display 27.
Filtering customers by revenue
For example, you can filter a Clients table to show only customers with Total Revenue > 100,000.
Sorting by activity
You can sort customers by their number of orders, from the customer with the most orders downward.
A Workflow based on an aggregated figure
For example: when the total of a customer orders changes and passes a certain threshold, a Workflow can be triggered based on the new value.
Deleting/updating an order
If an order is deleted or its amount changes, the KPI of the relevant customer is updated automatically.
Moving a record between customers
If an order moves from customer A to customer B, the system updates the KPI of both customers, subtracting from the first and adding to the second.

Origami Schedule: Every Appointment Booking Form on One Screen

A new app that brings together all the Web forms used for booking appointments. Instead of opening every form separately to check whether it is active and how many appointments were booked through it, you get one Dashboard with the status of each form, the number of upcoming appointments, booking statistics over time, and a Booking Funnel that shows exactly where people drop off.

Step by step

The user adds a new page of the application type.
The user goes to the new Origami Schedule app.
The main screen displays a central Dashboard of all the Web forms in the system that contain a Calendar field and are used for booking appointments.
The user sees all the booking forms in one place, without needing to open each Web Form separately.
For each form, key management details are displayed:
- The form name.
- Whether the form is active.
- The entity the form is assigned to.
- Whether the booking link is open and available to bookers.
- The number of upcoming appointments.
- Additional data related to the activity of the form.
The user can select a specific form from the list and continue to manage it or view its details.
The Dashboard displays general statistics of booking activity over time, so you can see the volume of appointments in different periods and identify trends.
In addition, a Booking Funnel is displayed, showing the process users go through from arriving at the booking page to completing a booking.
Using the consolidated data, the user can understand which booking forms are active, how many appointments are expected, and what the usage and conversion level of the booking process is.

Main uses

Bringing all the appointment booking forms together in one place.
Tracking the status and activity of each form.
Viewing the number of upcoming appointments for each form.
Tracking the volume of bookings over time.
Analyzing the performance of the booking process using the Booking Funnel.
Identifying forms that are not active or whose booking link is not open.
Getting a central picture of appointment booking activity in the system.

Who it’s for

System administrators and Solution Builders who manage several Web Forms used for booking appointments and want to manage them from a central screen.
Sales managers who run several forms for booking a Demo or sales calls and want to track the volume of appointments.
HR managers who manage forms for booking interviews and want to see the activity volume of each form.
Support / Customer Success managers who let customers book meetings through several forms and want to track the appointments and performance.
Operations managers who want to identify which booking forms are active, how many appointments are expected, and what their usage status is.

What it solves / examples

No need to look for booking forms separately
Instead of opening every Web Form to check whether it is active and how many appointments were booked through it, all the forms appear in a central list in the app.
A full picture of the entire booking setup
For example, an organization runs 10 appointment booking forms for Sales, HR, and Support. The Dashboard displays all of them and makes it easy to quickly understand which forms are active and how many upcoming appointments exist in each one.
Tracking upcoming appointments
You can see that one form includes, for example, 35 upcoming appointments, while another includes 0, and identify differences in activity.
Tracking trends over time
The statistics graph lets you see how many appointments were booked each day and identify periods of rising or falling demand.
Booking Funnel analysis
You can see the transition between the booking stages, for example users who arrived at the booking page, viewed availability, started the Booking process, and finally completed it. This makes it possible to identify where users abandon the process.
Identifying problems in forms
If a certain form is not active or its link is not open, you can identify this directly from the Dashboard instead of discovering it only after a customer reports that they cannot book an appointment.

Export Invoices to Hashavshevet in One Click

Month-end just became a one-minute task. Choose a company and a date range, click export, and get a ZIP file with the import files in Hashavshevet format, ready for direct import. No manual typing, no conversions, including foreign currency documents and automatic matching to the bookkeeping accounts of each company.

Step by step

Go to the Invoicing app.
Go to the settings, to the company you want to connect.
Check the Export to Hashavshevet option.
Set the date range of the documents to export.
Click Export.
The system creates and downloads a ZIP file containing the import files in the format supported by Hashavshevet.
Import the files directly into Hashavshevet using its built-in import mechanism.

Main uses

Exporting invoices and receipts directly to the Hashavshevet import format.
Selecting a company and a date range before performing the export.
Support for documents in local currency and in foreign currency.
Automatic matching to the bookkeeping accounts defined for each company.
Creating import files that are ready to use with no need for manual conversions.

Who it’s for

Bookkeeping teams.
Finance managers.
System administrators.
Organizations that use Hashavshevet for bookkeeping.

What it solves / examples

Removes the need for manual typing or data conversion before importing into Hashavshevet.
Makes it possible to transfer a large volume of invoices and receipts quickly and consistently.
Keeps the data in Origami aligned with the Hashavshevet system.
Also supports documents in foreign currency and their conversion according to the relevant exchange rates.
For example: at the end of the month, the bookkeeper selects a company and a date range, downloads the ZIP file that was created, and imports it directly into Hashavshevet, so all the invoices and receipts are taken into the system with no manual work.

Saving Filters in All Widget Types

Until now filters could only be saved in Datatable and Sortable List. In every other widget the user set the same conditions again on every visit. From this version, saving filters is available in all widget types, so the behavior is consistent and the dashboard opens in the morning with the view you want.

Step by step

The user goes to a screen where some Widget is displayed.
The user opens the filtering options of the Widget.
The user defines the desired filter conditions.
The user selects the Save Filter option.
The system saves the filter settings and lets the user use them again.
The user can return to the Widget and select the saved Filter instead of defining the same filter conditions again.
The option to save Filters is available for all Widget types.

Main uses

Saving common filters for reuse.
Saving time on defining the same filter conditions over and over.
Saving custom views for different types of Widgets.
Creating dedicated filters for different business needs.
Keeping consistency in the way users filter information in the system.

Who it’s for

Users who work with Dashboards – and need to save different filters for different Widgets.
System administrators – who want to define and save useful information views for different types of Widgets.
Managers – who need to regularly view data according to certain conditions.
Sales and service teams – for example saving filters by status, customer, region, or rep.

What it solves / examples

Today Filters can be saved only in Datatable and Sortable List Widgets. For the other Widget types, the user has to define the same filter conditions again every time they return to the Widget. The change makes it possible to save Filters in all Widget types, making the behavior consistent and more convenient.
Example 1 – Dashboard:
The user displays a Widget showing customer data and defines a Filter that shows only active customers. The user saves the filter and can run it again in the future with one click.
Example 2 – Task tracking:
The user wants to see only tasks that have not been completed and whose due date is within the coming week. Instead of defining the conditions again on every visit, they save the Filter and use it again.
Example 3 – Several Filters for the same Widget:
The user works with a certain Widget and wants to save several scenarios:
- New customers
- Active customers
- Customers with no recent activity. Each Filter is saved separately and can be chosen as needed.
Example 4 – A Widget type that is not Datatable or Sortable:
The user works with another type of Widget that does not currently support saving Filters. After the change, they can define a Filter, save it, and return to it later exactly as in Datatable and Sortable List.
Example 5 – Daily work:
A user opens the same Dashboard every morning and wants to see the same filtered data. Instead of defining several conditions again every day, they run the saved Filter and immediately get the view they want.

Quick Export of the Audit Trail to PDF or CSV

The full change history of a record, in one file, with one click. PDF for documentation and sharing, CSV for analysis in Excel. The file also includes the export details themselves: who exported, when, which record, and how many rows. The export action itself is also logged in the Audit Trail. Anyone who works with Compliance or auditing will immediately understand why this matters.

Step by step

The user goes to the desired record.
The user opens the Audit Trail of the record.
The user selects the desired date range or filters, if such exist.
The user clicks Quick Export.
The system exports the Audit Trail data that the user is permitted to view.
The user receives the file in the supported format, PDF or CSV, according to the approved requirement.
The file includes the Audit Trail data as well as information about the export itself, such as the user who performed the export, the export date and time, the record, and the number of rows.
The export action is also logged in the Audit Trail as a new event.

Main uses

Exporting the full Audit Trail of a record.
Saving the action history as a PDF file for documentation, sharing, or archiving.
Exporting to CSV for working with the data in Excel or other analysis tools.
Exporting history after applying a date range or filters.
Sharing the action history with support, IT, Compliance, or business stakeholders.

Who it’s for

System administrators – for documentation and control of changes to records.
Compliance and audit teams – for producing and keeping Audit Trail reports.
Support and IT teams – for investigating changes and actions performed on records.
Managers and process owners – for reviewing the activity history of records.
Users who need a documented file – can use the PDF for presentation or sharing.
Users who need to analyze the data – can use the CSV and process the data in Excel or an external tool.

What it solves / examples

The feature lets the user pull the Audit Trail quickly and in a useful format, without manually copying the information or going through a complex export process.
Example 1 – Formal documentation:
The user is required to hand over documentation of all the changes made to a record. They use Quick Export and produce a PDF file that can be saved or shared as a documented file.
Example 2 – Data analysis:
The user wants to analyze the actions performed on a record over time. They export the Audit Trail as CSV and open it in Excel for filtering, sorting, and analysis.

Call Summary Supports HTML: Structured Call Summaries from the PBX

When an AI or PBX system generates a call summary with headings, paragraphs, and lists, there is no reason for it to arrive in Origami as flat text. The Call Summary field now supports HTML through the API, preserves the structure and formatting, and holds long content of up to about 10,000 characters.

Step by step

The user goes to the PBX application page, or to an entity where an Omni Channel connected to the PBX is configured.
The user goes to the relevant customer record, or to the row documenting the relevant call.
The user opens the Call Summary using the eye button (on the application page), or using the dedicated button in the call documentation in Omni.
Through an API call, content in HTML format can now be sent to the field.
The system receives the HTML content and saves it in the field properly.
When the record is displayed, the Call Summary content is shown to the user in HTML format and not as plain text.
The structure of the content is preserved in the display, including elements such as headings, paragraphs, lists, and emphasis.
The field also supports long content, including values of up to about 10,000 characters.

Main uses

Transferring call summaries from a PBX system through the API.
Receiving call summaries that are generated automatically in HTML format.
Preserving the structure and formatting of content coming from an external system.
Displaying long, detailed call summaries.
Transferring content that includes headings, paragraphs, lists, and additional HTML elements.

Who it’s for

Sales teams – for displaying call summaries that arrive automatically from the PBX system.
Service and support teams – for keeping call summaries that include a breakdown of the problem, the solution, and Next Steps.
Organizations that use AI systems – when an external system generates a structured call summary in HTML.
PBX systems and external integrations – for transferring rich, structured information directly into the Call Summary.

What it solves / examples

Today Call Summary is a regular text field, so HTML content arriving from an external system may lose its structure and formatting. The change makes it possible both to receive HTML content through the API and to display it as HTML in the field.
Example 1 – A summary generated by AI:
An AI system generates a summary that includes:
- A call abstract
- Topics raised
- Customer requests
- Next Steps. The content is sent to Call Summary as HTML and displayed on the record in the same structure.
Example 2 – Long content:
A PBX system generates a call summary of about 10,000 characters. The content is sent through the API and received in the field without truncation, and is then displayed correctly to the user.
Example 4 – Formatted content:
The API sends content that includes HTML tags such as headings, paragraphs, and lists. Instead of displaying the HTML tags as part of the text, the system interprets them and displays the content in a formatted way.

A Dedicated URL for Every Page in Entity Settings

Every page in the entity settings now has its own address: fields, views, workflows, recycle-bin, forms-documents. Internal Tabs such as Visual Editor or Documents get a dedicated URL that opens directly too.

Step by step

Go to the Entity Settings of an entity.
Every main page in the settings has its own dedicated URL.
You can navigate directly to the Fields page using /fields.
You can navigate directly to the Views page using /views.
You can navigate directly to the Workflows page using /workflows.
You can navigate directly to the Recycle Bin using /recycle-bin.
You can navigate directly to Forms & Documents using /forms-documents.
You can return directly to the main Entity Settings page using /entity-settings.
Internal pages or Tabs inside the settings also get a dedicated URL, for example:
- /fields/visual-editor
- /forms-and-documents/documents
When a user enters the URL of an internal Tab, the system opens the matching Tab directly instead of opening the main page.
You can save or share a specific URL, and when a user opens it they arrive directly at the relevant screen.

Main uses

Direct navigation to a specific page in entity settings.
Sharing a direct link between team members.
Saving Settings pages as Favorites/Bookmarks.
Opening internal Tabs directly.
Improved navigation and Browser history.
Creating stable URLs for training, Support, and documentation.

Who it’s for

System administrators – who manage the entity settings and need to reach a certain screen quickly.
Solution Builders – who work regularly with Fields, Views, Forms, and Workflows.
Support specialists – can send a user a direct link to the screen where a change or a check is required.
Implementers and Implementation specialists – can use a direct URL as part of training or a configuration process.
Team managers – can share specific links to settings with other users.

What it solves / examples

Cumbersome navigation inside Settings
Before: a general URL for the entity settings did not allow reaching the desired page directly.
After: every page has its own URL.
Sharing a link to Fields
Instead of explaining to a user to go to Entity Settings and then choose Fields, you can send them directly to /fields.
Opening the Visual Editor directly
You can save or share a URL that leads directly to /fields/visual-editor, instead of first opening Fields and then choosing the editor.
Opening Documents directly
A URL such as /forms-and-documents/documents will open the Documents Tab directly and not the first page of Forms & Documents.

Enter in Smart Search Opens View All

A small improvement you feel on every search. Type, press Enter, and get all the results, without reaching for the mouse halfway through. And if there is an active Autocomplete suggestion, Enter still selects it exactly as before.

Step by step

The user opens Smart Search.
Enters a search word or a value to search for.
The system displays the relevant search results/suggestions.
The user presses Enter on the keyboard.
The system automatically opens the View All window with the search results.
This behavior is identical to manually clicking the View All button.
If the search field is empty, the behavior is identical to clicking View All when the field is empty.

Main uses

Opening the full search results using the keyboard.
Fast searching without needing to move from typing text to the mouse.
Improved user experience in Smart Search.
Support for a fast workflow for users who prefer keyboard navigation.

Who it’s for

All Origami users who use Smart Search to find records and information.
Users who work mainly with the keyboard and need to perform many searches in a row.
Service, sales, and Operations staff who perform frequent searches in the system.
Users who search for values that do not appear in the initial suggestions and need to move to the full results.

What it solves / examples

Enter that does nothing
Before: the user types John Smith, presses Enter, and nothing happens. To see all the results they have to click View All manually.
After: pressing Enter opens the View All results directly.
Searching without needing the mouse
The user can perform the whole action using the keyboard: type, Enter, get all the results.
Preserving Autocomplete
If there is an active suggestion, Enter still selects it instead of opening View All, so the change does not harm the existing search behavior.
Consistent behavior
Enter triggers the same action that is triggered by clicking View All, so there are no two different navigation logics for the same result.

Support for SolidWorks Files in the File Upload Field

Industrial and engineering organizations manage design in SolidWorks and the business process in Origami. From now on you can attach the part and drawing files directly to the record, with no conversions and without keeping them in a separate place.

Step by step

The user goes to a form or a record that has a File Upload Field.
The user clicks the file upload field and selects a file from the computer.
The user can also upload files in the SLDPRT and SLDDRW formats.
The file is uploaded and saved in the field according to the system settings.

Main uses

Uploading engineering design and CAD files.
Keeping part and drawing files as part of the record.

Who it’s for

Intended for users who work with SolidWorks files and want to attach them to records in the system.

What it solves / examples

The update expands the file types supported in the file upload field and makes it possible to upload also:
.SLDPRT – a SolidWorks part file.
.SLDDRW – a SolidWorks drawing file.

Support System Improvements: Ticket Number, Search, and Filtering

The support portal ticket number now appears directly in the ticket list inside Origami, identical to the number you see at support.origami.ms. You can quote it without opening the ticket, search for tickets in the search bar, and filter all of them by status.

Step by step

The user goes to Support from within the Origami environment.
The system displays the list of tickets the user opened through the Origami environment.
For each ticket, the support portal Ticket ID / ticket number is also displayed.
The ticket number displayed is identical to the Ticket number that appears in the support.origami.ms portal.
The user can copy or quote the ticket number when contacting the support team, without opening the ticket.
Clicking the button/link to open the ticket continues to direct the user to the matching ticket in the portal with no change to the existing behavior.
The user can search for tickets in the search bar.
All the tickets can be filtered by their status.

Main uses

Quickly identifying a ticket by number.
Quoting a ticket number to the support team.
Finding a specific ticket without needing to open it.

Who it’s for

Origami users who open support tickets and need to point the support team to a specific ticket.
Support specialists who manage tickets in the portal and want the user to be able to provide the same ticket number that appears on their side.
System administrators / Operations specialists who track support tickets and need to identify a ticket between the Origami environment and the support portal.

What it solves / examples

Identifying a ticket without opening it
Before: the My Tickets list showed only a title, status, and date, so to know the ticket number you had to open it.
After: the ticket number appears directly in the list.

Origami User ID in the User Export

Names and email addresses change, an identifier does not. An Origami User ID column was added to the user export, both in the All Users sheet and in the group sheets, as full text with no truncation or lost digits.

Step by step

Go to User Management.
Select the option to export the user list to an Excel file.
The system exports the users according to the existing filtering and grouping.
In the All Users sheet, a new column named Origami User ID appears.
In each user row, the matching Origami User ID appears for that user.
The same column with the matching ID also appears in the user group sheets.
The ID can be used as text, with no format change, truncation, or lost digits.
The rest of the export columns, the filtering, and the grouping remain unchanged.

Main uses

Unambiguous identification of users exported from the system.
Cross-referencing exported users with data from other systems or APIs.
Using the User ID for support, data analysis, and administration purposes.
Working with user data outside the Origami interface.

Who it’s for

System administrators who export user lists for management and control purposes.
IT and Support specialists who need to identify a specific user by their internal ID.
Operations / Data specialists who cross-reference user data from different sources.
Implementers and integration specialists who need to link Origami users to identifiers in other systems.

What it solves / examples

Unambiguous identification of a user
Names and email addresses can change or may not be unique, while the Origami User ID makes it possible to identify the user unambiguously.
Cross-referencing data
A manager exports users and processes the file in an external system. The Origami User ID makes it possible to link each row to the matching user in the system.
Working with groups
Even when the export is split into sheets by group, the ID is kept in every user row, so the user can be identified regardless of which sheet they are in.

In Summary

Version 6.3.5 moves Origami forward in three directions. AI that genuinely feeds the business process, with model selection, Context from related records, and structured responses, and Vision that now builds and updates Workflows from a Prompt. Money coming in, with a full payments system, payment links, payment gateway connections, and direct export to Hashavshevet. And data that sits in the right place, with an aggregated KPI field on the customer record, an appointment scheduling app, Audit Trail export, and dozens more improvements that came from the field.

If you have questions about the version, or want to know how to get the most out of it, contact us and we will be glad to help.