JR43184: NO INDICATOR SHOWN FOR EMPTY REQUIRED DATE FIELD IN A COACH

Version 8.0 Refresh Pack 1 for the IBM Business Process Manager products
Version 7.5.1 Fix Pack 1 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• In a coach, if a date (selector) field is required but is not
  populated when the user clicks the OK button, the date field is
  not highlighted in red (as missing required fields of other
  types are) to indicate that a date must be selected.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of BPM Express, BPM Standard and BPM  *
  *                  Advanced.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: In a coach, if a date (selector)        *
  *                      field is required but is not            *
  *                      populated when the user clicks the OK   *
  *                      button, the date field is               *
  *                      not highlighted in red (as missing      *
  *                      required fields of other                *
  *                      types are) to indicate that a date      *
  *                      must be selected.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The field validation logic for coaches was not correctly
  handling date fields (an error message was being displayed on
  the coach if a required date field was missing, but logic to
  highlight the field in red was missing).
  

Problem conclusion

• Changes to the field validation logic for date fields, in
  addition to changes to coach designer artifacts (in the
  Teamworks application, Portal application, and system
  toolkit), resolved the issue.
  
  An interim fix for Business Process Manager Version 7.5.1.0
  been published to Fix Central.  Below is prerequisite
  information and installation/uninstallation instructions for
  the interim fix (also published to Fix Central in a separate
  file that is automatically downloaded with the interim fix):
  
  
  Prerequisite information
  ========================
  
  Prereqs:
  JR42576, JR42765, JR42894, JR43096
  
  Supersedes:
  JR42727, JR42954, JR42959, JR42983, JR43612
  
  Following is the interim fix installation order based on
  prerequisites:
  
  Process Center/Server:
  JR42012-JR42280-JR42220-JR42232-JR42330-JR42342-JR42576-JR42331-
  JR42452-JR42765-JR42894-JR42683-JR43096-JR43184
  
  Process Designer:
  JR42012-JR42280-JR42894
  
  
  Installation instructions
  =========================
  To install the JR43184 interim fix, follow these steps:
  
  1.  Back up the BPM and Performance Data Warehouse databases.
  (This is important because part of the prerequisite fixes
  
  go into the database and a database backup is required to
  revert the fix from the database.)
  
  2.  Back up the stand-alone profile or all profiles in a
  network deployment environment.  The "backupConfig" command
  can be used to backup a profile.  See the following
  documentation section:
  
  http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/
  com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rxml_ba
  
  ckupconfig.html
  
  3.  Stop the stand-alone server or network deployment
  environment before applying any fix.
  
  4.  Install the JR43184 runtime interim fix packages using IBM
  Installation Manager.  Prerequisite fixes and other fixes
  
  in the installation order can be installed at the same time as
  JR43184.  Note that some of the prerequisite fixes have
  
  runtime as well as Process Designer fix packages.  The Process
  Designer fixes should be installed one at a time.
  
  5.  Upgrade profiles:
  
  - For a stand-alone environment, follow step two in this
  section:
  
  http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/topic/c
  om.ibm.wbpm.imuc.doc/topics/tmig_upgrading_bpm_errors.htm
  
  l
  
  - For a network deployment environment, follow step three in
  this section for each cluster:
  
  http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/topic/c
  om.ibm.wbpm.imuc.doc/topics/tmig_upgrading_bpm_nd_clusters.html
  
  6.  Run the upgrade_7x command to update the database by
  following step one in this section:
  
  http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/topic/c
  om.ibm.wbpm.imuc.doc/upgrade/topic/upgrading_existing_dbs_751.ht
  ml
  
  You must run the command three times as follows:
  
  First Run: As per step one listed in the above section
  (without any -ifix parameter).  This is for older fixes in the
  prerequisites chain.
  
  Second Run: Add "-ifix JR43096" to other required parameters
  like profileName, etc.
  
  Third Run: Add "-ifix JR43184" to other required parameters
  like profileName, etc.
  
  (The last two runs are specific to interim fixes.  This is
  because upgrade_7x was changed to accommodate changes specific
  to interim fixes, and not require being executed in its
  entirety).
  
  7.  Start the stand-alone server or network deployment
  environment.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R750 PSY

     UP