Skip to content
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

FOUR-10236 | Ellipsis Menu Action: Enhance Assign Asset Modal Information #5268

Merged
merged 4 commits into from Sep 7, 2023

Conversation

mcraeteisha
Copy link
Contributor

@mcraeteisha mcraeteisha commented Sep 6, 2023

Issue

Ticket: FOUR-10236

In the Assign Asset Modal, we need to provide users with additional information for better context and usability:

  1. Project Name: Display the name of the project to which the asset is being added. This ensures users can easily identify the destination project.
  2. Copy Asset Button: Include a "Copy Asset" button within the modal. This button empowers users to duplicate the selected asset and add it to the project efficiently.

How to Test

  1. Go to branch task/FOUR-10236 in processmaker.
  2. Go to branch next in package-projects. Install the package.
  3. Go to branch task/FOUR-10236 in package-decision-engine. Install the package.
  4. Go to branch task/FOUR-10236 in package-data-sources. Install the package.
  5. Go Designer → Processes. Have a process created. From the Ellipsis Menu, select 'Add to Project'.
    • Note that the Add to Project language has been updated from 'Assign to Project'.
    • Note that the folder icon has been udpated to a folder with a plus sign.
    • Note that the Add to Project modal now includes the asset type and asset name.
    • Note that the Add to Project modal now includes an option to copy the asset, which has a tooltip when hovered over.
      - The functionality to copy the asset has not yet been added.
  6. Repeat Step 5 for Scripts, Screens, Data Sources, and Decision Tables.

ci:next

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.

@processmaker-sonarqube
Copy link

@ryancooley ryancooley merged commit 2f3e1c4 into next Sep 7, 2023
10 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants