To create a new application, open the System Applications | Applications module, as shown in the following screenshot, and click on the New button on the left:
We will be presented with a new application wizard screen like the one shown in the following screenshot:
As we are interested in creating an application that requires a table to store data, we will select the second option to Create custom application. We will be taken to the Create Application page, similar to the one shown in the following screenshot:
Let us populate the form fields in the Create Application page with the following values:
- Name: Travel Booking Application Table
- Scope: (auto filled)
- Menu: (auto filled)
- User Role: (auto filled)
- CreateTable: Set as TRUE
- Table section fields: (use auto filled values)
Click on the Create button to create a new application named Travel Booking Application Table along with the following artifacts:
- An application scope: The process will also create a new scope, as discussed earlier in this chapter. It will consist of x_ prefix along with the customer vendor code. This will also create a new table and user role.
- A user role: A user role in the format of x_[vendor-prefix]_[app-name].user.
- A table: A new table with an application scope namespace prefixed to its name.
- Access control: The table access control list defined for create, read, update, and delete operations.
- An application menu: With the access role requirement set to the user role created with the application.
- A module: A list of records type module linked to the newly created table and the access role requirement set to the newly created user role.
The artifacts such as user roles, table, and so on will use the scope name as the prefix. So while the custom table we created in Chapter 3, Data Management had a prefix u_, all tables in custom application have an x_ prefix. This means that when we create a user role, business service, table, and so on in global scope, it doesn't have any namespace prefix in its name field.
Furthermore, the Applications column for all artifact records will have the value set to the application record when they are part of a private scope application. On the other hand, the value of the application is set to global application record when the artifact records are part of the global application.
We can go back to the System Applications | Applications module page to see our new application listed under the Develop tab, as shown in the following screenshot:
We can click on the Edit button next to the custom application to open it in Studio, which enables us to quickly create, edit, and manage application artifacts.