Bookshelf v7.5: Considerations for Upgrading

Siebel Business Process Designer Administration Guide for Financial Services > Introduction >

Considerations for Upgrading

The Workflow UI Utilities business service no longer exists. The functionality included in the Go To View method can be executed using the new User Interact step.

For sending error notifications when the Workflow Monitor Agent or Workflow Action Agent exits with an error condition, a new parameter called Mail Server is required.

Activity Type is a required field for all activity records. Make sure that all of your existing workflow policy actions and workflow processes that insert activity records include a value for Activity Type.

If you used the Workflow Administration screen in a previous customization, replace this screen with the Front Office Workflow screen in Siebel Tools. The Workflow Administration screen has been inactivated in version 7.0.

In the upgrade process, seeded workflows shipped with the latest Siebel release replace the seeded workflows from the previous release. Seeded workflows have inactive status and version 0. They cannot be modified. To use a seeded workflow, you must revise it and activate it. This causes a new copy of the seeded workflow to be created with the latest version number.

If you want to maintain your customization from the previous Siebel release while incorporating the changes in the new seeded workflows, you must do a manual three-way merge. That is, you must revise and activate the upgraded seeded workflow (version 0) and manually merge it in your customizations.

NOTE: Nonseeded workflows are migrated as-is, carrying over their respective version number. If schema changes or other improvements have occurred in the new Siebel release, then nonseeded workflows may not work.

For Siebel eBusiness Application Integration (eAI) workflows, there is a consideration regarding the <Value> field. Because of backward compatibility, the <Value> field can be defined as "String" even though it may contain binary data. After Unicode migration, the data in <Value> changes to type Binary, causing the passing of this data to no longer be a valid operation. When upgrading EAI workflows, you must do one of two things:

Change the data type of the field to Binary, or

Change the name of the process property from the existing name of the field to <Value>, since <Value> is a special process property that always has the data type Binary.

The following workflow policy components are inactivated in version 7.0. If necessary, you can reactivate these components:

Indirect Account

Indirect Account Address

Indirect Account Industry

Indirect Account Primary Address

Indirect Account Synonym

Opportunity/Indirect Account

Primary Account Address

In addition, the following Sales Team workflow policy component columns are inactivated in version 7.0. You cannot reactivate these components:

Forecast Close Date

Forecast Probability

Forecast Revenue

Sales Team Component