IBM Support

JR53280: INCORRECT USER MEMBERSHIP FOR AD HOC GROUPS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You cannot prevent users from being accidentally removed as
    members from an ad hoc group.
    .
      This is the scenario in which the problem occurs.
    
    1)An instance was created with List of Users routing on the
    first activity.
    2) Adhoc group 2852 was created in bpmdb (we can see this via
    Process Inspector) however, one of the users (named 'KD') is
    not in this group.
       The user is not in the adhoc group because if you try
    to run the task from Process Inspector it is not in the list of
    users presented to run the task via.  Also, the task is not
    visible in KD's dashboard
    

Local fix

Problem summary

  • For ad hoc groups, you are not supposed to change the
    membership. However, you could change the membership of an ad
    hoc group by, for example, directly accessing the database.
    Because ad hoc groups are shared, all subsequently created tasks
    that are assigned to the same list of users are associated with
    the incorrect ad hoc group and its membership. However, there is
    no way to detect such a situation and repair the ad hoc group's
    membership.
    

Problem conclusion

  • A fix is/will be available for IBM BPM that gives you a way to
    monitor and repair user membership for ad hoc groups. After you
    download the fix, you can enable this capability by setting the
    following configuration flag in your 100Custom.xml file:
    
     <server>
       <portal merge="mergeChildren">
         <enable-ad-hoc-group-monitoring>true
         </enable-ad-hoc-group-monitoring>
       </portal>
     </server>
    
    If this option is set to true, monitoring is enabled. As a
    result, when you create the next task that is associated with
    the same list of users that was in use when the ad hoc group was
    created, the membership of the ad hoc group is compared to the
    currently stored membership in the database. If these lists do
    not match, missing users are added to the ad-hoc group's
    membership and superfluous users are removed. The detection and
    repair actions are logged to the SystemOut.log file.
    
    Because incorrect ad hoc group membership should not occur,
    enable this option only when you've noticed incorrect user
    membership for ad hoc groups.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR53280:
    
    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 JR53280, 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

    JR53280

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-05

  • Closed date

    2015-07-08

  • Last modified date

    2016-05-02

  • 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

  • R751 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":"7.5.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
02 May 2016