Origami Version 6.3.4: Major WhatsApp Upgrade, Financial Dashboard, Background Export, and More

Version 6.3.4 arrives with an impressive package of updates: a comprehensive upgrade to the WhatsApp app, including full templates, automatic field mapping, and complete transparency in account management, alongside a wide-ranging upgrade to the finance module, background export of large reports, calendar improvements, and more. Every one of these improvements came from the field, directly from the teams that work with Origami every day.

WhatsApp Template Upgrade: Full Message Structure Support

WhatsApp templates in Origami have gone through a comprehensive upgrade. You can now build templates with every message component the Meta API supports: Header (text, image, or document), Body with dynamic parameters, Footer, and action buttons of the Call to Action and Quick Reply types. The highest standard Meta allows, now inside Origami.

Step by step

Go to the WhatsApp app settings.
Create a new template or edit an existing one.
Define a Header (text, image, or document).
Enter the message content (Body), including parameter definitions as needed.
Add a Footer as needed.
Define action buttons (Call to Action or Quick Reply).
Save the template and submit it to Meta for approval.

Main uses

Creating rich, well-designed WhatsApp messages.
Adding images, documents, and action buttons to messages.
Sending marketing, service, and personalized messages.

Who it’s for

Sales staff.
Service and support teams.
Operations teams.
System administrators.

What it solves / examples

Lets you build advanced WhatsApp templates with every message component supported by Meta.
Creates a richer, more interactive communication experience with customers.
For example: sending a product message that includes a product image, a description, and an “Order now” button, or a service message with “Resolved” / “Still need help” buttons.

Field Mapping for WhatsApp Templates: Manual Sending with Dynamic Values

Until now, sending a WhatsApp template with variables required creating a Workflow. Now you can map every variable in the template to a field in the entity, and send it manually straight from the Omni Widget, with the system filling in the values automatically from the record. It works in Workflows too, where the mapping you defined loads automatically.

Step by step

The user goes to the WhatsApp template settings.
Opens the settings of an existing, approved template, or creates a new template.
Moves to the Field Mapping area.
Selects the relevant entity.
Maps every variable in the template (and dynamic URL buttons, if there are any) to a field in the entity.
Saves the mapping.

Sending a template from the Omni Widget

The user opens a record in the relevant entity.
Opens the Omni Widget.
Selects a WhatsApp template.
The system fills in the variables from the record according to the mapping that was defined.
If all the values are present, the message is sent.
If one of the fields is empty, an error message is displayed and sending is blocked.

Using a template inside a Workflow

The user selects a template in a Workflow action.
The system automatically fills in the variable mappings according to the mapping defined in the template.
The user can change the mapping if needed.
Saves the Workflow.

Main uses

Sending WhatsApp templates with variables directly from Omni.
Using the same template on different screens without needing to create a Workflow.
Defining a single, consistent mapping for each template.
Saving time when defining variables in a Workflow.

Who it’s for

Service reps who send WhatsApp messages from the customer record.
Sales reps who send quotes, reminders, and updates to customers.
CRM managers who manage WhatsApp templates with dynamic fields.
Origami implementers who set up templates for system users.
Automation managers who build Workflows for sending WhatsApp messages.

What it solves / examples

Lets you manually send templates with variables from the Omni Widget and the conversation list.
Removes the need to create a Workflow just to fill in template variables.
Automatically fills in the variable values from the matching record.
Prevents templates that are not mapped, or that do not match the current entity, from being displayed.

WhatsApp Improvements: Template and Account Management

A package of improvements that makes day-to-day work with WhatsApp smoother: a template counter, statuses refreshed from Meta, rejection reasons shown in place, visual marking of active accounts, and template duplication with a single button. Every one of these improvements was born from a specific pain that came up in the field: whether it is the need to understand why a template was rejected without leaving for Meta Business Manager, or knowing in a second whether an account is active before trying to send. When you manage dozens of templates across several accounts, each of these improvements is worth valuable time in the working day.

Step by step

The user goes to the WhatsApp template list.
The system displays the number of existing templates in that app (the limit is 32 templates).
The system refreshes the template statuses against Meta.
If a template was rejected:
- The status is displayed as Rejected.
- The user sees Meta’s rejection reason, either through a Tooltip or as a note in the status row.
- Active accounts can be identified visually: a green dot appears next to the account (an inactive account will have a gray dot).
The user can duplicate an existing template. Clicking the duplicate icon opens a new template with the full details of the selected template. The template is given a default name, template_name_copy. The variables can be changed as needed, and the template saved.

Main uses

Understanding the reasons for WhatsApp template rejections.
Managing a larger number of templates across several accounts.
Quickly creating new templates based on existing ones.
Improved transparency for users who work with WhatsApp at scale.

Who it’s for

WhatsApp managers in the organization who are responsible for connecting WhatsApp Business accounts and managing templates with Meta.
CRM managers who set up workflows and automations that include sending WhatsApp messages.
Marketers who manage WhatsApp campaigns and templates for customer groups.

What it solves / examples

Saves time when creating templates.
Provides certainty about the status of a template.
Makes working with the WhatsApp app in the system easier.

WhatsApp Improvements: Service Window Transparency in Omnichannel

When a rep opens a WhatsApp conversation in Omnichannel, they see exactly how much time is left in the free 24-hour sending window. If the time has passed, they get clear guidance to send a template in order to reopen the conversation. And if a template with mapped fields is selected, the values load automatically from the record. It may sound like a small technical improvement, but in practice it prevents dozens of errors a day: reps who did not know the window had closed tried to send free messages that never went out, and templates with empty fields reached customers with a visible “{{1}}”. Both of those problems are solved here.

Step by step

The user opens a WhatsApp conversation in Omnichannel.
The system checks when the last message from the customer was received.
If the customer sent a message within the last 24 hours, a message is displayed showing how much time is left in the free sending window. If more than 24 hours have passed, a message appears explaining this and directing the user to send a template in order to reopen the conversation (in line with Meta rules).
If the user selects a template with variables mapped to the record (another feature in this version), the system loads the values from the entity.
If one of the mapped fields is empty:
- Sending is blocked.
- A clear error message is displayed, including:
  - The variable name.
  - The name of the missing field.

Main uses

Preventing messages from being sent with missing information.
Preventing send failures caused by the WhatsApp service window limit.

Who it’s for

CRM managers who manage WhatsApp conversations in Omnichannel.
Customer service reps who answer customers through WhatsApp and need to know whether a free message can be sent or a Template is required.
Business managers who rely on template sending and want to work with dynamic values.

What it solves / examples

Prevents uncertainty about templates that were not sent for some reason.
Streamlines work with WhatsApp templates in line with Meta rules.
Enables sending more accurate and more flexible templates to customers.

A Major Upgrade to the Invoicing App

Version 6.3.4 brings the biggest upgrade the Origami invoicing app has ever received: a brand-new financial dashboard, full ITA support (the Israel Tax Authority), usability improvements, smarter foreign currency handling, a financial widget for dashboard pages, and a new revenue report. Everything you need in order to manage finances directly from Origami, with no spreadsheets and no external systems.

Financial Dashboard, Invoice Improvements, and ITA Support

The invoicing app has a new face: a financial dashboard that brings the key figures together on a single screen, usability improvements that speed up work on line items, tracking of ITA Token validity for continuous work with the Israel Tax Authority invoicing model, and new, faster navigation between the app screens. Everything a finance manager needs to see, in one place, including in multi-company environments.

Step by step

Go to the Invoicing app.
The main screen displays a new financial dashboard showing the key figures on invoice activity.
When creating or editing an invoice, you benefit from usability improvements on the line items, such as duplicating rows, adding several rows at once, reordering by dragging, and moving quickly between fields.
If needed, you can set and track the ITA Token validity in the settings screen.
Use the new navigation in the app to move quickly between the different screens.

Main uses

Viewing financial metrics through a central dashboard.
More convenient and faster management of invoice line items.
Tracking ITA Token validity for continuous work with the Israel Tax Authority invoicing model.
Fast, convenient navigation between the invoicing app screens.
Accurate financial data display, including in multi-company environments.

Who it’s for

Bookkeeping teams.
Finance managers.
System administrators.
Users who manage invoices and billing processes in the system.

What it solves / examples

Brings the important financial information together on one screen and makes it easier to track invoice activity.
Significantly improves the working experience when creating and editing invoices, through quick actions on the line items.
Lets you track the ITA Token validity and prevent issues caused by expiration.
Improves the accuracy of the calculations and financial metrics in the dashboard, including work with several companies, ignoring canceled invoices, and correct calculation of financial metrics.
For example: a finance manager can see the activity status of all the companies in the dashboard, quickly edit an invoice by duplicating and reordering rows, and confirm that the ITA Token is still valid before issuing invoices.
In a multi-company setup, you can define whether a company is active or inactive, so that an inactive company is not available for selection, for a more convenient user experience.

Improved Foreign Currency Support in Invoices

Invoices in dollars, euros, or pounds? From version 6.3.4, working with foreign currency is simpler and more accurate: choose a currency from the currency list, set an exchange rate manually or use the automatic rate (the representative exchange rate from the Bank of Israel), and the invoice amounts are displayed both in the selected currency and in the base currency. Businesses that work with international customers, or with dollar-denominated agreements in Israel, get full control and accuracy.

Step by step

Go to create or edit an invoice.
Select the currency you want from the currency list.
Set the exchange rate manually, or use the automatic rate (the representative exchange rate from the Bank of Israel).
Continue filling in the invoice details as usual.
The invoice amounts will be displayed both in the selected currency and in the base currency, according to the exchange rate that was set.

Main uses

Issuing invoices in different currencies for customers in Israel and abroad.
Setting exchange rates manually or automatically.
Displaying the invoice amounts in the foreign currency and the base currency side by side.
Improved control and accuracy when working with foreign currencies.

Who it’s for

Bookkeeping teams.
International sales teams.
Managers.
Organizations that work with customers in different currencies.

What it solves / examples

Makes managing foreign currency invoices simpler and more accurate.
Helps issue invoices to international customers while also showing the value in the local currency.
Makes financial tracking and reporting easier when working with several currencies.
For example: an Israeli company that signs a dollar-denominated agreement with an Israeli customer can issue an invoice in dollars, while the amount in shekels is also displayed according to the selected exchange rate.

Financial Documents Widget Upgrade: All Documents in One Place

The financial documents widget has received a significant upgrade: instead of a separate widget for each document type, a single widget displays a unified list of all the document types defined for it, such as tax invoices, receipts, proforma invoices, and credit notes, with quick filtering by document type and the option to create a new document directly from the widget. Fewer widgets on the dashboard, a fuller picture.

Step by step

The user goes to the screen or dashboard where the financial documents widget was added.
The user views a unified list of all the document types defined for the widget (for example: tax invoices, receipts, proforma invoices, and credit notes).
The user filters the list by document type using the filtering options at the top of the widget.
The user opens the document they want, or performs the available actions on it.
If needed, the user creates a new document directly from the widget and selects the document type they want.

Main uses

Displaying several types of financial documents in a single widget.
Switching quickly between document types using filtering.
Saving space on the dashboard instead of using several separate widgets.
Viewing documents of all types together in chronological order.
Creating new documents directly from the widget.

Who it’s for

Bookkeeping team.
Finance managers.
Managers.
System administrators.

What it solves / examples

Removes the need to add a separate widget for each type of financial document.
Lets you see invoices, receipts, proforma invoices, credit notes, and additional document types in one place.
Makes day-to-day work easier by switching quickly between document types without leaving the widget.
For example: a finance manager can add a single widget that displays all the document types, filter with one click to show only receipts or only tax invoices, and create a new document directly from that same widget.

Revenue Report

A new revenue report that brings all the income documents together in one place: invoices, credit notes, and tax receipts, by date range, with automatic calculation of the amount before VAT, the VAT, and the total. The report also supports documents in foreign currency with the option to convert the amounts to shekels, and it can be exported for work with bookkeeping, with no need to produce several different reports and no manual calculations.

Step by step

Go to the Invoicing app and select the Revenue Report.
Set the date range you want.
Choose whether to display the data in the original currency or convert it to shekels.
Run the report.
The system displays all the relevant income documents in an organized table, including invoices, credit notes, and tax receipts.
If needed, the report can be exported for work with bookkeeping.

Main uses

Producing a consolidated revenue report by date range.
Displaying all the income documents in one place.
Automatic calculation of the amount before VAT, the VAT amount, and the total.
Support for documents in different currencies, including the option to display the amounts in shekels according to the exchange rate.
Exporting the report for accounting work and control.

Who it’s for

Bookkeepers.
Finance managers.
Managers.
Users of the finance app.

What it solves / examples

Brings all the income documents together in a single report instead of producing several different reports.
Enables accurate financial control over revenue in a given period.
Automatically shows the transaction amount before VAT, the VAT, and the total, with no need for manual calculations.
Supports working with documents in foreign currency and converting them to shekels when needed.
For example: a finance manager selects the month of July, runs the revenue report, and receives a full list of all the invoices, receipts, and credit notes, including amounts before VAT, VAT, the total, and conversion to shekels for reporting and control.

Large Report Export in the Background: Keep Working, the Report Will Wait for You

Exporting large reports from Origami now runs in the background, so you keep working without waiting and get a notification the moment the file is ready, with a download button right inside the notification. Until now, exporting more than 2,000 records was blocked with an error message. From now on the system simply offers to run the export in the background, and that limit disappears.

Step by step

Go to the view or report you want to export.
If the report includes up to 2,000 records, the export runs immediately, as it does today.
If the report includes more than 2,000 records, the system will offer to run the export in the background instead of showing an error message.
Approve the export, and you can keep working in the system while the file is created.
When the process finishes, you receive a notification that the report is ready.
From the notification, you can download the file directly using the Download button.

Main uses

Exporting large reports without the 2,000-record limit.
Creating reports in the background without blocking the user work.
Downloading the report directly from the notification, with no need to go to the reports screen.
Preserving the existing access permissions, so each user can only download their own reports.

Who it’s for

Users who export large reports.
Managers and analysts.
Users who work with complex or data-heavy reports.

What it solves / examples

Removes the export limit on large reports, which previously blocked users.
Lets you keep working in the system while the export runs in the background.
Shortens the process of getting the file, with a direct download button inside the notification.
Improves the performance of large file downloads using a download mechanism suited to large files.
For example: a manager tries to export a report with 50,000 records. Instead of getting an error message, the system starts the export process in the background. After a few minutes a notification arrives, and from it the Excel file can be downloaded in one click, or the report can be opened in the system.

Choosing the Fields and Their Order on Kanban View Cards

A new field called “Show as task description” has been added to the Kanban view settings, letting you choose which fields appear on the Kanban cards and in what order. Every change to this setting updates immediately on the cards across the entire entity.

Step by step

Go to an entity that has a Kanban view defined.
Go to the view settings.
Locate the “Show as task description” field.
Choose which fields will be displayed on the cards and set their order.
Save, and the cards will display the fields according to the new setting.

Main uses

Showing due date and owner fields at the top of task management cards.
In a CRM view: customer name and sales pipeline stage before the rest of the fields.
Adapting the cards to the way the team wants to consume the information.

What it solves

Until now there was no control over which fields were displayed on the Kanban cards and in what order.
Now you can determine exactly what appears, and tailor each Kanban view to the needs of the entity.

Expanded Split By Options in Table and Kanban Views

The Split By feature, which lets you divide a view into segments by field values, has received a significant upgrade: support for additional field types, beyond regular selection fields. You can now split Table and Kanban views by a wider range of fields, including multi-select fields, yes/no fields, entity link fields, and the assigned user field, and present the data in a more flexible and convenient way to suit how you work. In a Kanban view, the division into segments happens inside each column.

Step by step

The user goes to the entity view settings, to the filter definitions, and confirms that the Allow Split By option is enabled.
The user can choose from the field list which fields to allow splitting by.
The user opens a Table View or a Kanban View.
The user clicks the filter and selects a field from the Split By option.
The system divides the records into separate segments according to the values of the selected field. If the user performed the split in a Kanban view, the division into segments happens inside each column.
The user can work with each segment separately, create new records, and edit existing records exactly as before.

Main uses

Dividing records by a wider range of field types.
Better data organization in Table and Kanban views.
Making work with large lists easier.
Adapting how the data is displayed to different business needs.

Who it’s for

Users who want a visual division of the data by a specific category.
Sales managers who want to work on each branch separately.
Organization managers who want to see details about the employees of each department separately.

What it solves / examples

A project manager divides the task list by assigned user, so each employee appears in a separate segment.
A sales manager divides opportunities by a multi-select field in order to see each customer group separately.
A support team divides service tickets by a yes/no field, so urgent and non-urgent requests are displayed in different segments.
An organization divides records by an entity link field, so all the records are displayed under the relevant customer or project.

Inline Edit for the Calendar Field in Table View

Click a calendar field cell in the table, and the field editing interface opens right inside the table: start date and time, end date and time, and an all-day event option. Update, save, and the cell refreshes immediately, without opening the record. In environments where dozens of dates are updated every day, that is a difference that adds up to real time saved.

Step by step

Go to a table view where the Inline Edit option is enabled.
Set the calendar field as available for inline editing in the view settings.
Click a calendar field cell in the table.
The field editing interface opens directly inside the table, including selecting a start date and time, an end date and time, and an all-day event option.
Update the event details and click Save.
The cell in the table updates immediately and displays the updated date and time range.

Main uses

Editing events directly from the table view, with no need to open the record.
Quickly updating the start and end date and time of events.
Support for all-day events as well (All Day).

Who it’s for

System users who work with table views in an entity that has a calendar view.
System administrators and implementers who configure inline editing.
Users who manage events, meetings, and tasks using a calendar field.

What it solves / examples

Lets you edit calendar fields directly from the table, like other fields supported by inline editing.
Saves the need to open the record every time you want to change the event date.
Preserves the structure of the field as a date range (start and end), including validity checks such as preventing an end time earlier than the start time.
For example: a user can push a meeting from 10:00 to 11:00 directly from the table, update the end time, and save, without opening the full record.

Calendar Event Display Improvements: Overlaps and All Day Events

The calendar view in Origami has received significant improvements: clear display of overlapping events, with no event hidden, and full support for All Day events that span several days. If your team manages its schedule in Origami, this is a meaningful version for them.

Step by step

Viewing overlapping events in week/day view

The user goes to the calendar.
The user switches to week or day view.
There are several events on the same day with overlapping hours.
The system displays all the events clearly, without hiding:
- The event name.
- The event hours.
- The event details.
The user hovers over an event with the mouse.
An information window (Popup) opens, displaying:
- The event name.
- Start and end time.
- The event description.
The user can quickly identify the event details even when several events run in parallel.

Creating an All Day event across several days

The user creates a new event in the calendar.
The user marks the event as All Day.
The user selects a date range of several days.
The user saves the event.
The system displays the event across all the selected days, including the last day.
The event is displayed as a daily event with no specific time.

Main uses

Managing a work calendar with several events in parallel.
Planning meetings when there are overlaps in the schedule.
Displaying long-term events correctly.
Managing vacations, conferences, tasks, and events that run over several days.
Improved readability and ease of use in the calendar.

Who it’s for

Team managers who coordinate meetings and tasks among several employees.
Employees who use the organizational calendar to manage daily meetings.
Users who manage busy calendars with several events on the same day.
Organizations that use the calendar to plan vacations, conferences, and multi-day events.

What it solves / examples

Prevents events from being hidden when there are several meetings at the same hours.
Quick identification of event details (name, hours, and description) even in a busy calendar.
Correct display of All Day events without an unnecessary time.
Display of long-term events across the entire selected date range.

SMS App Upgrade: Dashboard, Usability Improvements, and Bug Fixes

The Origami SMS app has received a comprehensive upgrade: a new dashboard that shows sending statistics in real time, usability improvements for faster sending, and bug fixes that improve the overall reliability of the SMS channel. SMS is one of the channels with the highest open rates, and that is exactly why sending needs to be reliable, measurable, and easy to operate. This upgrade does precisely that: higher reliability, improved operational speed, and performance data that helps improve the messages over time.

Step by step

Go to the SMS app in the system settings.
Create or edit an SMS campaign using the updated interface.
While writing the message, the number of characters, the number of SMS segments, and the number of recipients are displayed in real time. You can also see the current credit status in the system before creating the campaign.
After sending, you can track the campaign status through the new dashboard, which includes information on messages that were sent, failed, or are waiting to be sent.
If needed, you can identify issues and track the sending statuses simply and clearly.

Main uses

Tracking SMS message sending statuses in real time.
Identifying messages that failed or are waiting to be sent.
Displaying the number of recipients, the number of characters in the message, and the current credit status for full transparency.
Improved reliability of the sending process with the Meser10 provider.
Viewing campaign data through a dedicated dashboard.
Available credit is displayed at all times, for maximum transparency and for decision-making before saving a campaign.

Who it’s for

Users who send SMS campaigns through Meser10.
System administrators.
Marketing, service, and sales teams that use the messaging module.

What it solves / examples

Improves the stability and reliability of sending with the Meser10 provider, by fixing issues in the sending process and in the status updates.
Lets the user understand in advance how much credit is available to them, the message, and the number of recipients before sending.
Provides a clear picture of SMS campaign activity through a central dashboard.
For example: a system administrator can quickly identify that a group of messages failed to send and act accordingly, or track how many messages were sent and which messages are still waiting to be processed.

Connecting Multiple Entities to a Single PBX Account

From version 6.3.4 you can connect several entities to a single PBX account. When an incoming call arrives, the system searches for the phone number across all the entities that were defined, such as customers, leads, suppliers, or any other entity, in the priority order that was set. If a match is found, you open the record straight from the notification. If no match is found, you create a new record in the first entity that was defined, with the phone number already filled in automatically.

Step by step

The user goes to the PBX app and defines or edits a phone line.
The user adds one or more entities in the Entity Mapping area and defines the phone and name fields for each entity.
The user orders the entities by the priority they want.
When an incoming call arrives, the system searches for the phone number across all the entities that were defined.
If a match is found, the user can open the record directly from the notification.
If no match is found, the user can create a new record in the first entity that was defined, with the phone number filled in automatically.

Main uses

Searching for callers across several entities using a single PBX line.
Automatic identification of customers, leads, suppliers, or any other entity.
Setting a search priority order between entities.
Quickly creating new records when the caller does not exist in the system.

Who it’s for

System administrators and implementers who configure the PBX connections.
Service reps who use the incoming call panel to identify callers.
Sales reps who receive incoming calls from customers and leads.
Service centers and Call Centers that work with several entities in the system.

What it solves / examples

A service rep receives a call from a number that exists in the Customers entity, even though the first entity is Leads. The system keeps searching and finds the record in Customers, so the rep can open it immediately.
An organization that manages customers, leads, and suppliers in different entities can work with a single phone line, with no need to choose in advance which entity to search in.
When the phone number does not exist in any of the defined entities, a new record can be created quickly in the main entity, with the phone number already filled in.

In Summary

Version 6.3.4 is one of the broadest versions released for Origami: a major WhatsApp upgrade with support for full templates and smart field mapping, a financial leap forward with a dashboard, a widget, a revenue report and ITA support, background export that does not block your work, view improvements in Kanban and the calendar, and SMS and PBX upgrades. Every one of these changes came to solve a real pain heard 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.