Add Yourself Plug-in

Introduction

This article introduces the Add yourself plug-in, which is a plug-in version of the sample code introduced in the "Add yourself to a user field with one click" article. This plug-in displays a button on the Record details page, which when clicked adds the user to the specified User Selection field. This removes the need for the user to go through the process of clicking the Edit icon, searching for their name in the User Selection field, and clicking on the Save button.

Plug-in file

The packaged sample plug-in zip file can be downloaded from the Releases page on GitHub.
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.

Overview

To set up the plug-in, the Kintone App must have a User Selection field and a Blank Space field in its form. The Blank Space field must have an Element ID allocated to it through the Blank Space field's settings.

 Image001.png

 

There are three settings to set up on the config page of the plug-in.

For the first setting, select a Blank Space field from the drop-down list where a button will be displayed for the end user.

For the second setting, input a label of your choice that will be displayed on the button.

For the third setting, choose a User selection field where the User's name will be inserted into after clicking the button.

 configaddyourselftpng.png

 

Save the settings and update the App. A button will be displayed on the Record details page. When the button is clicked, the name of the User who clicked the button will be added into the specified User Selection field. If there are other users already listed in the User Selection field, the User's name will be added to the end of the list.

sample001.gif

 

File structure

The sample codes used in the plug-in are listed under the src file in our GitHub repository.

The plug-in is created with the following file structure:

 

plug-in/
├── html/
│            └──── config.html
├── css/
│            ├──── 51-modern-default.css
│            └──── config.css
├── js/
│            ├──── config.js
│            └──── desktop.js
├── image/
│            └──── person.png
└── manifest.json

 

config.html

This file builds the HTML of the plug-in config page. Each div tag with the "block" class represents 1 row of related HTML elements.

addyourselftpng.png


The first "block" contains the HTML of the first settings, where the user chooses which Blank Space field to display the button in. 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.

<div class="block">
<label class="kintoneplugin-label">
<span id ="container_label">Button Space Field </span>
<span class="kintoneplugin-require">*</span>
</label>
<div class="kintoneplugin-row">Please select a space field to insert the button</div>
<div class="kintoneplugin-select-outer">
<div class="kintoneplugin-select">
<select id="select_space_field" name="select_space_field">
<option value="">-----</option>
</select>
</div>
</div>
</div>

 

The second "block" contains the HTML of the second settings, where the user inputs what text to display on the button that will be created in the config.js file. 

<div class="block">
<label class="kintoneplugin-label">
<span id ="container_label">Button Label</span>
<span class="kintoneplugin-require">*</span>
</label>
<div class="kintoneplugin-row">Please enter a button label</div>
<div class="kintoneplugin-input-outer">
<input class="kintoneplugin-input-text" type="text" id="text-button-label" name="text-button-label">
</div>
</div>

The third "block" contains the HTML of the third settings, where the user chooses which User Selection field to add themselves to when they click the button.  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.

<div class="block">
<label class="kintoneplugin-label">
<span id ="container_label">User Selection Field</span>
<span class="kintoneplugin-require">*</span>
</label>
<div class="kintoneplugin-row">Please select a user selection field</div>
<div class="kintoneplugin-select-outer">
<div class="kintoneplugin-select">
<select id="select_user_field" name="select_user_field">
<option value="">-----</option>
</select>
</div>
</div>
</div>

51-modern-default.css

This CSS file is provided on GitHub. 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.

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.

config.js

The function setDropDownForUser is called when the plug-in config page loads, followed by getLayout and setDropDownForSpace.

setDropDownForUser()
.then(getLayout)
.then(setDropDownForSpace);

The setDropDownForUser function is called to create a list of User Selection fields, that are added into the drop-down of the third setting of the config page. This function uses the kintone.api() wrapper from the JavaScript API to call the REST API endpoint 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 config page before they are ready to commit their changes.

function setDropDownForUser() {
// Retrieve field information, then set drop-down
return kintone.api(kintone.api.url('/k/v1/preview/app/form/fields', true), 'GET',
{'app': kintone.app.getId()}).then(function(resp) {
...
...
//run rest of code here after retrieving preview form information from the App
//resp contains the response data
...
...
}, function(resp) {
return alert('Failed to retrieve fields information');
});
}

As the third setting uses User Selection fields to populate the drop-down fields in the plug-in config page, the fields with type value of USER_SELECT (the User Selection field) are extracted from the returned object. The extracted selections are then appended to the element with the ids of select_user_field to make a drop-down list of User Selection fields in the App.

desktop.js

This file runs on the regular pages of the App, such as the Record List and Record Details pages, but not on the plug-in config page. This file uses the sample code included in the "Add yourself to a user field with one click" article. The code used in this plug-in is mostly the same, but it's wrapped in an immediate function with the plug-in ID value as the input parameter. The plug-in ID value is needed for several JavaScript API calls, such as Kintone's getConfig API that retrieves data that was saved in the plug-in config page using the setConfig API.

var CONFIG = kintone.plugin.app.getConfig(PLUGIN_ID);


Data retrieved with the kintone.plugin.app.getConfig(PLUGIN_ID) method are allocated to variables.

var CONFIG_SPACE = CONFIG.space;
var CONFIG_LABEL = CONFIG.label;
var CONFIG_USER = CONFIG.user;


When the app.record.detail.show event is triggered (when the Record Details page loads) , the kintone.app.record.getSpaceElement method is used to get the element of the Blank Space field that was specified in the Plug-in config page. A button is created, and appended onto this element. The Label settings obtained earlier are also applied to the button.

kintone.events.on('app.record.detail.show', function(event) {
member = event.record[CONFIG_USER].value;

// Get the element of the Blank space field
var se = kintone.app.record.getSpaceElement(CONFIG_SPACE);

// Create a button
var btn = document.createElement('button');
btn.appendChild(document.createTextNode(' ' + CONFIG_LABEL + ' '));
btn.id = 'btnAddMine';
btn.name = 'btnAddMine';
se.appendChild(btn);
btn.style.marginTop = '30px';
btn.addEventListener('click', addMemberMine);
});


When the button is clicked, it calls the addMemberMine function.

This process starts off by inserting the logged in user's information (i.e. the user who clicked the button) into the variable loginuser using the kintone.getLoginUser method.
An object objParam is created, so that it can be later used as the parameter for the Update Record REST API. This object is initially allocated with the App ID and Record ID of the record where the code is run.

The objParam object runs through a loop to be populated with user information that already exists inside the User Selection field. After the loop, the user information of the logged in user is also added to the objParam object. If this process is not carried out, and the field is updated with a single user such as "User A", then all existing user information in that User Selection field will be deleted, and replaced by "User A".

The objParam object is then finally used as the parameter for the Update Record REST API call. The page is refreshed after the call, so that the result of the call can be seen on the User Selection field.

function addMemberMine() {
var loginuser = kintone.getLoginUser();

var objParam = {};
objParam.app = kintone.app.getId(); // The App ID
objParam.id = kintone.app.record.getId(); // The Record ID
objParam.record = {};
objParam.record[CONFIG_USER] = {};
objParam.record[CONFIG_USER].value = [];

// If there are other users in the User Selection field, also add those users
for (var i = 0; i < member.length; i++) {
objParam.record[CONFIG_USER].value[i] = {};
objParam.record[CONFIG_USER].value[i].code = {};
objParam.record[CONFIG_USER].value[i].code = member[i].code;
}

// Add the logged-in user
objParam.record[CONFIG_USER].value[member.length] = {};
objParam.record[CONFIG_USER].value[member.length].code = {};
objParam.record[CONFIG_USER].value[member.length].code = loginuser.code;

// Refresh the page
kintone.api('/k/v1/record', 'PUT', objParam, function(resp) {
// Refresh the page on success
location.reload(true);
});
}

manifest.json

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.

"config": {
"html": "html/config.html",
"js": [
"https://js.kintone.com/jquery/3.3.1/jquery.min.js",
"js/config.js"
]
...


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. 

"required_params": [
"space",
"label",
"user"
]


The namedescription, and homepage_url key-value pairs are labels and links displayed in the plug-in config pages.

"name": {
"en": "Add Yourself Plug-in"
},
"description": {
"en": "This sample plug-in adds yourself to a User Selection field with the click of a button in the record details page."
},
"homepage_url": {
"en": "https://developer.kintone.io/hc/en-us/articles/360012298494"
}

Finally

Licenses

This plug-in is open sourced under the MIT License. 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 network community.

Contribution

This sample plug-in was created with the contribution of Fuji Business International
https://www.linkedin.com/in/mfujinoki/

Was this article helpful?
0 out of 0 found this helpful
Do you have any questions or issues related to this article?
Please share your views with us in the Community forums!