Skip to content

FOUR-14148 | A Screen Copied from a Project Does Not Appear in the Screen Listing #6234

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 2 commits into from
Feb 16, 2024

Conversation

mcraeteisha
Copy link
Contributor

@mcraeteisha mcraeteisha commented Feb 15, 2024

Issue

Ticket: FOUR-14148

Within a Project, after copying a Screen Asset, the copy of the Screen does not display in the Screen listing.

Solution

Previously, Screens that were created as copies within a project were assigned an asset_type of Screen in the database. This assignment hid the copied Screens from the Screen listing.

When copying a Screen to a Project, the asset_type value is now set to null so that the new Screen appears in the Screen listing.

How to Test

  1. Go to branch observation/FOUR-14148 in processmaker.
  2. Go to branch observation/FOUR-14148 in package-projects.
  3. Go to Designer → Projects. Create a new Project.
  4. Add a Screen to the Project.
  5. Copy the Screen to the Project.
  6. Go to Screens.
  7. Search for your Screen copy in the Screen listing.
    • The copied Screen should be listed among the other Screens that are available in your environment.

ci:next
ci:package-projects:observation/FOUR-14148
ci:deploy

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

@tokensPM
Copy link

QA server K8S was successfully deployed https://ci-133776a05a.engk8s.processmaker.net

@ryancooley ryancooley merged commit 6f3253f into next Feb 16, 2024
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.

4 participants