Best Practices for BP Separation

Click to copy

1) Reuse of the Business Process

Different application functions can be used repeatedly. In that case, it is recommended to create a separate business process for them and use this process instead of creating the combinations of blocks all the time.

2) Correct naming

The business process name should correspond to its purpose and functionality. If the business process is designed to work with certain database models or specific user roles, you should reflect it in the name.

3) Commenting

Sometimes the name is not enough to represent the work of the business process. Fill in the description of the BP for more detailed information and possible commenting on the features of use.

4) Minimizing database requests

Avoid sending universal requests to the database to obtain redundant data, a significant part of which is not needed in a particular BP. You need to minimize the number of requests to the database and not use _with unnecessarily.

5) Global variables for temporary files

Don’t use databases to save temporary files. The use of global variables will help minimize the number of database accesses and increase the speed of the application.

6) The use of asynchronous mode

Many tasks can be performed without the need to respond to the user. In that case, it is better to use an asynchronous mode of their blocks operation.

7) Separation of large BP

A large number of BP blocks makes it visually unclear. If possible, transform large parts into separate functions. But don't overuse. Break down BP only if necessary.