ForceActive Control/List Column User Property is Inconsistent in Behavior (Doc ID 2113364.1)

Last updated on JULY 06, 2017

Applies to:

Siebel CRM - Version 8.1.1.11 [IP2013] and later
Information in this document applies to any platform.

Symptoms

ForceActive Control/List Column User property should make the corresponding field active, even if Siebel CRM does not display it in the client.

However, it has an inconsistent in behavior, meaning it is not cascading the field as active for certain scenarios.

Steps to replicate

-----------------------------------------------
1. Service Request BC
     - created MV link "TST Solution"
          * Destination BC: Solution
          * Destination Link: Service Request/Solution
     - created MV field "TST Solution Status"
          * Destination Field: Status
          * Multi Valued: TRUE
          * MVL: TST Solution
     - created calculated field "TST Flag"
          * Calculated Value: EXISTS([TST Solution Status] = LookupValue('SOLUTION_STATUS','Final'))

2. Service Request Detail Applet
     - created control "TST Button" and added it to the web layout, button caption = 'Custom Method'
     - created applet user property "CanInvokeMethod: CustomMethod12" for method invoked by newly created button
     - created control "TST Flag" and control user property "ForceActive" and value Y

3. Service Request List Applet (Account)
     - created control "TST Button" and added it to the web layout
     - created applet user property "CanInvokeMethod: CustomMethod12" for method invoked by newly created button
     - created control "TST Flag" and control user property "ForceActive" and value Y

 Results

-----------------------------------------------

1. Go to Accounts > Accounts List > Drilldown on ACC1 and navigate to the Bottom Applet Account - Service Request detail view.
2. Select service request record SR1 and verify that custom button is disabled on service request list applet
4. Drilldown SR1 and verify that custom button is disabled on service request form applet
5. Navigate back to Account - Service Request detail view using thread bar link
6. Select SR2 and verify that custom button is enabled on service request form applet
7. Drilldown SR2 and verify that custom button is enabled on service request form applet

Step 7 is failing as button is disabled.

 

Changes

 N/A

Cause

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