Default Choice Restriction Plug-in
This article introduces the Default Choice Restriction Plug-in.
This plug-in restricts the user from choosing the default value of a Radio button field.
The packaged sample plug-in zip file can be downloaded from the
Install the plug-in into your domain by following the plug-in installation guide on the Help page .
You can then add the plug-in to a specific App by following the plug-in adding guide on the Help page. .
To set up the plug-in, the Kintone App must have a Radio button field in its form.
There is only one setting for this plug-in, which is to choose which field in the App form will be restricted from having its default value selected. This sample lets users to only select the Radio button field from the drop-down list.
After saving the plug-in settings and updating the App, the plug-in's features will run when a record is saved. If the user has left the specified Radio Button value as its default value, errors will be displayed on both below the field and at the top of the record. The record will also not be saved until the issue is solved.
The sample codes used in the plug-in are listed under the src file in our
The plug-in is created with the following file structure:
This file builds the HTML of the plug-in settings page.
<div> tag with the "block" class represents 1 row of related HTML elements.
The first "block" contains the HTML of the first (and only) setting, where the user chooses which Radio Button to place restrictions on. A select tag is stated in the HTML, that creates a drop-down field with a value of "-----". This drop-down field is later populated by the config.js file.
The drop-down fields have ids allocated to them, which are later specified by the config.js file so that they can be populated with other drop-down choices.
This CSS file is provided on
. This file styles HTML elements on the plug-in config page to fit in with Kintone's UI.
We recommend that you do not make changes to 51-modern-default.css. If you need to style additional elements, or over-ride the default styles, those changes should be added into config.css
This supporting CSS file is used to style some areas of the plug-in config page that 51-modern-default.css doesn't cover.
The function setDropDown is called when the plug-in setting page loads. It uses the
Get Form Fields. Get Form Fields returns an object that contains the form fields for the specified App.
Depending on the endpoint called, Get Form Fields can return either the deployed form fields (the user has clicked Update App in the App Settings and the changes have been committed) or the preview form fields (the form has been saved in the App settings, but the user has not clicked Update App and committed them). This function uses the preview endpoint as users may access the plug-in settings page before they are ready to commit their changes.
As this plug-in needs to use the Radio Button fields to populate the drop-down fields in the plug-in settings, the fields with type value of RADIO_BUTTON (the Radio Button field) are extracted from the returned object. The extracted selections are then appended to the element with the id of select_radio_button_field to create a drop-down list of Radio Button fields in the App.
The default value of the Radio Button fields are also extracted by identifying the value held in the defaultValue property of the fields.
At the end of the setDropDown function, the code looks through the CONF object where any saved setting data are stored. If it's the first time for the user to use the plug-in, there are no saved values, thus no values are placed in the settings of the plug-in settings page. If the user has previously saved any settings before in the plug-in (which are stored using Kintone's setConfig API), then those saved values (the specified Radio Button field) are inserted into the designated plug-in configuration settings.
When the Save button is clicked in the plug-in config page, the selected Radio Button value and the default value of that Radio Button are stored into Kintone using the setConfig API.
Data retrieved with the kintone.plugin.app.getConfig(PLUGIN_ID) method are allocated to variables.
These variables are used when the user clicks on the Save button of the record, which triggers the
The code checks the current selected value of the specified Radio Button field, and sees if it matches the value stored in the RADIO_VALUE variable (the default value of the specified Radio Button field). If it does, strings that contain error messages are inserted into the error property of the specified Radio Button field and the error property of the event object. As the error properties where updated in the event object, returning the event object results in cancelling the saving of the record, and displays error messages both underneath the field and at the top of the record.
The manifest file states the paths of the files that will be used in the plug-in. It also links to the jQuery library hosted on the Kintone CDN, so that it can be called on the config page.
The array in the value of the required_params key states which settings in the plug-in config page are required. If these settings are not saved using the setConfig API, errors will be displayed on other pages of the App, stating that the plug-in settings have not been configured yet.
The name, description, and homepage_url key-value pairs are labels and links displayed in the plug-in settings.
This plug-in is open sourced under the
. It allows open- or closed-sourced distribution, including commercial use.
If you would like to add more functionality to the plug-in, you are welcome to clone our repository to make your own changes and redistribute it. We generally do not accept external pull requests for the sample plug-in as this repository exists for educational purposes.
If you have any questions related to building Kintone plug-ins, please post your question in the Kintone Developer Program Community Forum .