Issue

Ticket: FOUR-26705

When a Flow Genie is added to a project and viewed from Designer → Recent Assets, the Genie options menu did not show "Copy", even though "Copy" is available on the main Flow Genie listing under the same permissions.

Solution

Aligned Designer Recent Assets with the main Flow Genie list copy behavior:

• Added a "Copy" action to the shared Recent Assets Flow Genie menu (ellipsisMenuActions.js).
• Handled copy-item in the Flow Genie navigation path (flowGenieNavigation.js).
• Added a duplicate-only modal in core (CopyFlowGenieModal.vue), imported by RecentAssetsList.vue, that submits through PUT package-ai/flow_genies/{id}/duplicate.
• Updated the package-ai duplicate endpoint to sync project associations and refresh the user project-assets cache so copied Genies appear correctly in project/recent-asset views.

How To Test

1. Create and add a Flow Genie to a project.
2. Go to Designer.
3. View Recent Assets.
4. Click on Genie options:
   • Ensure the "Copy" action is listed with the same permission rules used elsewhere (create-flow_genies / view-additional-asset-actions).
   • Ensure selecting Copy opens the expected copy flow (name, category, project, description).
   • Ensure submitting creates a new Genie copy successfully via the established duplicate API.
   • Ensure the copied Genie appears as a normal editable asset.
   • Ensure the existing Edit, Add to Project, and Delete actions are not regressed in Recent Assets or the main Flow Genie listing.

ci:package-ai:bugfix/FOUR-26705
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.