IV02346: UNABLE TO HIDE A STATUS IN DROP-DOWN LIST IN PROBLEM APPLICATION

APAR status

• Closed as user error.

Error description

• Problem Details
  
  ==================
  In the problem application I try to hide the status SLAHOLD
  I use the conditional expression manager to create following
  expression
  condition:
  
  :status in (select value from synonymdomain where
  domainid='PROBLEMSTATUS' and maxvalue not in ('SLAHOLD'))
  
  Then (from security groups)  I add an object restriction
  (object:
  Problem, apllication: problem, Type: Qualified) to group
  everyone. I
  add the condition that I created.
  
  Now when I open the problem application and open the drop-down
  from the
  status field, I still see the status SLAHOLD.
  
  Application effected
  ====================
  Problem
  
  Steps used to reproduced by L2 Support on BS 7118
  ===================================================
  1. Go to Conditional Expression Manager
  
  2. Create a new condition
     :status in (select value from synonymdomain where
     domainid='PROBLEMSTATUS' and maxvalue not in ('SLAHOLD'))
  
  3. Go to Security group ---> add a object restriction against
  PROBLEM
     with the condition created against Problem application with
  type
  qualified
  
  4. Go to Domain and add the same condition against SLAHOLD
  status
  
  5. Save changes
  
  6. Log as maxadmin and go to problem and click on the lookup
  from Status
  field you will see SLAHOLD which is normal because the condition
  is not
  set against MAXADMIN. group/user
  
  7. But now log in as wilson and go to problem and click on the
  lookup
  from Status field you will see SLAHOLD which is not normal.
  
  
  Product Version #
  ==================
  BS 7118
  

Local fix

• N/A
  

Problem summary

Problem conclusion

Temporary fix

Comments

• step 3. Go to Security group ---> add a object restriction
  against PROBLEM with the condition created against Problem
  application with type qualified
  
  
  
  
  
  => this step is making  the Problem records with SLAHOLD status
  to not show.  This has nothing to do with what's described in
  the issue.
  
  
  
  
  
  step 4. Go to Domain and add the same condition against SLAHOLD
  status
  
  the condition's expression is apparently written against a
  PROBLEM object, not a domain value.  Applying a condition like
  this to a domain value does not make sense.
  
  
  
  
  
  Put these two things aside, this issue is still not a bug.
  That's because on List tab, there is no actual object available
  for evaluating an expression.  The design decision is that for
  List tab and Advanced Searches where there is not actual
  object, we don't consider the conditions associated with domain
  values.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels