Actions, Determinations and Validations

Explanation

Actions expose custom operations (Approve, Cancel) beyond CRUDQ. Determinations fill derived fields automatically at defined trigger points. Validations enforce business rules and can return messages. Together they replace much of the classic user-exit landscape.

Code example

validation validateDates on save { create; update; }action ( features : instance ) Approve result [1] $self;

Real project scenario

An expense-report app used validations to enforce policy limits and a determination to auto-set the reviewer based on department.

Common mistakes

Placing rules in the UI layer; forgetting to declare features (features : instance) causing 'unauthorised' Fiori messages.

Best practices

Model rules where they belong; expose actions as verbs (Approve, Cancel); test with ADT unit tests for behaviour.

Interview angle

Difference between validation and determination.