Business Rules

By configuring the Business Rule Handler, business conditions can be set to run during an asset import and may reject assets that fail to meet one or more of the specified conditions (any structure created to support the asset will also be rejected, e.g., a new classification folder to store the asset). Additionally, a business action can be set that performs additional work following import of the asset. By default, 'Standard Business Rule Handler' is the only configuration option available for the Business Rules configuration.

Because this is an optional step, all configuration options are left blank by default, meaning that no business rules will be called as part of the asset upload.

All parameters detailed below are optional.

The screenshot below shows am example of a configuration involving both Business Conditions and Business Actions.

Note: If no business rule conditions or actions should be called as part of the import, there is no need to change the default (blank) configuration.

When selecting the Standard Business Rule Handler, the following parameters can be specified:

  1. Business Conditions

In the 'Business Condition' parameter, click the ellipsis button () and select one or more business conditions that are to be run during asset import.

  • Though multiple business condition IDs can be specified, it is recommended practice to include all relevant conditions in one business condition.

Error Handling

  • If one specified condition fails by returning 'FALSE' or null pointer exception, an error is logged, and the transaction is rolled back. This error handling includes the asset import, as well as the creation of any structures supporting it.
  1. Business Action

In the 'Business Action' parameter, click the ellipsis button () and select one or more business actions that are to be run following the import of an asset.

  • Though multiple business action IDs can be specified, it is recommended practice to include all relevant conditions in one business action.
  • Business actions are invoked following approvals carried out via the Approver configuration. Because of this, if any changes to data need to be approved, the rule itself must include an approval step.

For more information on the Approver, refer to the Approver section of the Asset Importer Configuration documentation here.

Error Handling

  • Errors from all executed business actions will be passed on and logged.
  • Null pointer exceptions and other errors caused by business actions will result in the transaction to be rolled back. This error handling includes the asset import, as well as the creation of any structures supporting it.