Client Script | Update - Client Script Support For Portals

Dear All!

We are excited to announce the highly anticipated feature: Client Script support for Portals. We understand that many of you have been eagerly awaiting this enhancement, and we are pleased to inform you that this support is now live for all DCs.

A Portal enables you to share selective data in the Vertical Solution with your customers. With this update, Client Script functionality is extended to Zoho CRM Portals, allowing businesses to enhance portal interactions without creating new scripts.

Here's what you need to know:

Effortless Integration

Your existing Client Script will automatically function within portals—no need for tedious rewrites or duplication.

Tailored Flexibility

Customize Client Script to operate portal-wide, target specific user types, or even individual users, ensuring they align perfectly with your business needs.
You can utilize $Crm.user to access all necessary details about user.

Response of $Crm.user for Regular User

Response of $Crm.user for Portal User

{

"id": "4013519000000559001",

"zuid": "74359639",

"full_name": "Daniel",

"first_name": "Daniel",

"last_name": null,

"email": "daniel.si+dx@zohotest.com",

"date_format": "MMM d, yyyy",

"type": "Regular User",

"profile": {

"id": "4013519000000015972",

"name": "Administrator"

"role": {

"id": "4013519000000015966",

"name": "CEO"

}

{

"id": "4013519000000572496",

"zuid": "1029309420",

"full_name": "Marrier (Sample) Kris",

"first_name": "Kris",

"last_name": "Marrier (Sample)",

"email": "Marrier.sg@zohotest.com",

"date_format": "MMM d, yyyy",

"type": "Client Portal User",

"profile": {

"id": "4013519000000568002",

"name": "ClientPortal"

"role": {

"id": "4013519000000559999",

"name": "Portal User"

}

Early Access Opportunity

Eager to get started? You can adjust your scripts now and enable this feature in your portal ahead of the auto-enablement.

Implementation Timeline

This feature will be enabled to all portal user types by November 1.

Action Steps

To ensure a smooth transition, businesses should use this period to:

Review existing Client Script.
Modify scripts to accommodate portal-specific scenarios.
Test and validate adjustments before the auto-enablement.

Note :

For newly created user types, Client Script will be enabled and will work by default.

Your proactive engagement will ensure you reap the full benefits of this exciting enhancement!

You can see this information on the Portals page.

Now, let's see some scenarios where users may require scripts to work differently for portal users and CRM users.

Scenario 1 : Controlling Delete Button states and Field Accessibility Based on Order Status by Portal user

The Delete button is enabled only when the order status is "Created" and remains disabled for all other statuses. After a CRM user approves the order, all fields become read-only for portal users.

Using the Client Script constant $Crm.user.type , you can easily find the type of user logged in (either "Regular" or "Client Portal") and then add your script. If your script is specific to Portal users, simply add this line if ($Crm.user.type == 'Client Portal User')

Click here to view the source code

Scenario 2: Managing Order Status Based on Portal User Type

Consider there are two user types in the portal:

Vendor Portal: Vendors can update Approved orders to "Delivered" in the Edit Page but cannot change it to any other state.

Client Portal: Clients cannot make any changes to the order status once the order is created.

Click here to view the source code.

Note:

$Crm.org and $Crm.environment will return null for portals.

Unsupported Actions in Portals:

ZDK.Apps.CRM.Functions.execute()
ZDK.Apps.CRM.Connections.invoke()
ZDK.Page.addTag()
ZDK.Page.removeTag()
ZDK.Page.getTags()
ZDK.Page.getList().freezeColumns()
ZDK.Page.getList().selectRecords()
ZDK.Page.getList().clearSelection()
ZDK.Client.openMailer( )

We hope you find this incredibly beneficial!

Happy Client Scripting :)