BPM, Workflow, and Case

BPM, Workflow, and Case

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

 View Only
Expand all | Collapse all

(IBM Case Manager) InBasket display issue in the external IBM Navigator

  • 1.  (IBM Case Manager) InBasket display issue in the external IBM Navigator

    Posted Mon July 01, 2024 10:41 AM

    Hello everyone,

    I have come across a potential bug in InBasket and thought I would share it with you.

    The issue is related to the display in an external navigator of the Case Manager. The possible bug causes the number of cases in an InBasket to be displayed incorrectly. The count is shown below the label. The cause of this is a CSS selector (.icmInbasketContainer .trimLongName .inbasketTabLabel.inbasketTabTrimWC). This selector is used for individual tabs, although they should logically have the same number of characters and width. However, this is not the case.

    In the screenshot, you can see how the error manifests. 

    To fix the error, we have "overridden" this CSS selector in our plugin with the following configuration:

    .icmInbasketContainer .trimLongName .inbasketTabLabel.inbasketTabTrimWC { width: auto !important; text-overflow: ellipsis; }

    This prevents the original configuration

    .icmInbasketContainer .trimLongName .inbasketTabLabel.inbasketTabTrimWC {
    width: 78%; text-overflow: ellipsis; }

    from taking effect. As you can see, the problem is that the label is too wide and the trim tries to reduce the value. However, this causes a display issue. Without the fix, the label VOC has a width of 55.7167, and with the fix, the width is 38.6667 (according to the Firefox Box Model).

    I hope this post helps you, if you encounter this behavior.
    (I think I will open a case in the Support Center)

    Best regards,
    Marcel




    ------------------------------
    Marcel Wölki
    ------------------------------


  • 2.  RE: (IBM Case Manager) InBasket display issue in the external IBM Navigator

    Posted Mon July 08, 2024 12:16 PM

    Hi Marcel,

    Thank you for sharing your observation! Yes, opening a Support case is the best step, then IBM can investigate the potential defect. There have been recent changes in BAW/CP4BA 23.0.2 in this exact area, which might fix your symptom. The Known Issue is not published yet. I will share it when it is published.



    ------------------------------
    Tom Garda
    ------------------------------