API

Procurement APIs

PUT procurement/contracts/{purchaseContractId}/auto-approval-rules/{autoApprovalRuleId}

Update rule for automatic approval of purchase contracts

HTTP method PUT
URI https://api.rambase.net/procurement/contracts/{purchaseContractId}/auto-approval-rules/{autoApprovalRuleId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {purchaseContractId} Purchase contract identifier
Integer, minimum 100000
- URI parameter {autoApprovalRuleId} Item reference number
Integer, minimum 1
Successful HTTP status code 200
API resource identifier 6785, version 2

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
<AutoApprovalRule
AutoApprovalRule

This field is optional.

>
2
     <Product
Product

Product reference

This field is optional.

>
3
          <ProductId
ProductId

Product identifier

Minimum value: 10000

This field is optional.

>{Integer}</ProductId>
4
     </Product>
5
     <Validity
Validity

This field is optional.

>
6
          <EffectiveDate
EffectiveDate

The date from which the approval rule is active

This field is optional.

>{Date}</EffectiveDate>
7
          <ExpirationDate
ExpirationDate

The date to which the approval rule is active

This field is optional.

>{Date}</ExpirationDate>
8
     </Validity>
9
</AutoApprovalRule>
1
{
2
     "autoApprovalRule
AutoApprovalRule

This field is optional.

": {
3
          "product
Product

Product reference

This field is optional.

": {
4
               "productId
ProductId

Product identifier

Minimum value: 10000

This field is optional.

": "{Integer}"
5
          },
6
          "validity
Validity

This field is optional.

": {
7
               "effectiveDate
EffectiveDate

The date from which the approval rule is active

This field is optional.

": "{Date}",
8
               "expirationDate
ExpirationDate

The date to which the approval rule is active

This field is optional.

": "{Date}"
9
          }
10
     }
11
}

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
1

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 100089 HTTP 404 Product {0} not found
Error 109640 HTTP 400 Expiration date is mandatory
Error 109641 HTTP 400 Effective date cannot be greater that expiration date
Error 109664 HTTP 400 Only one auto approval rule with the same parameters can be in effect at a time.