There are 3 possible outcomes: It can modularize your code, to be reused within your application (Don’t Repeat Yourself – DRY). It can act as an infrastructure piece for your factory, to be reused in more than one application. It can be published to the Forge, where it will serve several apps and developers.
A reusable object: Speeds up application creation and delivery. Can be either an application or a module that provides additional features. Should be easy to use and understand, The focus should be main or common use cases. You are successful if your own components have these 3 criteria and right steps to design a component in here. Keep in […more]
Run logic in user device (client-side action) Can create in 2 scopes: Mobile Screen Run logic when there is event as the user interacts with the screen ( e.g. Update button click event) For example, if you have a screen to update a Contact, you can create a Client Action that reacts to user clicking the “Save” […more]
Run on the server (server-side action). Fetch complex data from database, which we cannot fetch by single Aggregate. Fetch data from external system ( by REST API,…) Run simultaneously (at the same time) with the client and server Aggregates to fetch data after each screen loads We can also create Data Actions in Block.
Both of Mobile App and Web Application have Server Action with the same purposes: Reuse in other actions (e.g. Server Action, Data Action, Client Action, Preparation Action, Screen Action) Encapsulate the logic that implements the business rules of our application Server Action run at server side. So considering to not down performance for logic that […more]
Only have in Web Application Right place to put logic to handle events, which raises at user interaction (e.g. button click, link click) Run at client side
It is a kind of action which has only in Web Application: Automatically executed before Web Screen is rendered. Do not need to explicit invoke. Right place to add logics that you want to execute before Web Screen is displayed. (e.g. Fetch data from database, assign variables ) Can also manually add a Preparation to […more]
User Actions are actions that you can create by yourself. We have different action types for Mobile App and Web Application. You can create the following Actions in Mobile App: Data Action Client Action Server Action You can create the following Actions in Web Application: Preparation Screen Action Server Action
Reuse logic with User Actions Reuse screen parts with Web Blocks Encapsulate data formatting with User Functions Use RefreshQuery to rerun a Query
In the module tree, under the Process tab, right-click on the Timer folder and select Add Timer; Choose the action to execute when the timer runs or select (New Server Action) to create a new action.