feat(workflow): add WorkflowExecutorService for action dispatch#28
Open
feat(workflow): add WorkflowExecutorService for action dispatch#28
Conversation
Ports the NestJS workflow-executor.service.ts to WordPress. The existing
WorkflowEngine only evaluates conditions; this service parses the JSON
action array stored on workflow.actions and dispatches each entry
against TicketService / AssignmentService.
Action catalog: change_priority, change_status, assign_agent,
set_department, add_tag, remove_tag, add_note, insert_canned_reply.
{{field}} placeholders in canned replies are interpolated via
WorkflowEngine::interpolateVariables.
One failing action does not halt the others (warn-logged when WP_DEBUG
is on). Unknown action types skip. Malformed JSON returns an empty
action list.
Follow-up PR will add the WorkflowRunner (loads matching workflows,
evaluates, writes WorkflowLog) and the hook that bridges
escalated_ticket_created / _replied / etc. into processEvent.
The existing AutomationRunner stays as-is — Automations and Workflows
are distinct product surfaces.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Ports the NestJS
workflow-executor.service.tsto WordPress. The existingWorkflowEngineonly evaluates conditions — this service parses the JSON action array onworkflow.actionsand dispatches each entry toTicketService/AssignmentService.Action catalog:
change_priority,change_status,assign_agent,set_department,add_tag,remove_tag,add_note,insert_canned_reply.{{field}}placeholders in canned replies interpolated viaWorkflowEngine::interpolateVariablesWP_DEBUGis on) — mirrors NestJSAutomationRunnerstays as-is — Automations and Workflows are distinct surfacesScope
Executor only. Follow-up PRs:
WorkflowRunner— loads matching workflows for a trigger event, evaluates conditions, writesWorkflowLogescalated_ticket_created/_replied/ etc. intoprocessEventSplitting keeps the diff reviewable and lets each piece land independently.
Test plan
test (8.1),test (8.2),lint