KrewData Features > Schedule Execution > Configure Data Editing Flow |
Data editing flow can be configured in the Flow Setting tab of Plug-in Settings page.
Displays the commands that are used for configuring data editing flow. For more details about each command, see Commands.
Allows you to drag and drop commands from the command panel to flow creation area.
krewData internally uses the kintone REST API to carry out the operations such as fetching, updating and deleting records of kintone app. There is a limit to the number of API requests that can be made per day. The number of API requests that can be used when executing the current data editing flow is displayed in the header of the flow creation area. For more details about daily limit of API requests, see limit values of kintone REST API in List of Limits topic of kintone documentation. |
There are three steps required for creating a data editing flow.
A data editing flow starts with an "Input App" command and ends with an "Output App" command.
You can define how to aggregate or process the data by placing editing commands between Input App and Output App commands. Each command is connected by a connecting line and data edited by the commands flows in direction of the arrow.
Only one I/O flow can be placed in a single data editing flow. You cannot place multiple independent I/O flows starting with Input App command and ending with Output App command, as shown in the image below. If a flow is divided into multiple I/O flows, you must create multiple data editing flows.
In this topic, we explain how to configure a data editing flow using following aggregation and processing examples.
Select kintone apps to be used as input data of data editing flow.
The Configuration tab gets displayed when you add or click a command icon in the flow creation area. |
Selecting too many fields from the field section impacts performance of the flow. Hence, it is recommended to select the minimum required fields only. |
The Preview tab displays only up to 500 records of the input app. Any records beyond 500 do not get displayed in the Preview tab. |
You can reduce the execution time and API requests of a data editing flow by excluding the unnecessary records of input data. |
Add editing commands after the Input App command to define how the data is aggregated and processed.
Options in the Configuration tab vary depending on the type of command. For details of each command, see Commands. |
As Preview tab may not retrieve all records of the input app, aggregate value displayed in the command preview may differ from the actual output. |
Create a kintone app to export resulting data of the data editing flow created in the steps so far.
|
Click Update App to save the created data editing flow.
|
You can add notes to the flow creation area to add text such as explanation of command settings or the flow itself.
To create a note, click anywhere in the flow creation area and select Add Note from the context menu.
Also, you can create notes specific to a command by selecting the Add Note option from context menu that gets displayed by right clicking the command.
To add a note related to multiple commands, select multiple commands and then click the Add Note option on far left of the page.