Kaizen# 209 - Answering Your Questions | All About Client Script
Hello everyone!
Welcome back to another exciting Kaizen post! Thanks for all your feedback and questions. In this post, let's see the answers to your questions related to Client Script.
Q1: Repeating the same validation code across Create, Edit, List, and Detail views reduces maintainability
Currently, this requirement is under analysis. For now, we suggest you use Static Resources to reduce duplication and improve maintainability.
Q2: A unified screen for writing client-side validation logic would improve efficiency, especially if it supports both validation and CRM data fetching
We are planning to provide a Client Script IDE with a tree structure listing all scripts. This will allow you to access a page’s complete script in a single view without exiting each time. This is part of future enhancements and as of now there is no ETA for this.
Q3: Client Scripts currently do not support access to third-party APIs
API calls can be made using HTTP requests or Connections.
Check out Kaizen#135: Third Party Integration using Client Script to see the implementation and a practical use case.
Also, our new ZRC support, now in early access, provides direct API calls for enhanced control and flexibility.
Q4: Need for deeper UI control in Client Scripts (like modifying metadata CSS and HTML)
Direct modification of CRM page CSS/HTML via Client Script is not possible.
Q5: Canvas actions cannot trigger Blueprint transitions, limiting process automation
Blueprint transitions can now be initiated from Canvas pages. Click here for documentation.
Q6: Lack of functions to retrieve a field’s data type (text, boolean, datetime) limits dynamic handling
This feature is planned for future enhancements.
While the Save action is not available on Detail pages, the onBeforeUpdate() field event can be used to enforce validations post-edit.
Q8: onChange does not work on multi-picklists and subforms
Q9: Currently, there is no way to control or restrict access to the "Record detail page views" dropdown selector in Canvas detail pages based on user profiles or roles.
We are working on addressing this limitation and will keep you updated once the enhancement is available.
Feature | How It Works | Best For |
Validation Rules | Define conditions in the setup UI without coding. These checks run when you try to save a record. If conditions fail, the save is blocked and an error message is shown. Click here for more details. | Quick, straightforward validations like “Email must contain @domain.com” or “Amount cannot be negative,” especially for admins with no coding knowledge. |
Layout rules | Define layout rules that adjust the form UI in real-time based on field values. This includes showing/hiding sections, enabling/disabling fields, or making them mandatory. Click here for more details. | Use when the form sections needs to adapt dynamically to the context for pages other than Canvas (e.g., “If Customer Type = Business → Show GST details section”). |
Functions (Deluge) | In Functions, you can write a Deluge script that executes server-side. Functions are usually triggered by workflows, buttons, schedules or record actions and can update fields, create related records, call external APIs and so on. Click here for more details. | Ideal for automating complex business logic and integrating with Zoho services or third-party applications. |
Client Scripts (ZDK + JavaScript) | Use Zoho Developer Kit (ZDK) APIs with JavaScript to run logic directly in the browser. Triggers include On Load, On Field Change, On Save. You can block record save, fetch CRM/external data instantly, show dynamic messages, or modify field behavior and much more. Click here for more details. | Perfect for advanced, real-time validations and dynamic UI. |
In this Kaizen post, we have answered all your questions about Client Script, shared solutions along with relevant help doc links, and highlighted upcoming features and enhancements. We hope this answers your queries and provides clarity on Client Script usage.
