Profile Attribute Not Caching Issue for WFProcMgr (Doc ID 1629651.1)

Last updated on MARCH 07, 2014

Applies to:

Siebel Workflow - Version SIA [20436] and later
Information in this document applies to any platform.


If a WF process is run in WFProcMgr and it defines a value for a profile attribute this profile attribute value can be read in another task if it's run in same MT Server.

If this profile attribute is used for example in a calculated field for a BC a wrong value can be generated.


1 - Create a WF1 that defines a profile attribute Attr1 with value Value1 e.g. using BS SessionAccessService with method GetProfileAttr.

2 - Create another WF2 that reads a value of attribute Attr1.

3 - Execute WF1

4 - Execute WF2 and inspect the logs and it can be verified that WF retrieved value Value1 even it was not defined in WF.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms