Siebel Business Process Designer Administration Guide > Workflow Policies > About Customizing Workflow Policies with Siebel Tools >

Creating a Workflow Policy Program

A workflow policy program is a generic event that actions are based on. You define a program by defining the workflow policy event.

CAUTION:  Do not rename or change the name of an existing workflow policy program. If you do so, you will lose all the actions created for the program.

When creating a workflow policy program that inserts new records, you must determine and provide the minimum field values that constitute a valid record as defined in the repository for the table:

  • Provide values for all required columns. If a default value is defined for a column, that default value is used on the insert if the program specifies none. For example, S_EVT_ACT has two required columns: NAME and ROW_STATUS. ROW_STATUS defaults to Y so you do not have to set a value in the program (although you can).
  • You do not need to provide a value for system-generated columns such as CREATED, CREATED BY, LAST_UPD, LAST_UPD_BY, ROW_Id, MODIFICTION_NUM, CONFLICT_Id.

For more information, see Siebel Data Model Reference.

Siebel Systems recommends that when you want to define a new workflow policy program that you copy an existing program that is similar to what you need and then modify the copy to suit your specific business needs. The advantage to using this method is that if something goes wrong with your customized program, you can always start over with the original existing program. Additionally, modifying a copy of an existing program is less error-prone that creating an entirely new program.

CAUTION:  Thoroughly test any SQL queries that you plan to use with customized policy programs. Be aware that if the SQL statement fails to find rows, the workflow policies action is unable to process any tokens.

To create a workflow policy program

  1. In Siebel Tools, choose Program.
  2. Select an existing program that is similar to what you need for the new workflow policy program.
  3. Click the right mouse button and choose Copy Record. This copies the entire program including the program arguments.
  4. Modify the appropriate fields, such as Workflow Object, to meet the needs of the new program.
  5. Define the program arguments.

    Enter the arguments carefully to make sure capitalization, punctuation, spelling, and so on are correct:

    • Type the entries in the Name column exactly as indicated in Table 55. Primary ID, Primary Table, Operation Type, SQL Statement, and SQL Statement Outputs must have one space between each word and each word must be properly capitalized. For example, Primary ID must have one space between the two words, capital P, and lowercase d.

      NOTE:  In program arguments, the carriage return character that exists in SQL Statement and SQL Statement Outputs can cause unexpected behavior for a workflow policy program. In most cases, the substitution value is not substituted with the intended value but is instead substituted with the [Label] literally. Avoid using the carriage return character.

    • When using SQL statements in program arguments, make sure that the statements are specific to the particular RDBMS you are using.
    • Type the names of the column pairs exactly: One space between each word, identically capitalized, one space in front of the left parenthesis and no spaces in the (Column).

      The order of the rows is not important.

      NOTE:  Before using a program and its related program arguments in a workflow policy, you must delete any inactive or incomplete program argument definitions. These could cause Workflow Monitor Agent errors.

Siebel Business Process Designer Administration Guide