Sprint 1 January Release Highlights
What’s New
Control Email Visibility in Comments
A new checkbox, "Make Comment Private", has been added to the email action configuration. This allows admins to decide whether an email should be added as a private or public comment. If this checkbox is enabled, the email will be added as a private comment, making it invisible to client users in the comments section. This checkbox appears only when the "Add Email as Comment" option is selected.
.png)
Admin Portal: Email Configuration Page
Confirmation Prompts to Custom Buttons
This feature allows you to add confirmation prompts when users click on custom buttons. Previously, clicking a custom button would immediately execute the action. Now, you can configure a confirmation message, such as "Are you sure you want to proceed with this action?" in the button configuration page.
.png)
Admin Portal: Button Configuration Page
If a message is added, a confirmation pop-up will appear before the action is performed. If the field is left blank, the button will continue to execute the action without any prompt.
.png)
Agent Portal: Display View
Notable Bug Fixes
When scrolling down a page in the agent portal, the page title now remains fixed at the top, ensuring it is always visible.
Fixed an issue where the AND and OR operators were not displayed below the filter options when multiple filters were added to charts.
Fixed an issue where an appropriate error messages were not displayed during image or file uploads during multi-edit operations in list and embedded lists. The supported image file types are: .apng, .avif, .bmp, .gif, .jpeg, .jpg, .png, .svg, .tif, .tiff, .ico, and .webp.
Fixed an issue where filters were not automatically removed from button settings after the corresponding filter was deleted.
Fixed an issue where additional field searching was not functioning in embedded lists.
Fixed an issue where state colors were not applied when states were displayed in embedded lists.
Fixed an issue where updates to a child object's field made through field mapping were not being recorded in the child object's history.