How does workflow work in Siebel?
Workflow policies are a set of conditions that, when violated, triggers an associated workflow action. The workflow action initiates a workflow process, that sends the modified data to the gateway reader module.
Is updated in Siebel Workflow policy?
Siebel CRM joins workflow policy conditions when it runs an IS UPDATED statement, but the format of the trigger.
How do I create a workflow policy in Siebel?
Configuring a Custom Workflow Policy Component Column
- In Siebel Tools, navigate to the Workflow Policy Columns list.
- Query the Name property for the name of the column you must modify.
- Navigate to the Workflow Policy Objects list, and then query the Name property for the workflow policy object that you require.
How do you run a trigger in Siebel?
- In the Siebel client, navigate to Administration-Server Management > Jobs.
- In the Jobs list, click New.
- From the Component/Job drop-down list, choose Generate Triggers.
- In the Job Parameters list, click New to modify parameter settings.
- Enter your Privileged User name and password.
How do I create a workflow policy column in Siebel?
How do you generate triggers?
Creating Triggers
- CREATE [OR REPLACE] TRIGGER trigger_name − Creates or replaces an existing trigger with the trigger_name.
- {BEFORE | AFTER | INSTEAD OF} − This specifies when the trigger will be executed.
- {INSERT [OR] | UPDATE [OR] | DELETE} − This specifies the DML operation.
What is SQL trigger?
A SQL trigger is a database object which fires when an event occurs in a database. We can execute a SQL query that will “do something” in a database when a change occurs on a database table such as a record is inserted or updated or deleted. For example, a trigger can be set on a record insert in a database table.
What is cursor in DBMS?
A cursor is a temporary work area created in the system memory when a SQL statement is executed. A cursor contains information on a select statement and the rows of data accessed by it. A cursor can hold more than one row, but can process only one row at a time.
How do I monitor a workflow group in a Siebel enterprise?
Only one Workflow Monitor Agent and Workflow Action Agent can monitor a workflow group in a Siebel Enterprise. For example, assume a regional node runs a Workflow Monitor Agent that monitors a group named Group 1. Another Workflow Monitor Agent that resides in the headquarters node monitors a group named Group 2.
What does the workflow monitor agent do?
The Workflow Monitor Agent runs several server processes that monitor the Siebel database. It does the following: Examines the S_ESCL_REQ table to determine when the workflow policy conditions are met. Monitors workflow policies in a single group. You can run only one process of the Workflow Monitor Agent on one group at one time.
How does Siebel calculate the duration of a workflow policy?
If a workflow policy includes a duration, then Siebel CRM calculates the duration starting with the time that the Workflow Monitor Agent detects that the row is in violation of the policy. It does not start the duration from when Siebel CRM inserts the row in the S_ESCL_REQ table.
What is action action agent in Siebel CRM?
Action Agent is True and the request in the S_ESCL_REQ table does not include a duration in the workflow policy. The request remains in the S_ESCL_STATE table until the duration is met or until Siebel CRM removes the request because the workflow policy conditions are no longer met.