API Updates for December

kintone.com was update during the scheduled maintenance on Friday, December 9, 2016 (Pacific). Here are the API updates!

JavaScript API

New features

  • [Smartphone] A new event has been added for when a field value changes upon Record Create / Record Edit

    Added events:
    • mobile.app.record.create.change.<fieldcode>
    • mobile.app.record.edit.change.<fieldcode>

    This event will function in the same way as the desktop version.

  • [Smartphone] A new event has been added for when clicking the save button upon Record Create / Record Edit

    Added events:
    • mobile.app.record.create.submit
    • mobile.app.record.edit.submit

    This event will function in the same way as the desktop version.

  • [Smartphone] New methods are now available to hide fields upon Record Create / Record Edit / Record Details

    Added methods
    • kintone.mobile.app.record.setFieldShown()
    • kintone.mobile.app.record.setFieldShown()
    • kintone.mobile.app.record.setFieldShown()

    These methods will function in the same way as the desktop version.

Spec Changes

  • [Smartphone] The behavior of the kintone app on the smartphone has been changed after clicking the save button when adding or editing records.

    Before the update, saving a record on the smartphone would trigger two events.
    We figured that this was nonsense, so after the update, the specs have changed so that only one event (mobile.app.event.record.detail.show) will trigger.

Bug fixes

  • Fixed a bug where the value of a field that had no edit permissions would be retrieved as "undefined" on a mobile event or mobile JavaScript API, even though it could be retrieved normally on the desktop. The mobile.app.record.create.show event and mobile.app.record.edit.show event will now give back the correct value. Sorry for hiding away things that we shouldn't have had to.

  • Fixed a bug where number fields would still be editable, even after their "disabled" property was set to "true". The mobile.app.record.create.show event and mobile.app.record.edit.show event will now make the field unable to edit when the event object that is returned has the "disabled" property set as "true".

REST API

Bug fixes

  • Fixed a bug where a 520 error would return when the same row IDs of tables were stated multiple times in a POST or PUT API. We'll now be little nicer to return an error message stating not to do that.

Other

  • [Desktop/Smartphone] We've added a document on how to add/remove table rows

    Table rows can be added/deleted by adding/deleting a row object to/from the table's value parameter. We could actually do this before the update, but decided to make this more open instead of keeping it as our own little secret.
    This has been added into our API Docs.
Was this article helpful?
0 out of 0 found this helpful
Comments
Please sign in to leave a comment.