Fixing Loading Issue and Enhancing Parsing for PM Blocks in Process Reloading and Importing

[sanjacornelius]

Issue & Reproduction Steps

This PR effectively resolves a loading issue that occurs during reloading a process when a PM Block is configured. Similarly, it tackles an issue arising when importing a process containing a PM Block.

Previously, when a PM Block was loaded, its node type would erroneously convert to a subprocess, disrupting the configuration of the custom inspector panel for that particular PM Block.

Upon investigation, the problem was traced back to the Modeler's createNode method. The underlying parser in this method was inadvertently defaulting to the processmaker-modeler-call-activity instead of the required custom pm-block node.

Test Case A:

1. Create a PM Block
2. Create a Process
3. Add the PM Block to the process
4. Save the process
5. Reload the process (you may have to reload multiple times)

Test Case B:

1. Create a PM Block
2. Create a Process
3. Add the PM Block to the process
4. Save the process
5. Export the process
6. Reimport the process

Expected behavior:
The PM Block loads the correct node type

Actual behavior:

The PM Block is converted to the subprocess node type

Solution

• Implement the correct parsing mechanism for PM Blocks.

How to Test

Test the steps above

ci:package-pm-blocks:observation/FOUR-8887
.

Related Tickets & Packages

• PM Blocks PR
• Ticket: FOUR-8887 & FOUR-9321

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.