Updating to 22.7+ and Task Based UI
Task Based User Interface (TBUI) Tasks were Workspace-enabled in the 22.7 Siebel Monthly Update. Before updating to 22.7 and beyond you must make sure your deployed Tasks have the same version as the Task in your Design Repository.
The update process looks at the Tasks deployed to the Runtime Repository and tries to find the matching source for that Task in the Design Repository. The deployed Task had to originate from a Design Repository at some point, and the application wants to make sure that Design definition of the Task remains active and that their versions are the same.
Prior to Siebel Monthly Update 22.7 (Tasks were not Workspace-enabled) we used these two tables.
| Repository | Table Name | Version Column | Task Status Column | Function of Table |
|---|---|---|---|---|
|
Design (Tools/Web Tools) |
S_TU_TASK |
VERSION |
STATUS_CD (IN PROGRESS, COMPLETED, NOT IN USE) |
This holds the design time definition for the Task. |
|
Runtime (Call Center) |
S_WFA_DPLOY_DEF |
REPOSITORY_VERSION |
DEPLOY_STATUS_CD (ACTIVE, OUTDATED) |
This held the runtime, compiled definition of the Task. |
In Siebel Monthly Update 22.7 and beyond we use these tables:
| Repository | Table Name | Version Column | Task Status Column | Function of Table |
|---|---|---|---|---|
|
Design (Tools/Web Tools) |
S_TU_TASK |
VERSION |
STATUS_CD |
This holds the design time definition for the Task. |
|
Runtime (Call Center) |
S_RR_TASK |
VERSION_NUM |
No need here because if a record is deployed to this table, it is active and ready to be used. |
This holds the runtime, compiled definition of the Workspace-enabled Task. |
The update process will look in your Design Repository to find the Task with the status of COMPLETED that also has the highest version. It will compare this to the same named Task record in S_WFA_DPLOY_DEF that has a status of ACTIVE and has the highest REPOSITORY_VERSION.
For example, Here we have three records with the same TASK_NAME in the Design Repository in a version prior to 22.7. The update process finds two of them are in a COMPLETED status. Out of these two records, the highest VERSION is 1. This is the record the update process expects to find in the S_WFA_DPLOY_DEF Table.
| TASK_NAME | NAME | VERSION | STATUS_CD | INACTIVE_FLG |
|---|---|---|---|---|
|
MyTask |
MyTask:0 |
0 |
COMPLETED |
N |
|
MyTask |
MyTask:1 |
1 |
COMPLETED |
N |
|
MyTask |
MyTask:2 |
2 |
IN PROGRESS |
N |
The update process expects to find a record with a REPOSITORY_VERSION equal to the VERSION in S_TU_TASK and where the STATUS_CD is ACTIVE in the S_WFA_DPLOY_DEF Table.
| NAME | REPOSITORY_VERSION | VERSION | STATUS_CD |
|---|---|---|---|
|
MyTask |
1 |
2 |
ACTIVE |
|
MyTask |
0 |
1 |
OUTDATED |
|
MyTask |
0 |
0 |
OUTDATED |
If they match, there is no issue. But if they do not match, perhaps the design definition has been deleted or inactivated. This means there is an active Task in the Runtime Repository with no source design definition.