My Oracle Support Banner

How To Migrate Workflows Using Migration Application When Development Environment Is Pos 20.7 version and Target Runtime Environment Is Pre 20.7 (Cross Version Migration) (Doc ID 2727760.1)

Last updated on JANUARY 26, 2022

Applies to:

Siebel CRM - Version 20.7 and later
Information in this document applies to any platform.

Purpose

Cross-Version Migration refers to the situation where 20.7 (or later) has been installed in Development Design Repository (DR) environment, but it has been not yet been installed in any downstream (Test, Production, etc.) Runtime Repository (RR) environments. For more details about Workflow in Workspace in Siebel 20.7 and higher review the Transfer or Information presentation "Siebel CRM 2020 TOI: Workflow in Workspaces Functional Overview". To access that go to Document "Get Proactive - Oracle Applications Transfer of Information (TOI) Online Training (Doc ID 732026.1)" > on drop down "Choose a Product Line" select "Siebel" and search  for the presentations available and click on "Siebel CRM 2020 TOI: Workflow in Workspaces Functional Overview"

The issue that this introduces is that the 20.7+ DR environment will be compiling Workflow Processes to the new table, S_RR_WORKFLOW and exporting them for migration to the RR environment just like any other RR object definition. It will not migrate the non-compiled DR definition of the Workflow Process.

However, if the destination environment is on anything previous to 20.7, the binaries in the destination environment are going to be looking for the DR definition of the object so that it can be activated into the old table, S_WFA_DPLOY_DEF. That definition will not be in the migration package, so there is no way to use the Migration Application to migrate workflows until Production has also been updated to the 20.7 patch level.

As a concrete example, assume that in July of 2020, all your environments are on 19.9 and you plan to have a release in October of 2020 that includes repository changes and features released in Siebel 20.7. You have given yourself three months of lead time to merge the Oracle changes with your changes and test them before updating Production to 20.7 and migrating the October release into Production.

Now assume that in August, you discover a critical issue involving Workflow Processes in Production. You need to be able to fix that independently of the October release branch because it is still work-in-progress. For most objects, such as Applets or BusComps, you could create a new branch off MAIN (or whichever branch matches Production), make and test your changes there, deliver to MAIN, and do an incremental repository migration to Production and the problem would be solved.

However, as described above, this will not work for Workflow Processes, because the 20.7 DR environment will generate records into S_RR_WORKFLOW and not send the DR definition to the 19.9 RR environment, which would allow it to compile to the older S_WFA_DPLOY_DEF table.

Scope

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 Full Migration Solution
 Incremental Migration Solution 
 Individual Workflow Process Migration Workaround
 FAQ
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.