BPM, Workflow, and Case

BPM, Workflow, and Case

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

  • 1.  Help needed: Understanding LSW_GRP_GRP_MEM_EXPLODED_XREF usage

    Posted 06/18/26 07:47 AM
    Edited by venkatesh sudhandhiran 06/18/26 07:48 AM

    Hello IBM Community,

    I’m trying to better understand the purpose and usage of the table/view LSW_GRP_GRP_MEM_EXPLODED_XREF.

    We are having a slow response while users switch from one role to another in Business Automation Workflow 24.0.0.10 Case Client. My DBA suggests that we create an index on the table mentioned above.

    CREATE INDEX IDX_GRP_EXP_MAIN ON CPEDBUSR.LSW_GRP_GRP_MEM_EXPLODED_XREF

    (CONTAINER_GROUP_ID, GROUP_ID);

     

     Could anyone provide details on:

    • What business scenario this artifact is intended for
    • What columns it contains and how they relate to users, groups, and member data
    • Typical queries or use‑cases that involve this object

    Any insights, documentation references, or sample code snippets would be greatly appreciated. Thanks in advance for your expertise!



  • 2.  RE: Help needed: Understanding LSW_GRP_GRP_MEM_EXPLODED_XREF usage
    Best Answer

    Posted 06/23/26 03:32 PM

    Hi Venkatesh, I believe this table is used for BAW group membership expansion.

    The way I understand it, BAW uses it to keep track of group-to-group relationships, including nested groups. So if a user belongs to Group A, and Group A is part of a role/team group, BAW can quickly determine that the user should have access through that indirect membership.

    That would make sense in your case, since switching roles in Case Client likely causes BAW to re-check the teams/roles/tasks the user is allowed to see.

    For the columns, I'd read CONTAINER_GROUP_ID as the parent group/role being checked, and GROUP_ID as one of the groups inside it. So the index on (CONTAINER_GROUP_ID, GROUP_ID) seems like a reasonable one if your slow SQL is searching that way.

    I'd just ask the DBA to confirm the slow statement is actually using this path before adding it.



    ------------------------------
    Martin Medina
    Lead Engineer
    Raymond James
    St Petersburg FL
    ------------------------------



  • 3.  RE: Help needed: Understanding LSW_GRP_GRP_MEM_EXPLODED_XREF usage

    Posted 06/24/26 02:18 AM

    That's mostly right, with one caveat:

    Case and Process happen to reside in the same AppServer, but have not really merged to share all infrastructure. This table is likely not accessed by Case code at all. Access may happen as a side effect, e.g. when opening Navigator happens to invoke some process-side REST APIs or alike. Other than that, the rule of thumb is: Tables prefixed LSW_ relate to the process side. LSW was the acronym for Lombardi Software, acquired by IBM in 2010. This acquisition evolved the product to "WebSphere Process Server" to "IBM Business Process Manager" in V8.0.
    Later, when Case joined, the product was called "IBM Business Automation Workflow" in V18.0.0.

    BAW's process side is a heavy user of the database. If your DBA found hints about congestion accessing this table - that's plausible, but it is not obvious how switching case roles relates to it.



    ------------------------------
    Jens Engelke
    ------------------------------

    Original Message


  • 4.  RE: Help needed: Understanding LSW_GRP_GRP_MEM_EXPLODED_XREF usage

    Posted 06/24/26 04:24 AM
    Edited by venkatesh sudhandhiran 06/24/26 04:25 AM

    Many Thanks for the clarification Martin and Jens.



    ------------------------------
    venkatesh sudhandhiran
    ------------------------------

    Original Message


  • 5.  RE: Help needed: Understanding LSW_GRP_GRP_MEM_EXPLODED_XREF usage

    Posted 06/25/26 05:05 AM
    Edited by venkatesh sudhandhiran 06/25/26 05:05 AM

    Hi Martin/Jens,

    yesterday we introduced this index in the production environment. We see a substantial improvement in the response time within the UI while switching roles. The response time has reduced from 20 to 12 seconds.



    ------------------------------
    venkatesh sudhandhiran
    ------------------------------

    Original Message


  • 6.  RE: Help needed: Understanding LSW_GRP_GRP_MEM_EXPLODED_XREF usage

    Posted 06/25/26 05:44 AM

    Thanks for the feedback.

    I passed that on to our Case Management team. It is not intuitive.



    ------------------------------
    Jens Engelke
    ------------------------------

    Original Message


  • 7.  RE: Help needed: Understanding LSW_GRP_GRP_MEM_EXPLODED_XREF usage

    Posted 12 days ago

    Hi Jens,

    after the review with the Case management team, is such index helpful ?

    BR

    Yannick



    ------------------------------
    Yannick Martin
    ------------------------------

    Original Message


  • 8.  RE: Help needed: Understanding LSW_GRP_GRP_MEM_EXPLODED_XREF usage

    Posted 10 days ago

    I am sorry, I expected the case team to respond. 

    In our internal chat, the conclusion was: We are not aware of a scenario where this would help with Case. There are two BAW APIs called upon login to Navigator, but it would be a surprise if that made a huge difference.

    That said, if observation in your exact installation shows congestion on this table, maybe there is something special about your environment - in terms of data distribution or even custom apps calling product APIs.

    I don't think there is any harm in creating that index.



    ------------------------------
    Jens Engelke
    ------------------------------

    Original Message


Related Content