IBM Support

JR47297: TEXT OUTPUT FIELD WILL BECOME "READONLY" VS. "REQUIRED"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer has created a table.  Within the table, it has a text
    field.
    Underneath the table, it has a Output Text, which bound to a
    variable
    with a List.   The first element of the name of the list.  Then
    later
    the table, it is bound to a text field.  It is map to the
    variable
    called visibility with value 'REQUIRED'.  This application works
    fine
    and the value is display correctly.
    
    However, if the text field within the table is associated with
    the
    visibility and map its variable to visability, then the text
    output
    field value will become 'READONLY instead of "REQUIRED".
    
    The fix is currently targeted for next cumulative maintenance
    deliverable on 8.0.1.
    

Local fix

  • n/a
    

Problem summary

  • The stock Table control by design uses the visibility
    configuration option of the cells to provide the "click-to-edit"
    functionality. So when a Text control is marked as REQUIRED
    within a Table cell and this Table is using the "click-to-edit"
    functionality, the control will be changed to READONLY by the
    Table.
    
    USER AFFECTED:
    Business Process Manager Advanced, Standard and Express Coach
    users
    
    PROBLEM DETAILED DESCRIPTION:
    The stock Table control by design uses the visibility
    configuration option of the cells to provide the "click-to-edit"
    functionality. So when a Text control is marked is REQUIRED
    within a Table cell and this Table is using the "click-to-edit"
    functionality, the control will be changed to READONLY by the
    Table. In addition to this, when the table is first loaded the
    column headings for a "REQUIRED" cell/column is not decorated
    with a red asterisk and is only done after certain actions are
    taken in the table (for example, resizing column, sorting
    column, deleting a row, adding a row).
    

Problem conclusion

  • Here are the some things to consider when wanting to have
    REQUIRED cells/columns in a stock Table control. The stock Table
    control by design uses the visibility configuration option of
    the cells to provide the "click-to-edit" functionality. If this
    is not desired, there are 2 separate configuration options on
    the Table coach view to control how "click-to-edit" behaves for
    users.
     * First is the "Disable Click-to-Edit" configuration option
    which has the following description "Select this option if you
    want the entire table to be editable without requiring the user
    to click individual cells to edit them.". So basically this
    turns off the "click-to-edit" support of the Table. This can
    have performance implications with Table containing a large
    number of cells or when rows are added/deleted from tables
    nested within another table.
     * Second is the "Set Editable Columns" configuration option
    which has the following description "Select this option if you
    want certain columns to be editable without requiring the user
    to click individual cells to edit them. Use a comma-separated
    list to specify these columns. For example 1,3 makes the cells
    in the first and third columns directly editable." So this
    option allows for only the specified columns to be always
    editable, as such the visibility is not altered.
    
    After trying to make cells/columns REQUIRED, we discovered that
    the stock Table control does not initially mark the Required
    columns with a red * in the column heading. This is the problem
    that was addressed with this APAR.
    
    FIX AVAILABILITY:
    Fix for 8.0.1.1 has been included in Coaches cumulative toolkit
    fix for JR47855 . Fix is available on Fix Central,
    http://www-933.ibm.com/support/fixcentral/ . Search for APAR
    JR47855.
    
    When downloading interim fixes, ensure that the complimentary
    readme is obtained and reviewed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR47297

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-07-23

  • Closed date

    2013-10-16

  • Last modified date

    2013-10-24

  • 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

  • R801 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
24 October 2013