Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
2000_concepts:0200_basics:0300_processes_link_ui_business_logic [2022/08/21 22:48] – ↷ Links adapted because of a move operation administrator2000_concepts:0200_basics:0300_processes_link_ui_business_logic [2026/08/13 00:55] (current) – ↷ Links adapted because of a move operation localdev
Line 1: Line 1:
 +{{tag>process user_interface business_logic concepts}}
 [<10>] [<10>]
 ====== Processes as Links between User Interface and Business Logic ====== ====== Processes as Links between User Interface and Business Logic ======
  
-As we said in the [[2000_concepts:0200_basics:0200_business_rules_carriers_business_logic|Business Rules as Carriers of Business Logic]] section business logic of an application //**Aware IM**// is encapsulated in business rules, which get triggered whenever business objects are created or modified. Let us now have a look at when these creations and modifications take place. +As we said in the [[2000_concepts:0200_basics:0200_business_rules_carriers_business_logic|Business Rules as Carriers of Business Logic]] section business logic of an application //**AwareIM**// is encapsulated in business rules, which get triggered whenever business objects are created or modified. Let us now have a look at when these creations and modifications take place. 
  
 The initial trigger that leads to the creation or modification of a business object is almost always some external request to the system usually from a user who sends this request via the system’s User Interface. The user can perform this request in two ways – she can explicitly ask the system to create a new instance of a business object or edit an existing instance. More often though a user asks the system to start a //process//, which will then create or modify a business object(s). The initial trigger that leads to the creation or modification of a business object is almost always some external request to the system usually from a user who sends this request via the system’s User Interface. The user can perform this request in two ways – she can explicitly ask the system to create a new instance of a business object or edit an existing instance. More often though a user asks the system to start a //process//, which will then create or modify a business object(s).
Line 11: Line 12:
  
  
-{{ documentation:images:process_interaction_flowchart.png?nolink&590 |}}+{{ docs:images:process_interaction_flowchart.png?nolink&590 |}}
  
  
-<note>Even though a process itself usually consists of rules it is not supposed to implement any business logic other than triggering the initial change as described above.</note>+<callout type="primary" icon="true" title="note"> Even though a process itself usually consists of rules it is not supposed to implement any business logic other than triggering the initial change as described above.</callout>
  
-<note>A process may be started not just by the User Interface but also by other forms of external requests – for example, a request from other software system through a service (see [[2000_concepts:0900_prod_feats:0300_comm_with_other_systems|Communication with Other Systems]])</note>+<callout type="primary" icon="true" title="note"> A process may be started not just by the User Interface but also by other forms of external requests – for example, a request from other software system through a service (see [[2000_concepts:0900_prod_feats:0300_comm_with_other_systems|Communication with Other Systems]])</callout>
  
  
 The illustration below shows the make up of a process transferring funds between two accounts. The illustration below shows the make up of a process transferring funds between two accounts.
  
-{{ :documentation:images:rules_table_example.png?nolink&590 |}}+{{ docs:images:rules_table_example.png?nolink&590 |}}
  
-Note that the process is very small and is mainly concerned with allowing the user to enter necessary details and presenting the results of the operation to the user. All the business logic behind the funds transfer operation (such as checking whether there are sufficient funds in the source account, calculation of fees for the transfer operation etc) is expressed in business rules related to the object ''FundsTransfer'' (they are not shown here). //**Aware IM**// evaluates these rules as soon as the user enters the data for the ''FundsTransfer'' object (between “Display funds transfer form” and “Check for transfer success” operations).+Note that the process is very small and is mainly concerned with allowing the user to enter necessary details and presenting the results of the operation to the user. All the business logic behind the funds transfer operation (such as checking whether there are sufficient funds in the source account, calculation of fees for the transfer operation etc) is expressed in business rules related to the object ''FundsTransfer'' (they are not shown here). //**AwareIM**// evaluates these rules as soon as the user enters the data for the ''FundsTransfer'' object (between “Display funds transfer form” and “Check for transfer success” operations).
  
 Configuration of processes is discussed in detail in the [[2500_config_apps:0900_add_edit_processes|Adding/Editing Processes]] section. Configuration of processes is discussed in detail in the [[2500_config_apps:0900_add_edit_processes|Adding/Editing Processes]] section.