Vous êtes sur la page 1sur 7

Workflow Policies

Policies:

1) Create Policy Group (Combination of Policies)

2) Create Action (We Need to specify the workflow Name)

3) Create Policy

a. Add Condition (Need to Add the condition for initiating the


workflow)

b. Add Action

4) Generate Triggers (Add our policy condition in Database along with the
existing Conditions related to the Table)

5) Enable Workflow Monitor Agent

Parameters:

Use Action Agent: True

Policy Group: Group1

Sleep time: 1

Default task: 1

6) Enable Workflow Action Agent

Policy Group: Group1

Sleep time: 1

Default task: 1
Tables:

S_ESCL_REQ

S_ESCL_STATE

S_ESCL_ACTN_REQ

S_ESCL_LOG

Note: Without specifying condition we cant create Policies

Case Studies:

1. With Duration & with Action Agent:

2. Without Duration & with Action Agent:

3. With Duration & without Action Agent:

4. Without Duration & without Action Agent:

With Policy Duration and With Workflow Action Agent:

When the condition satisfies, a new record will be inserted into


S_ESCL_REQ table. Workflow Monitor Agent picks the record and inserts
into S_ESCL_STATE table and waits till the duration end time is reached.
Once the duration is reached to end time, workflow monitor agent picks that
record and inserts into S_ESCL_ACTN_REQ table.

Workflow Action Agent picks the record and inserts into S_ESCL_LOG
table. Once the record is reached to S_ESCL_LOG table, the workflow has
been triggered properly.
Without Policy Duration and Without Workflow Action Agent:

When the condition satisfies, a new record will be inserted into


S_ESCL_REQ table. Workflow Monitor Agent picks the record and inserts
into S_ESCL_LOG table.

Note: If there is no duration, then S_ESCL_REQ, S_ESCL_ACTN_REQ


and S_ESCL_LOG tables will be involved

If there is no Action Agent, then S_ESCL_REQ, S_ESCL_STATE


and S_ESCL_LOG tables will be involved

1) Create Policy Group

Login to Server ApplicationSite mapAdministration Business


ProcessPolicy GroupsCreate New Record

Name: AccountGroup

2) Create Action

Go To Actions : New Record

Name Program Workflow Object

AccountAction Run Workflow Process Account

Arguments:

Argument Value

ProcessName UpdateAccountType
3) Create Policy

Go To PoliciesNew Record

Name Workflow Object Policy Group

AccountPolicy Account AccountGroup

Conditions:

ConditionField Operation Value

Account Status = Customer

Actions:

Action : AccountAction

4) Generate Triggers

SitemapAdministration Server ManagementJobsCreate New


Record

Component/Job Requested Server

Generate Triggers MIND (Siebel Server Name)

Job Parameters:

Name Value

Privileged User SIEBEL

Privileged User Password SIEBEL

EXEC True
Click on Start button to start the job and wait till the status changes to
Success

Note: In EXEC is False, then trigger will be generated in to


D:\Sea77\siebsrvr folder with name as triggers.sql and then manually
we need to run the file from the data base to generate the triggers in the
database.

If we set EXEC as True, then trigger will be generated directly in Data


Base.

5) Enable Workflow Monitor Agent

SitemapAdministration Server
ConfigurationEnterprisesComponent DefinitionsQuery for
Workflow Monitor AgentCopy Record

Component Alias Component Group

AccountWorkMon AccountWorkMon Workflow


Management

Component Parameters:

Parameter Value

Sleep Time 1

Default Tasks 1

Group Name AccountGroup

Use Action Agent True/False(if set to true go to step 6)

Click on Enable and then Synchronize buttons


If we create any new component, we need to enable and then we need
to synchronize so that the new component will be identified by
Gateway Server

6) Enable Workflow Action Agent

SitemapAdministration Server
ConfigurationEnterprisesComponent DefinitionsQuery for
Workflow Action AgentCopy Record

Component Alias Component Group

AccountWorkAct AccountWorkAct Workflow


Management

Component Parameters:

Parameter Value

Sleep Time 1

Default Tasks 1

Group Name AccountGroup

Click on Enable and then Synchronize buttons

If we create any new component, we need to enable and then we need


to synchronize so that the new component will be identified by
Gateway Server

Restart Siebel services / bounce the Siebel server and check


the results

Vous aimerez peut-être aussi