Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Application tables

Log in to subscribe to topics and get notified when content changes.

Application tables

Application developers create tables and their associated lists and forms for users to add and update records.

An application owns its tables and determines whether other applications can access resources from them. For example, the Book Rooms application can store conference room data in the Conference Rooms [x_acme_book_rooms_conference_rooms] table and permit other applications to read this data.

The system uses standard access controls to manage user access to application data. During application creation, developers can specify an application-specific user role for these access controls. They can also use application access settings to manage runtime and design time access to application tables.

User interface elements

By default, the system creates a list and form view for each table.

Application developers can configure the layout of these views to provide a basic user interface. In addition, they can also create supporting menus, modules, or UI pages to access these list and form views.

Alternatively, developers can create their own custom user interface with Service Portal or the Content Management System.

Application user roles

Application developers can create application-specific user roles to control access to application data.

Application developers can create an end-user role for the primary users of a custom application. The system automatically restricts access to application data by:

  • Standard record operations on application tables are restricted to the application user role or the admin role.
    • Create
    • Read
    • Write
    • Delete
  • The application menu is restricted to the application user role or the admin role.
  • All application modules are restricted to the application user role or the admin role.

Application developers can create additional user roles to support the application but must manually create any associated access controls or role requirements.

Web services integrations

Application developers can create web services integrations to application tables.

By default, the system allows other applications to access application tables using web services integrations. Application developers can allow or restrict web services access from the table application access settings.