API Updates for November 2017

API Updates

The next Kintone update is 10th November 2017. The release also includes these API updates.

Kintone REST API

New features

  • The REST API is limited in the number of simultaneous calls you can make for a given domain. To make tracking that easier, we are adding two new fields to the call response header.

    • X-ConcurrencyLimit-Limit: Contains the maximum number of calls you can make simultaneously
    • X-ConcurrencyLimit-Running: Contains the current number of simultaneous calls
  • Developers who have issues running into the concurrency limit may want to add logic that builds in a delay if they approach around 80% of that limit.

Bug fixes

  • Get Record , Get Records , Update Record , Update Records .
    • Condition: The record object in the JSON of the request body includes a field code value of null.
    • Bug: “Illegal request” is returned.
    • Fix: An error message will be returned, containing a message that is easier to understand.
  • Bulk Request
    • Condition: The request parameter includes null.
    • Bug: “Illegal request” is returned.
    • Fix: An error message will be returned, containing a message that is easier to understand.
  • Update Views
    • Condition: Multiple values are stated with the in operator for views.{viewname}.filterCond
      (The Get Views API may return the filter condition of the views in this format)
    • Bug: An error occurs.
    • Fix: An error will not occur, and the call will succeed.
  • Update Status , Update Multiple Statuses

Spec changes

  • Get Records
    • Changes: An error with the status code 500 will return when the Get Records is called using the like operator and Kintone’s full-text search server is inaccessible due to server failures.
    • Reasons for changes: Currently no error is returned.
  • APIs: Upload File , calls that retrieve the fileKey
    • Changes: An error with the status code 500 will return when Upload File (or other calls that specify the fileKey) is used and Kintone’s file server is inaccessible due to server failures.
    • Reasons for changes: Currently, each call acts differently in this state.

Kintone JavaScript API

New features

  • The name value can now be specified when using the JavaScript API on mobile devices and adding users to the User/Department/Group selection field. The name value can be specified with kintone.mobile.app.record.set(), or by editing and returning the event object in the event handler for each event.
    If you specify the name value, that string will be shown when selecting a user. Note that the code value is still displayed on the record itself. If a name value is not specified, the code value will display during selection instead.
    Note: The User/Department/Group field must not hold any preset values.
    The following GIF shows an example where

    1
    2
    3
    4
    
    {
      "code": "Andrea",
      "name": "Andrea the Great!"
    }
    

    is specified for the value of the User Selection field. “Andrea the Great!” is shown during selection and “Andrea” is shown on the record.
    new mobile feature Screenshot

Others

Spec changes

  • To improve Kintone accessibility, we are updating the DOM structure for the Kintone page header. This improves keyboard navigation.
    header Screenshot
    System-wide JavaScript/CSS customizations may be impacted if they change how the header is displayed (e.g. placing a button or field on the header).