Workflow Policy Conditions

Policy Condition
IS ADDED :
If a new row is added for workflow policy component, then trigger this workflow policy to be examined.
If it is used in conjunction with standard comparisons, IS ADDED can also be triggered when a record is updated.

IS DELETED :
When specify a child workflow policy component in the Condition field, and nothing is specified in the Condition value.
A child workflow policy component is a workflow policy component that is associated with a parent workflow policy component in Siebel.

Above both comparison don't work on field/column level

IS UPDATED:
When IS UPDATED is not present, the Workflow Monitor Agent only invokes the policy if conditions defined in the policy are violated. However, if an IS UPDATED comparison is included as criteria on a field, then other fields in the Policy conditions are never be present on trigger.sql. But at run time workmon checks other condition of policies.

Ref : Siebel Bookself

Anonymous said...

As per my understanding, All Above Comparison uses OR, not AND, Opposite to common behavior of policies.

Invoking a workflow using custom Menu Item

1.Create Applet method menu item and specify Commnad .
2.Create Commnad and specify Method name as :CustomMethod
3.Set Applet user property : Named Method:CustomMethod- Invokesvc,"Workflow Process Manger"...

Above is an approach for executing WF through Menu.

Workflow Syncronous and Async mode.

Workflow triggers in Sync /Async Mode
Local Sync mode : through Run time /Scripting , Means when WF is processed inside OM then it is called to be in Syncronous mode.

Async mode : Through Workflow Process Mangercomponet.

Remote Sync : We need to use Submit Request Component with Sync Parameter

Remote async : No need to set sync parameter in Submit Request Componet.

Wait Step- siebel Workflow

We can't use wait step in long running workflow.

Workflow default Parameters

workflow has following process properties by default :

1.Object Id : This is the id of primary BC of BO.Every time it takes only id of primary BC.no matter from where you are invoking this.For example , you can invoke a wf through named methode from any child BC.but it will take ID of primary BC.

2. Siebel Operation Object Id : it shows the Row_Id of current BC on which WF is executing.

3.Process Instance Id : this is not very significant.It is Id of Process only.
Tejeshwer said...
Process Instance Id is comes very handy when you need to generate a random number or co relation id.

and i think it is the same id that is used to identify workflow process in the instance monitor.


4.Error Code : this is just error code .

5.Error Messages : Show detail error with error code.