Application

Users can choose from four types: desktop, mobile, REST API, and batch.
Desktop and mobile applications are automatically assigned a URL when deployed, allowing them to be accessed from a browser.
REST APIs are automatically assigned endpoints when deployed, allowing external REST calls to be made.
Batch jobs are added to the batch job list upon deployment and can be executed from the job list.

List

After signing in and selecting the execution environment, the first screen displayed is the application list. Applications under development should always be selected. It can be displayed by clicking on the "Apps" (home icon) from the side menu. You can reselect from the applications under development.

Create

Create an application by clicking the "Add New App" button in the upper right corner. Applications can be selected from the following four types

• Desktop
• Mobile
• REST API
• Batch

Depending on the type you choose, the applications you can develop will vary. The application registers an ID that uniquely identifies the application and a label used to identify the application. The application ID is used as part of the URL.

Edit

You can change the application ID, label, and type. Select "Edit" from the "Application Menu"

Note

• Application type REST API and Batch cannot be changed
• The application type can be changed between desktop and mobile from the Edit menu, but be aware that some applications may display components that are not supported by the application.
  If you change the type of an application created on mobile to desktop and place a component that is only available on mobile (such as a 2D code scanner), it will appear in the desktop application.
  Conversely, components that are only available on the desktop (e.g., data grid) will appear in the mobile application.
  Components that are not supported by each application should be removed.

Application Type	Unsupported Components
Desktop	2D Code Scanner
Desktop	Bottom Navigation
Mobile	Data Grid
Mobile	Spreadsheet
Mobile	Tree View
Mobile	Event Calendar

Delete

Application definitions can be deleted. Select "Delete" from the "Application Menu".

Search

You can filter applications from the [Application Name] in the upper right corner of the screen. A partial match is hit for the corresponding application label.

Export

Application definitions can be downloaded locally as files. This can be done by selecting "Export" from the "Application Menu".

Note

If the zip file is automatically unzipped after exporting in Safari, please uncheck Open "safe" files after downloading in Safari - "Preferences" - "General".

Import

Application definitions exported locally can be uploaded to the service. Select "Import" from the "Add New App" button in the upper right corner of the screen. From the "Import" dialog, select the application definition folder and perform the upload.

Note

When importing an exported application definition, the database name and file path must be changed depending on the import destination environment.
Modify the properties and action definitions in each component according to the environment of the import destination.

Commit

The user can commit an app definition to repository with the application definition against commit.

URL

The deployed application and REST API will have the following URL.

• Application：https://{applicationdomain}/ {applicationID}
• REST API Endpoint：https://{REST API domain}/{dev | prod} / {applicationID}/{resource}

Note

• Custom domain can be set for the application domain.
  For details, please refer to the custom domain for details.
• Application URLs can be parameterized in the form of query string and parameters can be sent to the destination.
  • The URL should end with a “?” followed by the content in the format “name=value” at the end of the URL.
  • If there are multiple values, separate them with “&” and link them together.
    Example）http ://example.com/appId?param1=value1&param2=value2
  • If the length of the URL including query parameters exceeds a certain length, the request itself may not be accepted.
  • If the parameter data includes delimiters, the parameter string must be encoded.
  • In the destination, the $param object to obtain parameter values.