SCV macro processing stopped on error status

Since SCP version 21.3, it is possible to override the SCV macro processing behavior in case of errors. The following describes the default macro processing behavior for SCV jobs:

  • When an SCV Job ends with Information, the corresponding macro also ends with Information (success) and macro execution continues.
  • When an SCV Job ends with Warning, the corresponding macro also ends with Warning and macro execution continues.
  • When an SCV Job ends with Critical, the corresponding macro ends with Warning and macro execution continues.

SCV Jobs can return with Critical severity for several reasons, like incorrect input parameters. However, this cannot have one single rule for the macro execution to determine if the macro must continue or stop. For example, an SCV data enhancement job can update a column which is critical in the planning process and hence the macro execution must stop if the SCV job ends displaying an error message. Another enhancement rule can be updating an information only column and this does not affect the planning process if the SCV job ends with error. The SCP_EXECUTION_STOP_ON_STATUS SCV configuration parameter is already available to override the default macro processing behavior for all SCV Jobs.

In this release, the app_var_scp_execution_stop_on_status application variable is introduced to override the default macro processing behavior for individual macros. Possible values for the new application variable are <empty>, "Warning" and "Error". Default is <empty> (i.e. continue). If the SCV Job ends with the specified status, macro execution stops with the status set to Critical.

All SCV data processing macros using the RunSCV command are updated to accept the new application variable as input parameter:
RunSCV(. . .,"-STOP_ON_END_STATUS=%app_var_scp_execution_stop_on_status%")

The default value for the app_var_scp_execution_stop_on_status application variable is <empty>, therefore, the default behavior remained unchanged.

Note: This feature is enabled after loading the base template (base.zip) for the current version. A new role or privilege is not required to access this feature.