Question
Legato Health Technologies
IN
Last activity: 5 Sep 2025 16:36 EDT
Static banner for work object, case lifecycle and work object error messages
Our application is built on Theme Cosmos. Client is expecting in the main work area - the work object header, the lifecycle chevron and the page level errors should be static at the top and not scroll along with the work object details. As per our understanding, this would require CSS/script customization to achieve the desired functionality but wanted to know if there is any such extension in the Cosmos framework which would help for this use case.
So, trying to understand if any such implementation/customization is available across the product for extension?
Note: We did reach out to Pega support team and they confirmed no such extension is available as part of Cosmos framework and it is more constrained with Constellation as well for such a customization. We did explore the possibility of customization using CSS/Javascript but that would complicate any future upgrades to UI and hence, do not want to build a tight dependency on complex customizations.
HCA Healthcare
US
@Siva_Tadikonda there is no out-of-the-box Cosmos or Constellation extension to pin the case header, lifecycle, and page-level errors. The cleanest Cosmos approach is to specialize your case harness and split it into two regions: a top “chrome” region that holds Case Header, lifecycle, and error placeholder, and a scrollable content region for details. Make the top region position: sticky with top: 0, give it a solid background and higher z-index, and wrap the content region in a container with overflow: auto and height set with calc(100vh minus header height). Keep all styling in the Skin using helper classes or tokens, not ad-hoc CSS files, and avoid JavaScript. Reference sections by regions, not fragile DOM selectors, and move the pxAddMessage or error placeholder into the sticky region so errors remain visible. Test on small screens for focus order and keyboard traps. In Constellation, this pattern is not supported and custom CSS is discouraged, so recommend accepting the default scroll model there.