Update a rule for a territory

patch

/crmRestApi/resources/11.13.18.05/territories/{TerritoryVersionId}/child/TerritoryRule/{TerrRuleId}

Request

Path Parameters
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Coverage Number
    The coverage number for the territory.
  • Title: Customer Coverage Code
    Maximum Length: 30
    Default Value: INCLUSION
    The code for identifying whether the coverage adds to or removes from the territory's jurisdiction. The accepted values are: EXCLUSION (for rule type EXCLUSION and PARTNER_EXCLUSION) and INCLUSION (for all other rule types, such as REGULAR, INCLUSION, PARTNER_REGULAR, PARTNER_INCLUSION, and INHERITANCE_OVERRIDE).
  • Title: Coverage
    Maximum Length: 30
    Default Value: REGULAR
    The code for the territory coverage type. If the territory coverage model is sales account centric, the accepted values are: -REGULAR (for coverage based on sales account dimensionality or named accounts) -INCLUSION (for manually included account coverage) -EXCLUSION (for manually excluded account coverage) If the territory coverage model is partner centric, the accepted values are: -PARTNER_REGULAR (for coverage based on partner dimensionality) -PARTNER_INCLUSION (for manually included partner coverage) -PARTNER_EXCLUSION (for manually excluded partner coverage) In case of inheritance, if the coverage is for a recipient territory, then the accepted value is INHERITANCE_OVERRIDE which indicates that the coverage overrides some of the inherited dimensionality.
  • Rule Boundaries
    Title: Rule Boundaries
    The rule boundaries resource is used to view the rule boundaries associated with a sales territory. The equivalent functional term for rule boundary is coverage dimension. The rule boundaries object contains records for each of the dimensions defined for a given territory coverage.
  • Title: Territory Number
    The unique identifier of the territory version.
Nested Schema : Rule Boundaries
Type: array
Title: Rule Boundaries
The rule boundaries resource is used to view the rule boundaries associated with a sales territory. The equivalent functional term for rule boundary is coverage dimension. The rule boundaries object contains records for each of the dimensions defined for a given territory coverage.
Show Source
Nested Schema : territories-TerritoryRule-TerritoryRuleBoundary1-item-patch-request
Type: object
Show Source
  • Rule Boundary Values
    Title: Rule Boundary Values
    The rule boundary values resource is used to view the rule boundary values associated with a sales territory. The equivalent functional term for rule boundary value is coverage dimension member. The rule boundary values object contains records for the dimension members for each coverage dimension.
  • Title: Territory Number
    The identifier of the territory rule.
Nested Schema : Rule Boundary Values
Type: array
Title: Rule Boundary Values
The rule boundary values resource is used to view the rule boundary values associated with a sales territory. The equivalent functional term for rule boundary value is coverage dimension member. The rule boundary values object contains records for the dimension members for each coverage dimension.
Show Source
Nested Schema : territories-TerritoryRule-TerritoryRuleBoundary1-TerritoryRuleBndryValue1-item-patch-request
Type: object
Show Source
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : territories-TerritoryRule-item-response
Type: object
Show Source
  • Title: Created By
    Read Only: true
    Maximum Length: 255
    The user who created the territory rule.
  • Title: Creation Date
    Read Only: true
    The date the territory rule was created.
  • Title: Last Updated Date
    Read Only: true
    The date the territory rule was last updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 255
    The user who last updated the territory rule.
  • Title: Last Update Login
    Read Only: true
    Maximum Length: 255
    The login of the user who last updated the territory rule.
  • Links
  • Title: Coverage Number
    The coverage number for the territory.
  • Title: Customer Coverage Code
    Maximum Length: 30
    Default Value: INCLUSION
    The code for identifying whether the coverage adds to or removes from the territory's jurisdiction. The accepted values are: EXCLUSION (for rule type EXCLUSION and PARTNER_EXCLUSION) and INCLUSION (for all other rule types, such as REGULAR, INCLUSION, PARTNER_REGULAR, PARTNER_INCLUSION, and INHERITANCE_OVERRIDE).
  • Title: Coverage
    Maximum Length: 30
    Default Value: REGULAR
    The code for the territory coverage type. If the territory coverage model is sales account centric, the accepted values are: -REGULAR (for coverage based on sales account dimensionality or named accounts) -INCLUSION (for manually included account coverage) -EXCLUSION (for manually excluded account coverage) If the territory coverage model is partner centric, the accepted values are: -PARTNER_REGULAR (for coverage based on partner dimensionality) -PARTNER_INCLUSION (for manually included partner coverage) -PARTNER_EXCLUSION (for manually excluded partner coverage) In case of inheritance, if the coverage is for a recipient territory, then the accepted value is INHERITANCE_OVERRIDE which indicates that the coverage overrides some of the inherited dimensionality.
  • Rule Boundaries
    Title: Rule Boundaries
    The rule boundaries resource is used to view the rule boundaries associated with a sales territory. The equivalent functional term for rule boundary is coverage dimension. The rule boundaries object contains records for each of the dimensions defined for a given territory coverage.
  • Title: Territory Number
    The unique identifier of the territory version.
  • Title: Coverage ID
    The unique identifier of the territory rule.
Nested Schema : Rule Boundaries
Type: array
Title: Rule Boundaries
The rule boundaries resource is used to view the rule boundaries associated with a sales territory. The equivalent functional term for rule boundary is coverage dimension. The rule boundaries object contains records for each of the dimensions defined for a given territory coverage.
Show Source
Nested Schema : territories-TerritoryRule-TerritoryRuleBoundary1-item-response
Type: object
Show Source
Nested Schema : Rule Boundary Values
Type: array
Title: Rule Boundary Values
The rule boundary values resource is used to view the rule boundary values associated with a sales territory. The equivalent functional term for rule boundary value is coverage dimension member. The rule boundary values object contains records for the dimension members for each coverage dimension.
Show Source
Nested Schema : territories-TerritoryRule-TerritoryRuleBoundary1-TerritoryRuleBndryValue1-item-response
Type: object
Show Source
Back to Top

Examples

The following example shows how to create a rule boundary for a territory by submitting a POST request on the REST resource using cURL.

cURL Command

curl -u <username:password> \ -X POST -d @example_request_payload.json https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/territories/300100091635502/child/TerritoryRule/300100091635545/child/TerritoryRuleBoundary1

Example of Request Body

The following example shows the contents of the request body in JSON format.

{
  "TerrDimensionCode":"Indst",
  "TerritoryRuleBndryValue1":[
     {
        "TerrDimIntgId":"ONE VOICE~1100",
        "TerrDimensionCode":"Indst"
      }]
}

Example of Response Body

The following example shows the contents of the response body in JSON format.

{
"TerrRuleBoundaryId": 300100091635549,
"TerrRuleId": 300100091635545,
"Dimension": "Industry",
"TerrDimensionCode": "Indst",
"TerritoryRuleBndryValue1":[
{"TerrRuleBndryValueId": 300100091635550, "TerrRuleBoundaryId": 300100091635549, "DimensionMember": "Automotive", "DimensionMemberHigh": null,…}
],
"links":[
{"rel": "self", "href": "https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/territories/300100091635502/child/TerritoryRule/300100091635545/child/TerritoryRuleBoundary1/300100091635549",...},
{"rel": "canonical", "href": "https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/territories/300100091635502/child/TerritoryRule/300100091635545/child/TerritoryRuleBoundary1/300100091635549",...},
{"rel": "parent", "href": "https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/territories/300100091635502/child/TerritoryRule/300100091635545",...}
]
}
Back to Top