Skip to content

Feature/FOUR-20298: Implement logic to detect previous Customized Home Screen and redirect new Home Screen #7818

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Dec 16, 2024

Conversation

CarliPinell
Copy link
Contributor

How to Test

Scenario 1: Without Package-dynamic-ui installed

  • Login PM4
  • First Page loaded after Login should be TASKS

Scenario 2: With package-dynamic-ui Installed

Use Case 1: Package Dynamic UI is installed and Default Welcome Screen is enabled by default

  • Login PM4
  • First Page loaded after login should be TASKS instead of DEFAULT WELCOME SCREEN

Use Case 2: Package Dynamic UI is installed and we need to create a Custom Dashboard for Default Screen

  • Login PM4
  • Go to Screens -> Create Display Screen called "CUSTOM DASHBOARD TEST"
  • Add some controls to Display Screen and SAVE
  • Go to Admin -> Customize UI -> Dashboards TAB -> Create new Dashboard and select screen "CUSTOM DASHBOARD TEST"
  • Go to Admin -> Select some user (like Admin) and EDIT
  • In Dynamic UI section, choose "My Dashboard" in Home Page dropdown
  • Then select "CUSTOM DASHBOARD TEST" in Dashboard Dropdown
  • Save changes.
  • Login PM4 with Admin user
  • First Page Loaded after login should be "CUSTOM DASHBOARD TEST"

Related Tickets & Packages

https://processmaker.atlassian.net/browse/FOUR-20298

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.

Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

Copy link
Contributor

@gproly gproly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved

@nolanpro nolanpro merged commit a126adc into epic/FOUR-20297 Dec 16, 2024
8 checks passed
@nolanpro nolanpro deleted the feature/FOUR-20298 branch December 16, 2024 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants