Background business processing model of eeplat

Background processing includes data processing, business logic, business processes, and other server operations. Related meta-models include business object meta-models, Business Object attribute meta-models, service meta-models, parameter meta-models, business rule meta-models, and workflow meta-models. As shown in:
The business object is the abstraction of business data and logic. Generally, it corresponds to a table in the database, which can also represent a larger or smaller business scope, such as an independent business module (sales module ), A table can have multiple business objects. A business object can also contain multiple tables. The Business Object completes the business logic through the service and data bus. Data Bus is a medium for sharing and exchanging data between business objects. The data bus is dedicated to threads and thread-safe. changes made by one thread to the data bus do not affect the use of data bus by other threads. Each thread is a copy of the bus used. A property is a property of a business object. For Business Objects of the basic table type, the attribute is the column name of the corresponding table. However, the attribute may not correspond to a column, or the column may not. A property can be a set. If a query service is defined for the property, the property corresponds to the set returned by the Service Execution. In this case, it is generally used to process one-to-many or many-to-many business objects. A service is a behavior that describes a business object. When a data table is initialized as a business object, multiple basic services are formed, including common data operations such as addition, deletion, modification, and query. The subject of the service is an SQL statement associated with the addition, deletion, modification, and query parameters. You can modify these SQL statements and parameter associations for personalized purposes. For example, to change the data status, we can create a new service or modify the default service, and only change the value of this status field. A service can reference one or more other services through rules. Parameters are used to obtain the corresponding values from the Business Object bus. Parameters are generally associated with properties, while table elements are also associated with properties. Table elements are submitted and stored on the form node of the Business Object bus. parameters are taken from the Data Bus Based on the associated properties, if no association property is available or the value is not obtained based on the association property, the parameter value is used. Parameter check is to check whether the parameters of the service are valid before the service executes an operation. You can customize calculation expressions, regular expressions, and extension scripts for parameter checks. Parameter check is defined on parameters and can be reused by multiple services. Rules are concepts introduced to fulfill complex business logic. The Rule Subject defines a service with execution conditions, that is, the service is executed only when the conditions are met. A rule has an execution priority. When multiple rules are executed, the higher the priority, the higher the execution order. Workflows can automate business processes. workflows are mainly composed of nodes through transfer. When a workflow is started, node task submission and rollback are triggered by services, and node execution can also trigger services, these services can be data table changes, business logic execution, or email or SMS messages.
Www. eeplat. com QQ group: 105867861