A data action is a piece of logic that performs a create update or delete action on one or more entities.

Exposing data with ODC

Contrary to O11 in ODC entities are always exposed read only and server actions are not public.

The rule is to expose entities read only and to use Service Actions to expose the CRUD operations.

CRUD Templates

We use the CRUD templates application from the forge to speed up and standardize the creation of Entities and Data Actions.

The template has the following elements:

Template Entity

The template entity has the following attributes:

Unique NaturalKey index

An index to ensure the uniqueness of the natural key.

TemplateEntityDbActions

The following CRUD wrappers are available:

• TemplateEntityCreateOrUpdate- Create or update a valid record.
• TemplateEntityDelete - Delete a TemplateEntity record
• TemplateEntityValidate - Performs the TemplateEntity record validation

⚠️ These actions do not contain authorization checks. Make sure these actions are not exposed to anonymous screens. You should create your own business logic that provides the proper interface and authorization checks!

⚠️ When invoked by a timer, bpt or API there is no logged in user.

Utility Actions

💡 You may want to put these actions in a library for reuse.

• NotificationListConcat - Concatenates a list of notifications to one string using StringBuilder.

Adding a new entity and data actions to an application

Preparation

if you haven't done it on a previous occasion, follow these steps:

1. Install the [CRUD Templates application] from the forge.
2. Switch to the logic tab (Ctrl+3) and copy the Utility Actions to your application or library:
   • NotificationListConcat
3. Add a ValidationException to <Your Application>
4. Add a ConcurrentUpdateException to <Your Application>

Creating the new Entity

⚠️ WARNING: Do NOT publish the application before instructed to do so.

1. Open <Your Application>
2. Open the CRUD Templates application
3. Go to the data tab (Ctrl+4)
4. Select TemplateEntity and copy it
5. Switch to <Your Application> and paste the TemplateEntity
6. Rename TemplateEntity to the <new entity name>
7. Open the entity editor and enter a proper description for the entity.
8. In the entity editor open the More options and set the:
   • Label
   • Label (plural)
   • Order by attribute
9. Check that the entity and all the attributes have proper descriptions.

Add database actions for the new entity

1. Switch to the CRUD Templates and go to Logic tab (Ctrl-3)
2. Make sure the folder TemplateEntityDbActions is collapsed
3. Copy folder TemplateEntityDbActions and Paste it in <Your Application> logic tab
4. Go to Data tab (Ctrl-4) and locate the TemplateEntity in the Stencil_DBActions_Pat referenced module
5. Find all usages of the TemplateEntity (F12)
6. Use the button: Replace all instances to replace with your new entity (select in the popup)
7. Remove the TemplateEntity dependency (Del)
8. Using (Ctrl + R): find string "TemplateEntity" and replace all occurrences with your <new entity name>
9. Using (Ctrl + R): find string "TemplateEntities" and replace all occurrences with your <new entity name> plural form. E.g. Products.
10. Fix the errors by replacing the missing entity actions with <new entity name> entity actions and the exceptions;
    • 'GetTemplateEntityForUpdate'
    • 'CreateTemplateEntity'
    • 'DeleteTemplateEntity'
    • 'UpdateTemplateEntity'
    • ValidationException
    • ConcurrentUpdateException

Rename the natural key attribute

A natural key (also known as business key or domain key) is a type of unique key in a database formed of one or more attributes that exist and are used in the external world outside the database (i.e. in the business domain or domain of discourse). In the relational model of data, a natural key is a super key and is therefore a functional determinant for all attributes in a relation. From Wikipedia Natural Key

1. Designate a meaningful name to the Natural Key for your entity and using (Ctrl + R) find string "NaturalKey"and replace all occurrences with that name.
2. Fix the errors one by one by clicking on each of them.
3. If the natural key is a composed of multiple attributes change the <UniqueNaturalKey> index and the validation actions accordingly.
4. When done, check all the Reminder TODO comments (shown as warnings in the TrueChange tab) and remove them when OK.
5. Check that there are no warnings and reminders in the TrueChange tab

Add additional attributes

1. Add any additional attributes and set the properties:
   • Name
   • Description
   • Data Type
   • Is Mandatory
2. Add validation logic for each new attribute in the Validate server action.
3. 1-Click publish your module.