Unable to Create and View Case ID after Customizing Cosmos UI
Currently we have a requirement to update user portal as per company guidelines. For that we had to customize most of the UI and harness from User Portal. Basically the requirement was to remove the default screen layout from left pane view and just keep portal header and content with clickable link to create case/open case/dashboard etc.
I m facing issue while progressing after new case page does not move forward. keeps loading after entering all fields and click on submit. Also open/view exiting case id using “open work by handle” from section action is not working.
Can you please suggest me how to progress if I have to customize cosmos UI components to achieve this?
Basically client don’t want to see OOTB portal They just want one portal with horizontal header where they can see 3 options.
1. To create case 2. Open case vis report3. To see dashboard charts
I created a header and on click of each link, I am calling ajax container which is configured under user portal to show harness. I customized harness pyCreate, Perform, Review and kept in work class. Also I am using ajax container to display each harness based on click from portal header.
Is that correct approach?
Maantic Technologies Pvt Ltd
US
Hi @AnushaG7
Hope you are doing well.
Your approach of customizing the User Portal using Ajax containers and customized harnesses is generally valid. However, it's important to consider the following:
Impact on OOTB Functionality: Removing the default screen layout can potentially affect the functionality of certain OOTB features.
Maintenance and Updates: Customizations can make it more difficult to apply future Pega updates or upgrades.
Compatibility with Existing Features: Ensure that your customizations do not conflict with any existing portal features that users rely on.
If your client is open to alternative approaches, consider the following:
Create a Custom Dashboard Page: Create a custom dashboard page that contains links to the desired case creation, case opening, and dashboard functionality. This allows you to maintain the Pega User Portal framework while providing a tailored user experience.
Use a Custom Skin: Apply a custom skin to the User Portal that modifies the appearance and layout of the portal without affecting the underlying functionality.
Thanks
Megha
Pegasystems Inc.
CA
I was just wondering if you're creating a case from Dev Studio (directly from the case type), are you facing a similar issue once you submit it? This will help isolate the issue and ensure the portal changes don't impact it.
Are there any errors in the tracer while using open work by handle?
Also, why don't you configure the visible conditions to Never for hiding OOTB widgets/sections in the OOTB portal?