Issue & Reproduction Steps

https://processmaker.atlassian.net/wiki/spaces/PM4/pages/3408625665/Cases+vs+Requests+in+the+UI
Introducing the "Cases vs Requests in the UI" feature—a solution designed to provide clear differentiation and improved management of cases and requests within the user interface. By enhancing visibility and categorization, this feature aims to streamline task handling, prioritize workload effectively, and enhance overall user experience.

Solution

Update My Case Tab:

Description: Enhance the functionality and user interface of the "My Cases" tab to provide users with a more intuitive and efficient way to view and manage their requests.

Update My Case in Home Page:

Description: Improve the presentation and accessibility of user cases on the home page, allowing users to quickly view and interact with their pending and completed cases.

Update My Tasks in Home Page:

Description: Enhance the visibility and usability of user tasks on the home page, enabling users to efficiently track and manage their assigned tasks.

Update Breadcrumbs:

Description: Revise the breadcrumb navigation system to provide clearer pathways for users to navigate through different sections of the application, improving overall user experience.

Update the Case Page:

Description: Overhaul the design and functionality of the case page to provide users with a more comprehensive and user-friendly interface for viewing and managing cases.

Update the Task Page Options:

Description: Expand and enhance the options available on the task page, providing users with more functionality and customization options to manage their tasks effectively.

Update My Request Table in Launchpad:

Description: Modify the layout and features of the "My Request" table in the Launchpad interface to improve usability and streamline the request management process.

Update the Message for Empty Cases:

Description: Enhance the messaging displayed when there are no cases to display, providing users with helpful guidance or suggestions for next steps.

Update the Case Title Configuration:

Description: Introduce new configuration options for customizing the appearance and formatting of case titles, allowing users to tailor the presentation of case information to their preferences.

Updates in the UI:

Description: Implement various updates and enhancements to the user interface (UI) across different sections of the application, aiming to improve usability, visual appeal, and overall user experience.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-15539
• https://processmaker.atlassian.net/browse/FOUR-15542
• https://processmaker.atlassian.net/browse/FOUR-15543
• https://processmaker.atlassian.net/browse/FOUR-15544
• https://processmaker.atlassian.net/browse/FOUR-15545
• https://processmaker.atlassian.net/browse/FOUR-15546
• https://processmaker.atlassian.net/browse/FOUR-15547

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

ci:next
ci:deploy
ci:screen-builder:feature/FOUR-15529