Changelogs

• From V7, a Zia insights module will be created automatically whenever you enable any Zia features for a specific module. You can fetch the list of these Zia insights modules using the Modules API.
  • Zia features : Field Prediction, Churn Prediction, NBX, Recommendation, Call Transcription, Best Time for Call, Best Time for Mail, Owner Recommendation, Vision, Best Time for Notes, and Best Mode to Contact.
  

• When you enable Zia features for a module, a corresponding Zia Insights module will be created, from V7. 

  • Zia features : Field Prediction, Churn Prediction, NBX, Recommendation, Call Transcription, Best Time for Call, Best Time for Mail, Owner Recommendation, Vision, Best Time for Notes, and Best Mode to Contact. 

    To see the fields available within the created Zia Insights module, use the GET - Fields Metadata API 

    Note : Use the corresponding Zia insight module's API name in the "module" parameter. Example : /settings/fields?module=Leads_Insights__s

• A new "layout_associations" JSON array key is introduced in the response of the GET - Fields Metadata API from V7, representing the layouts with which the fields are associated in a module.
  

• While fetching a particular layout using its unique ID in a module, the "subform_properties" JSON object in the response of the GET - Layouts API represents whether any field is pinned in the subform. 
  Note: This feature is currently in "Early Access." Contact the support team at support@zohocrm.com to request access.
   
  
• The "mode" key will be listed in the GET - Layouts API, representing the section's mode in a layout. 
  • Possible values 
    • All modules except "Events" :default_create, quick_create, and business_card.
    • Events module : create, view, and quick_view. 
    • Subform: create and view. 
    • Wizard : create
  

• Introduced in V7, the "status" key for each related list represents its visibility in the module. 

  Possible Values : visible, user_hidden, and scheduled_for_deletion.

  

• From V7,  You can retrieve a maximum of 2000 records in a single API call, using the Territories API.  The maximum value of "per_page" key has been increased from 200 to 2000.

• From V7 onwards, the "include" parameter is introduced to retrieve territory specific criteria rules. Possible Values: lead_rule_criteria, account_rule_criteria, and deal_rule_criteria in a comma separated value.  

  Note : In V7 GET Territories API, the lead_rule_criteria, account_rule_criteria, and deal_rule_criteria will not be displayed unless you specify them to the include parameter. 

• The "api_name" key is introduced from V7 to represent the API name of a territory.

  

• From v7, the "used_count" JSON object key is introduced within the "component" JSON object to denote the feature's usage count for your edition.
  
• From V7, all custom field datatypes are grouped together under a single "Custom Field" component. Each specific datatype (like text, integer and so on) is represented as a separate component within this main "Custom Field" component in the GET - Features API's response.
   
  
• From V7 onwards, the "Personal Health Field" will be included in the response of the GET - Features API.
  

• The value of the "code" key in the response of the Mass Convert Lead API has been changed from "SUCCESS" to "SCHEDULED".

• In the GET - Files API, if you do not pass the "id" parameter, the system will return an "HTTP 400 - REQUIRED_PARAM_MISSING" error response from V7. If you specify an invalid ID in the "id" parameter, the response will be "HTTP 204 - NO_CONTENT".

• In a blueprint record, the "current_picklist" JSON object is introduced in the GET - Blueprint API response from V7, specifies the details of the current picklist option. 

  The current_picklist includes :

  • colour_code (string): Represents the hex color code of the current picklist option.
  • id (string): Represents the unique ID of the current picklist option.
  • value (string): Represent the value of the picklist option.
  

• In the User Groups API, you can do criteria-based searches for user groups , using the "filters" (singular and multiple filters) parameter introduced from V7.
• Using the Associated Groups of a User API, from V7, the "include" parameter is introduced to know the sources available in a group a user is associated with. Supported value is sources.

• If the Create Bulk Read API request has more than 200,000 records to export in a module, the "next_page_token" key will be present in the Get the Status of the Bulk Read Job's response from V7.
• Use the next_page_token's value received in the response of the Get the Status of the Bulk Read Job API to fetch the next set of records by passing the value to the "page_token" key (introduced from V7 onwards) using a separate Create Bulk Read job API. Repeat this process until all records are retrieved.

From V7, we will introduce additional support in the COQL API, which will be released in the upcoming weeks.

• Increasing field limitations from 50 to 500.
• Increasing the join support.
• CVID support.
• Adding ORDER BY, GROUP BY, and aggregation field limitations.
• Territory support in the SELECT column.
• Providing display names for all lookups.