We are pleased to announce the release of Origami 5.7.2, launched May 15th, 2023.
Here’s what you can now do:
- Repeatable Groups in Table View!
This exciting enhancement revolutionizes how you organize and visualize data within your tables.
With this update, you can now utilize repeatable groups in table view to efficiently manage and track various “sub-instances”. Here’s how it can benefit you:
Imagine you have a table dedicated to tracking leads. Each row represents a different lead, and you want to keep a comprehensive record of all communications made with each lead. With repeatable groups in table view, you can easily achieve this.
By adding a repeatable group to the lead table view, you can now include fields for calls, emails, meetings, or any other relevant communication types. Each lead’s row will display a plus icon at the beginning, allowing you to expand and view the associated repeatable groups for that lead right within the table view.
With a single click, you can access a consolidated view of all communications related to a specific lead, without the need to switch between different screens or views. You can quickly review the history of calls, emails, and other interactions, ensuring nothing falls through the cracks.
This powerful feature streamlines your workflow, saves time, and ensures you have a comprehensive record of all communications with your leads. It’s an invaluable tool for effective lead management and building strong customer relationships.
To set this feature, browse to the view settings > table view > choose the fields you wish to see from your repeatable groups in the table view.
Language Customization for Webforms.
This empowers you to create webforms in a language that differs from the system language, ensuring seamless communication with your audience.
Suppose your Origami system is set to Hebrew, but you need to create a webform in English (or vice versa). With this update, it’s now effortless to achieve your desired language for webforms. Here’s how it works:
When generating the URL for your webform, simply add a language parameter at the end of the URL. For example, if your webform’s URL is “https://live-public.origamicloud.ms/web_forms/unique_url,” you can customize the language by appending “?lang=english” or “?lang=hebrew” to the URL.
For instance, if you want to display the webform in Hebrew, the URL would be: “https://live-public.origamicloud.ms/web_forms/unique_url?lang=hebrew”. Likewise, to present the webform in English, the URL would be: “https://live-public.origamicloud.ms/web_forms/unique_url?lang=english”.
This flexibility allows you to cater to different audiences, seamlessly aligning your webform’s language with their preferences or requirements. It’s a simple yet powerful way to enhance communication and user experience.
Dynamic Tags in the HTML Field
Allows you to seamlessly incorporate data from your entities into various aspects of your workflows, automations, webforms, contracts, documents, and reports.
Here’s how it works:
When creating an HTML field, you can now utilize dynamic tags to insert fields from the entity directly into the field. These dynamic tags act as placeholders, and when the field is used in workflows, automations, webforms, contracts, documents, or reports, Origami will automatically replace the tags with the actual data value of the corresponding field.
Let’s explore a practical use case:
Suppose you’re creating an email text field where the end user can personalize and edit the content before sending it to clients. With the power of dynamic tags, you can include relevant fields such as client name, order details, or any other data from the entity. For example, your email template could include a dynamic tag like #client_name#, which will be replaced with the actual client’s name when the email is sent.
This feature streamlines your communication processes, eliminates manual data entry, and ensures accurate and personalized content every time. Whether you’re generating automated emails, populating contracts and documents, or creating customized reports, dynamic tags in the HTML field offer endless possibilities for efficient data integration.
*This feature is available for the Master and Enterprise plans.
ChatGPT Integration: Engage and Generate Responses with Ease
This powerful feature empowers you to seamlessly incorporate ChatGPT’s capabilities into your workflows, enabling dynamic and interactive conversations within your application.
Here’s how it works:
Within your workflow, you can now add an action that interacts with ChatGPT to generate responses. By including an area text field, you can write the initial prompt or message to initiate the conversation with ChatGPT. You can also leverage fields from the instance to personalize and contextualize the conversation.
Let’s explore a practical use case:
Imagine you’re creating a workflow for meeting summaries. After a meeting, you can automate the process of generating action items. Within the workflow, you’ll include an action that utilizes ChatGPT. The area text field allows you to compose the prompt, incorporating relevant details from the meeting summary and leveraging fields from the instance. ChatGPT will then generate a response that outlines action items based on the provided information.
This feature streamlines your workflow automation, saving you time and effort. You can use the generated ChatGPT response to forward as an email, convert to tasks, or perform any other desired action within your application.
To set these workflows, the admin will need to create an API key, this needs to be a paid API account. To generate a key for your account, visit https://platform.openai.com/account/api-keys and insert that key in the Origami system settings.
Bugs that were fixed in this release:
- Instance relation field and filter – results were not shown in a consistent way.
- Excel imports with a large amount of repeating group rows would create an error on import due to errors in the files that weren’t shown.
- Invitations from the calendar in case the admin allowed for use of the personal calendar but the user didn’t set the integration, were not sending.