Zoho: Update specific record locking configuration
Zoho recordLockingConfigurations.updateRecordLockingConfigurationPassingIdInUrl: arguments, response, policy and SDK examples.
← Record locking configurations operations · Get started
Operation zoho.updaterecordlockingconfigurationpassingidinurl
Provider route: PUT /crm/v8/settings/record_locking_configurations/{id}. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/zoho with npm, or alter-sdk-zoho with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { ZohoIntegration } from "@alter-ai/zoho";
async function execute(input: Parameters<ZohoIntegration["recordLockingConfigurations"]["updateRecordLockingConfigurationPassingIdInUrl"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new ZohoIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.recordLockingConfigurations.updateRecordLockingConfigurationPassingIdInUrl(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_zoho import ZohoIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = ZohoIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.record_locking_configurations.update_record_locking_configuration_passing_id_in_url(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
path | object | Required within parent | Additional keys: not allowed |
path.id | string | Required within parent | Record Locking Configuration ID Format: int64 |
query | object | Required within parent | Additional keys: not allowed |
query.module | string | Required within parent | Maximum length: 256 |
body | object | Required within parent | Request body for updating a record locking configuration. Additional keys: not allowed |
body.record_locking_configurations | array | Required within parent | Array containing the updated configuration. Maximum items: 1 |
body.record_locking_configurations[] | object | Each item | The configuration object to update. Additional keys: not allowed |
body.record_locking_configurations[].excluded_fields | array | Optional | Fields that are exempt from locking. Maximum items: 15 |
body.record_locking_configurations[].excluded_fields[] | object | Each item | Field descriptor for a field to be excluded from locking. Additional keys: not allowed |
body.record_locking_configurations[].excluded_fields[].id | string | Required within parent | Field ID. Use the [Get Fields Metadata API](fields.yaml#$.paths./settings/fields.get) to retrieve field IDs. Format: int64 |
body.record_locking_configurations[].feature_type | string | Optional | Feature type identifier (must be `record_locking`). Default: record_locking One of: record_locking |
body.record_locking_configurations[].id | string | Required within parent | Unique identifier of the configuration to update. This field is required. Maximum length: 32 |
body.record_locking_configurations[].lock_excluded_profiles | array | Optional | Profiles that are excluded from locking. Required when `locked_for` is `all_profiles_except_excluded_profiles`. Maximum items: 15 |
body.record_locking_configurations[].lock_excluded_profiles[] | object | Each item | Profile descriptor for a profile to be excluded from locking. Additional keys: not allowed |
body.record_locking_configurations[].lock_excluded_profiles[].id | string | Required within parent | Profile ID. Use the [Get Profiles API](profiles.yaml#$.paths./settings/profiles.get) to retrieve profile IDs. Format: int64 Maximum length: 19 Minimum length: 1 Pattern: ^[0-9]{1,19}$ |
body.record_locking_configurations[].lock_for_portal_users | boolean | Optional | If `true`, portal users are also subject to the locking restrictions. Default: true |
body.record_locking_configurations[].lock_type | string | Optional | Defines the locking mode. `automatic` locks records based on rules, `manual` requires explicit action, `both` supports both. One of: automatic, manual, both |
body.record_locking_configurations[].locked_for | string | Optional | Indicates which profiles the lock applies to. One of: all_profiles, all_profiles_except_excluded_profiles |
body.record_locking_configurations[].locking_rules | array | Optional | A set of rules that define when records should be automatically locked. Maximum items: 5 |
body.record_locking_configurations[].locking_rules[] | Model | Each item | Expand Update record locking configuration — request body — body record locking configurations item locking rules item |
body.record_locking_configurations[].restricted_actions | array | Optional | List of actions that are restricted on locked records. Maximum items: 10 |
body.record_locking_configurations[].restricted_actions[] | string | Each item | A restricted action. Default: update One of: change_owner, update, delete, tags |
body.record_locking_configurations[].restricted_communications | array | Optional | List of communication actions that are restricted for locked records. Maximum items: 10 |
body.record_locking_configurations[].restricted_communications[] | string | Each item | A restricted communication action. One of: send_mail |
Referenced models: Update record locking configuration — request body — body record locking configurations item locking rules item
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Response object for a successful update. Additional keys: not allowed |
record_locking_configurations | array | Required within parent | Array containing the update response. Maximum items: 1 |
record_locking_configurations[] | object | Each item | Details of the updated configuration. Additional keys: not allowed |
record_locking_configurations[].code | string | Required within parent | Success code for the operation. Known values: SUCCESS Maximum length: 256 |
record_locking_configurations[].details | object | Required within parent | Additional details about the updated configuration. Additional keys: not allowed |
record_locking_configurations[].details.id | string | Required within parent | ID of the updated configuration. Maximum length: 256 |
record_locking_configurations[].message | string | Required within parent | Informational message about the update. Maximum length: 256 |
record_locking_configurations[].status | string | Required within parent | Indicates successful update. Known values: success Maximum length: 256 |
Schemas
Section titled “Schemas”Update record locking configuration — request body — body record locking configurations item locking rules item
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | A locking rule object. Additional keys: not allowed |
criteria | object | Required within parent | Criteria that records must satisfy for the rule to apply. Additional keys: allowed |
id | string | Optional | Unique identifier of the locking rule. Required when updating an existing rule. Maximum length: 32 |
lock_existing_records | boolean | Optional | If `true`, existing records that match the criteria will also be locked when the rule is saved. Default: false |
name | string | Required within parent | Unique name for the locking rule. Maximum length: 256 |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: zoho.updaterecordlockingconfigurationpassingidinurl. Catalog operation: updateRecordLockingConfigurationPassingIdInURL. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.