Siebel Open UI >  Siebel Open UI LOV errors - Part 2

Hierarchical List of Values is Failing in Workflow Process but works from the UI

APPLIES TO:
Siebel Workflow Manager - Version 16.11 [IP2016] and later
Information in this document applies to any platform.
SYMPTOMS
On : 16.11 [IP2016] version, Siebel Workflow

Hierarchical list of values is failing in workflow process but works from the UI
For a hierarchical pick list for SR status and sub status, the values need to be set to Done and Escalated. This works from the UI. In workflow processes however it is not working.
When both status and sub status are set in a single step, it fails. However when status and sub status are updated in different workflow steps , it works.

Reproduction steps:
The issue can be reproduced at will with the following steps:
1. Go To Siebel Tools
2. Navigate to Workflow Processes
3. Simulate workflow 'PPS Auto Escalate Test'.

Error messages:

ObjMgrBusCompLog Error 1 0000000259412784:0 2017-06-14 06:00:52 (buscomp.cpp (33780)) SBL-DAT-00225: The value entered in field Sub-Status of buscomp Action does not match any value in the bounded pick list PickList Hierarchical Sub-Status.
ObjMgrLog Error 1 0000000259412784:0 2017-06-14 06:00:52 (svbcoper.cpp (534)) SBL-BPR-00100: This error is returned when the workflow/task is executing the Siebel Operation business service.
ObjMgrLog Error 1 0000000259412784:0 2017-06-14 06:00:52 (stepexec.cpp (1370)) SBL-BPR-00187: Error updating business component at step 'Update Status Sub-Status'.

CAUSE
Issue caused by incorrect setup

This issue is described in My Oracle Support's Note: Error in updating a hierarchical Picklist using workflows
This note outlines the issue that you encounter: Error updating business component at step 'Hold Activity Status'.(SBL-BPR-00187)
--
This error is returned when the workflow/task is executing the Siebel Operation business service.(SBL-BPR-00100)
--
The value entered in field OS CC Sub Status of buscomp Action does not match any value in the bounded pick list OS CC Activity Sub Status.(SBL-DAT-00225)
The note also explains that the issue is caused by a setup similar to what you have.

Put two Siebel Operation steps.
Siebel Operation Update Step 1:- Update the Status
Siebel Operation Update Step 1:- Update the Sub Statu

SOLUTION
Add two distinct steps in workflow process to update the status and substatus:

1. Go To Siebel Tools
2. Navigate to Workflow Processes 'PPS Auto Escalate Test'.
3. Add two distinct steps in workflow process to update the status and substatus

----//----

Another solution will be to add the parameter: ProcessArgAsc = true into OM's config file

1. Login on Siebel OpenUI
2. Go to Sitemap > Administration - Server Configuration > Servers > Query for "Workflow Process Manager" > Parameters > Query for "OM - Configuration File" and confirm that the value is "siebel.cfg".
3. Go to C:\Siebel\ses\siebsrvr\BIN\enu or your language.
4. Backup your siebel.cfg file
5. Set "ProcessArgAsc" = True
e.g

[Task]
ProcessArgAsc = true

6. Bounce the "Workflow Process Manager" Component and Siebel Server.
7. Retest

 

OpenUI - Manifest LOV Seed Data Contain Wrong Values

APPLIES TO:
Siebel eCommunications - Version 8.1.1.11.5 [IP2013] and later
Information in this document applies to any platform.
SYMPTOMS

Seed data for LOV values of Type MANIFEST_EXPR_OPERATOR, MANIFEST_OBJECT_TYPE, MANIFEST_OBJECT_USAGE_TYPE are in DEU.
But they should be in ENU

STEPS
The issue can be reproduced with the following steps:
1. Go to LOV administratioin
2. Query for one of the types MANIFEST_EXPR_OPERATOR, MANIFEST_OBJECT_TYPE, MANIFEST_OBJECT_USAGE_TYPE
=> Values are not the save as the LIC (language independent values)


CAUSE
LOV values seem incorrect.

Non-translatable Non-multilingual LOV should have same value from LIC and Value.

SOLUTION


There has been logged a Bug 18067602 for the described behavior and it has been fixed with 8.1.1.14. (Please note, this is an internal Bug and will not be visible for you)

Workaround:

is to change the LOV Values to the values of the LIC for the LOV Types: MANIFEST_EXPR_OPERATOR, MANIFEST_OBJECT_TYPE, MANIFEST_OBJECT_USAGE_TYPE