This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| ref:glossary:process_input [2026/08/13 00:43] – ↷ Page moved from glossary:process_input to ref:glossary:process_input localdev | ref:glossary:process_input [2026/08/13 00:43] (current) – ↷ Links adapted because of a move operation localdev |
|---|
| ===== Process input ===== | ===== Process input ===== |
| |
| If a [[glossary:process|process]] needs one or several [[glossary:business_object|business objects]] to work properly, a [[glossary:configurator|configurator]] should declare such objects as the process input. When the process is executed in the [[glossary:operation_mode|operation mode]] these objects will form the initial [[glossary:context|context]] for the process. | If a [[ref:glossary:process|process]] needs one or several [[ref:glossary:business_object|business objects]] to work properly, a [[ref:glossary:configurator|configurator]] should declare such objects as the process input. When the process is executed in the [[ref:glossary:operation_mode|operation mode]] these objects will form the initial [[ref:glossary:context|context]] for the process. |
| |
| **//[[glossary:aware_im]]//** uses the process input information for various purposes, for example when looking for [[glossary:object_operation|object operations]] for a particular business object, or when determining [[glossary:service_input|service input]] for a [[glossary:service|service]]. | **//[[ref:glossary:aware_im]]//** uses the process input information for various purposes, for example when looking for [[ref:glossary:object_operation|object operations]] for a particular business object, or when determining [[ref:glossary:service_input|service input]] for a [[ref:glossary:service|service]]. |
| |
| |
| |