Siebel Business Process Framework: Workflow Guide > Defining Custom Workflow Policies > Customizing Workflow Policy Objects >

Configuring a Custom Workflow Policy Program


This topic describes how to configure a custom workflow policy program, which is a generic event that determines an action. To configure a custom workflow policy program, you configure the workflow policy event.

CAUTION:  Make sure you thoroughly test any SQL query that you use with a custom workflow policy program. If this SQL query fails to find a row, then the workflow policies action cannot process a token.

To configure a custom workflow policy program

  1. In Siebel Tools, in the Object Explorer, click Workflow Policy Program.
  2. In the Workflow Policy Programs list, locate a workflow policy program that provides some or most of the functionality that you require.
  3. Right-click the workflow policy program you located in step Step 2, and then click Copy Record.

    Siebel Tools copies the entire program, including the program arguments. For more information, see Copying an Existing Workflow Policy Program.

    CAUTION:  Do not rename or change the name of an existing workflow policy program. If you change this name, then Siebel CRM might not be able to locate the actions that it creates for this workflow policy program.

  1. In the new workflow policy program, modify the properties as necessary to meet the requirements of the custom program, such as the Workflow Object property.
  2. Configure the workflow policy program arguments.
  3. To avoid Workflow Monitor Agent errors, delete any workflow policy program arguments that are not active or that are not complete.

Copying an Existing Workflow Policy Program

If you configure a new workflow policy program, then it is recommended that you copy an existing workflow policy program that provides functionality that is similar to the functionality that you require. You can then modify this copy. If something goes wrong with your custom workflow policy program, then you can start over with the original, unmodified workflow policy program. If you modify a copy, then you can often reuse a significant portion of the existing configuration, which leads to fewer errors than if you configure an entirely new workflow policy program.

Using a Carriage Return in a Workflow Policy Program

It is recommended that you avoid using the carriage return character. If you configure a workflow policy program argument, and if a carriage return character exists in SQL Statement or SQL Statement Outputs, then unexpected behavior might result. Siebel CRM might not substitute the substitution value with the intended value. It might literally substitute it with the [Label].

Configuring Required Values

Table 61 describes the values you must provide if you configure a workflow policy program that inserts a new record. For more information, see Siebel Data Model Reference on My Oracle Support.

Table 61. Values Required When Configuring a Custom Workflow Policy Program
Required Values
Values Not Required

If you configure a workflow policy program that inserts a new record, then you must provide a value for each field that Siebel CRM requires to add this record.

If you configure a default value for a column, and if the workflow policy program does not specify a value, then Siebel CRM uses that default value on the insert. For example, the S_EVT_ACT table includes the following required columns:

  • NAME
  • ROW_STATUS

Siebel CRM sets ROW_STATUS to Y by default. It is not necessary for you to set a value for ROW_STATUS.

Siebel CRM does not require a value for a system column. For example, the following columns are system columns:

  • CREATED
  • CREATED BY
  • LAST_UPD
  • LAST_UPD_BY
  • ROW_Id
  • MODIFICTION_NUM
  • CONFLICT_Id
Siebel Business Process Framework: Workflow Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.