This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| ref:a_f:a:report_error [2026/08/13 00:43] – ↷ Page moved from a_f:a:report_error to ref:a_f:a:report_error localdev | ref:a_f:a:report_error [2026/08/13 07:20] (current) – external edit 127.0.0.1 |
|---|
| <code aim>REPORT ERROR 'Value of the attribute is not defined' </code> | <code aim>REPORT ERROR 'Value of the attribute is not defined' </code> |
| |
| <callout type="primary" icon="true" title="note"> The action stops execution of any rules caused by the initial request to the system(unless there are process failure rules defined – see further notes). If the request was issued by the user the specified error message is displayed on the user’s screen. If the request did not originate from the user interface (for example, the request originated from a scheduled process) the error message is written into the log and the current process is terminated. </callout> | <alert type="primary" icon="fa info-circle"> |
| | **note** |
| |
| | The action stops execution of any rules caused by the initial request to the system(unless there are process failure rules defined – see further notes). If the request was issued by the user the specified error message is displayed on the user’s screen. If the request did not originate from the user interface (for example, the request originated from a scheduled process) the error message is written into the log and the current process is terminated. </alert> |
| |
| <callout type="primary" icon="true" title="note"> The request that eventually caused the ''REPORT ERROR'' action could have changed a number of objects and attributes prior to the execution of the ''REPORT ERROR'' action. All changes to business objects and their attributes prior to the ''REPORT ERROR'' action within the context of the request are discarded when the ''REPORT ERROR'' action is triggered). See also the “[[docs:2000_concepts:0800_data_processing:0200_rules_transactions|Rules and Transactions]]” section.</callout> | |
| |
| <callout type="primary" icon="true" title="note"> If evaluation of rules that caused execution of the ''REPORT ERROR'' action was initially triggered by a process and this process had failure rules attached to it, the changes to the business objects and their attributes prior to the REPORT ERROR action are not discarded. Instead process failure rules are evaluated and the execution of the process continues – see also the “[[docs:2000_concepts:0800_data_processing:0200_rules_transactions:0300_process_failure_rules|Process Failure Rules]]” section.</callout> | <alert type="primary" icon="fa info-circle"> |
| | **note** |
| | |
| | The request that eventually caused the ''REPORT ERROR'' action could have changed a number of objects and attributes prior to the execution of the ''REPORT ERROR'' action. All changes to business objects and their attributes prior to the ''REPORT ERROR'' action within the context of the request are discarded when the ''REPORT ERROR'' action is triggered). See also the “[[2000_concepts:0800_data_processing:0200_rules_transactions|Rules and Transactions]]” section.</alert> |
| | |
| | <alert type="primary" icon="fa info-circle"> |
| | **note** |
| | |
| | If evaluation of rules that caused execution of the ''REPORT ERROR'' action was initially triggered by a process and this process had failure rules attached to it, the changes to the business objects and their attributes prior to the REPORT ERROR action are not discarded. Instead process failure rules are evaluated and the execution of the process continues – see also the “[[2000_concepts:0800_data_processing:0200_rules_transactions:0300_process_failure_rules|Process Failure Rules]]” section.</alert> |