ONEWEB uses schemas and security domains to control access to data and to restrict the use of various database resources.

ONEWEB uses two different database structures for the development environment and for user acceptance or production environment. The development environment should install all schema as the designers have features for preview or simulation and hence need to insert them into the runtime schema. But for user acceptance environment or production we recommended that you install only the runtime schema.

Schema Description

ONEWEB provides easy data access nodes to access data as a micro-service. This section explains the procedure to access data as a service using the Database node in your microflow.

Process Designer provides a Database Activity node for accessing data from the database. You can configure the connection type and the command for interacting with DB like insert, update, select or delete data. Follow the below steps to configure your database activity.

First, create the Input/Output process parameter

Drag and drop the Database node into your process flow. This example shows a process with only database activity. So, drop your database node between the start and end node and then link it between the Start node and the End node

Double click on the Database node to open the configurations panel.

Click the BusinessObject tab and choose the Business Object from the list for input and output

Click the Database parameter tab. Users can set the database connection either using JNDI or JDBC connection setting.

• JNDI

• JDBC

Map the Activity parameter to the Database parameter for input and output.

Save the process.

You can now test the flow using the Simulator Utility

• Enter the value of the input (using double quote) to get output then click Start.

• Database node access data from the database and display the queried data on the screen.

Microflow Designer provides a Database node for accessing data from the database. You can configure the connection type and the command for interacting with DB like insert, update, select or delete data. Follow the below steps to configure your database activity.

First, create the Input/Output process parameter

Drag and drop the Database node. This example shows a flow with only a database node. So drop your database node between the start and end node and then link it between the Start node and the End node

Double click on the Database node to open the configurations panel.

Click the BusinessObject tab and choose the Business Object from the list for input and output

Click the Database parameter tab. Users can set the database connection either using JNDI or JDBC connection setting.

• JNDI

• JDBC

Map the Activity parameter to the Database parameter for input and output.

Save the process.

You can now test the flow using the Simulator Utility

• Enter the value of the input to get output then click Start.

• Database node access data from the database and display the queried data on the screen

ONEWEB provides easy data access nodes to access data from its Process components. This section explains the procedure to access data using the Database node from your process.

ONEWEB provides easy access to data from its UX/ UI components. This section explains the procedure to access data using Smart Form and Page.

There are two ways to access the database from a page created using the page designer.

• Integrating with Microflow.

• Using Local database only for mobile application

Access Database from Page using Microflow. Microflow provides a database node for accessing data from the database. You can configure the connection type and the command for interacting with DB like insert, update, select or delete data.

After preparing Microflow, Integrate Page with Microflow. Read the steps from Page Integration with Microflow. Once the page is integrated, it can interact with the database through microflow.

Access Database from Page using Local Database option The following example shows how to query data from the local database to show on the screen.

First, create the table on the local database and prepare data. Read the steps to create a table from the Local database. (You can link the local database to database server to sync the data from server to local database)

Go to the page where you want to display this data. Select PageContent level and then configure the action to query data as shown in the image below.

Save the page and use Play me to see the results.

App Designer provides you with built-in connectors to access the database. Users can configure the data source and schema in the Datasource Configuration screen.

The user can then choose to set this data source at the entity configuration

Once the entity is linked to a data source, the user can then proceed to map the different modules to the tables in that schema and then map the fields to the columns. All the CRUD operations to the database will be managed by ONEWEB.

Select the table to be mapped in Module Configuration

Select the column name that you want to map to save the data and also search data for "Name"

Enable the property SearchCriteria for fields that you want to use as Search Criteria and enable ShowSearch for fields that you want to see as a result of searching.

To enable table search, add Buttons to trigger Search Action Drag and drop the Entity button and select ENTITY_SEARCH for page action & searchResult() for button action.

Box (1) shows the SearchCriteria and box (2) shows the ShowSearch

To enable Insert and Update of the table add Buttons to trigger Save Action Drag and drop the Entity button and select saveEntity() as button action. The other options available are saveDraftEntity() to save and return to the same screen i.e. within the open entity and saveEntityCommit() to save the transaction with commit

• select ENTITY_INSERT as page action for insert page (create new)

• select ENTITY_UPDATE as page action for update page (update existing)