FOUR-9398 - Hide Scripts and DataSources of PM Blocks

[estebangallego]

Issue & Reproduction Steps

When we create a PM Block, we need to hide all the assets linked to the PM Block. At the moment we're only hiding the Screens.

1. Create a Process with the following: Screen, Scripts, DataSouces.
2. Create a Pm Block from the Process.
3. The Scripts and DataSouces created based on the Pm Block are still showing on the page related to each asset.

Solution

• Added Scripts, DataSouces to HideSystemResources.php

How to Test

Follow the reproduction steps and check if the Screen and Scripts related to the PM Block are hidden from the page related to the asset.

Related Tickets & Packages

• Ticket FOUR-9398

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]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

0.0% Coverage
0.0% Duplication