IBM Support

JR52321: DIFFERENT CAPITALIZATION OF GROUP NAMES IN REST API SEARCH CAN CAUSE MULTIPLE GROUPS, ONE FOR EACH CASE VARIATION USED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you look up a group by name in IBM Process Designer or
    search for a group by name by using a REST API or JavaScript
    API, the group name is stored in the capitalization that the
    caller provided. This capitalization might be different from the
    capitalization used in the user registry. For every
    capitalization variation, a new group entry is stored in the IBM
    BPM database, possibly leading to duplicate entries for the same
    group.
    
    
    1. tw.system.org.findRoleByName is now case sensitive (it wasn't
    in BPM 7.5.1.1)
    .
    2. REST API group details is case insensitive on search, but
    stores a unique group for each case of the group that is used to
    search on
    

Local fix

Problem summary

  • When you use one of the following methods to initialize a group
    
    - tw.system.org.findRoleByName(roleName)
    - group REST API
    - task assignment in Process Designer
    
    IBM BPM searches in case-sensitive manner for a group entry in
    the database, exposing the requested group name. If the group
    name is not found in the database, a new group is created with
    the capitalization used in the search request. As a result, two
    group entries with same characters in the name but different
    capitalization exist in the database.
    

Problem conclusion

  • A fix is/will be available for IBM BPM that enables IBM BPM to
    find group names with different capitalization in the database.
    With the fix applied, IBM BPM creates only group entries with
    group names exactly as they are stored in the user repository.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR52321:
    
    1. Select IBM Business Process Manager with your edition from
      the product selector, the installed version to the fix pack
      level, and your platform, and then click Continue.
    
    2. Select APAR or SPR, enter JR52321 , and click Continue.
    
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR52321

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-01-19

  • Closed date

    2015-03-17

  • Last modified date

    2015-07-07

  • 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 STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R855 PSY

       UP

  • R856 PSY

       UP

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

Document Information

Modified date:
07 July 2015