Here you’ll find a list of recommendations that you should follow when modelling an application using OMNIA. It’s a group of best practices based on our experience collected from application development.
2. Best Practices
Use meaningful names for modelled artifacts. The name should tell you why it exists and what it does.
Use ETag when consuming the API
Filter behaviour execution to the desired Action
Behaviours can be executed in the sequence of multiple actions. For example, an After Save can be triggered by a Create, Update or Delete. If you want to only execute the code in a given action you should apply a condition at the beginning of the behaviour.
Example to only execute the code if the operation is Create or Update:
if (_Context.Operation.Action != Action.EntityCreate && _Context.Operation.Action != Action.EntityUpdate) return await Task.FromResult(AfterSaveMessage.Empty); (...)
Integration: idempotent requests
Networks are unreliable, so when integrating multiple systems, it’s a best practice to ensure that the requests are idempotent. A request is idempotent if it can be called multiple times without producing additional side-effects after the first call.
To know more about idempotency:
Application Behaviours security
The authorization to execute a given application behaviour should be implemented in the Application Behaviour.
Information like the current Role or Username can be accessed from the
Round Calculated decimal attributes
Decimal attributes that are calculated on C# behaviours should be rounded to match the number of decimal cases defined on UI.
this.Average = Decimal.Round(this.Amount / this.Quantity, 2);