Processing Siebel Operation Steps in Sequence
This topic explains how setting the ProcessArgAsc parameter in the
Siebel Object Manager configuration file enforces the processing of Fields in the defined
sequence during Siebel Operation Steps in Tasks or Workflow Processes, ensuring dependent
fields are updated in the correct order.
In the configuration file (for example fins.cfg) used for your Object Manager you can direct how the Siebel Application will handle Fields and their values during a Siebel Operation Step in a Task (TBUI) or in a Workflow Process. In the configuration file, it appears as following:
[Task]
ProcessArgAsc = trueThe ProcessArgAsc parameter tells the Task or Workflow to process the
Fields in the sequence in which they appear in the Siebel Operation Step.
Siebel Operation Steps do not necessarily process the Fields using the sequence defined on the Siebel Operation Step, but this parameter, when set to True (case insensitive so “TRUE”, “True”, and “true” will all work) will process the Fields in ascending order according to their Sequence value in the Step. This will help to ensure that if a Field (FieldA for example) in the underlying Business Component depends on another Field (FieldB) having its value set first, using this parameter can enforce that.
In the Siebel Operation Step in your Task or Workflow, set FieldB to have a lower Sequence value than FieldA and set this parameter to True. FieldB will then be updated before FieldA.