Execution profiles

Build 1501 on 14/Nov/2017  This topic last edited on: 13/Nov/2015, at 14:44

All tasks have an optional parameter "Profile" that specifies a profile to use for the task execution, or to assign tasks to the specific Back4 server. The profiles are defined in the Back4 configuration.

Parameter

Name

Description

Name of the execution profile (required).

Default

-

MaxRetries

Number of retries for the task in case of failure (used only for DBTasks).

0 (no retry)

OnSuccess

Log actions to take for task execution success.

"DBLog,EventLog"

OnWarning

Log actions to take for task execution error when the maximum retry number has not been reached.        

"DBLog,EventLog"

OnError

Log actions to take for task execution error when the maximum retry number has been reached

"DBLog,EventLog"

Possible log actions:

None

Take no log action.

DBLog

Log the task execution result in the task log database table.

EventLog

Log the task execution result in the windows event log.

All

Take all the defined log actions (even those that could be defined in the future).

 

NOTE: MaxRetries and OnWarning parameters are currently used only by the DBTasks (Publish and ObjWF). In case of error, if the value of retries has not been reached, the task database entry is updated with the current retry count and the task "in execution" values are cleared so that the task can be selected in the next task polling.

Example:

<ProfileList>

 <ProfileConfig

  Name="MyProfile"

  MaxRetries="10"

  OnSuccess="EventLog"

  OnWarning="EventLog"

  OnError="EventLog" />

</ProfileList>

Enhancements in version 1.4

In version 1.3 it was not possible to create a Back4 profile that does not produce any log. When editing an enumSet attribute defined as required in the schema, then it was mandatory to select at least one entry for that attribute in the editing/creation form. In version 1.4 and newer it is possible to select no entry for an enumSet attribute, EVEN IF it is defined as required in the schema. If you want to unforce the selection of at least one entry (in order to preserve the old behavior for example), then you have to use the "/objectUI/attribute/ui/@forceRequired" option.