3548751be2
- Create a workflow version when the user visits an empty workflow. - If the trigger is not defined yet and the user selects either the standard object type or the event type first, we automatically select the first option of the other value. Indeed, every state update is automatically saved on the backend and we need both standard object and event types to save the event name. - Introduces a change in the backend. I removed the assertions that throw when a workflow version is not complete, that is, when it doesn't have a defined trigger, which is the case when scaffolding a new workflow with a first empty workflow version. - We should keep validating the workflow versions, at least when we publish them. That should be done in a second step.
23 lines
642 B
TypeScript
23 lines
642 B
TypeScript
import { WorkflowVersion } from '@/workflow/types/Workflow';
|
|
import { WorkflowDiagram } from '@/workflow/types/WorkflowDiagram';
|
|
import { generateWorkflowDiagram } from '@/workflow/utils/generateWorkflowDiagram';
|
|
import { isDefined } from 'twenty-ui';
|
|
|
|
const EMPTY_DIAGRAM: WorkflowDiagram = {
|
|
nodes: [],
|
|
edges: [],
|
|
};
|
|
|
|
export const getWorkflowVersionDiagram = (
|
|
workflowVersion: WorkflowVersion | undefined,
|
|
): WorkflowDiagram => {
|
|
if (!isDefined(workflowVersion)) {
|
|
return EMPTY_DIAGRAM;
|
|
}
|
|
|
|
return generateWorkflowDiagram({
|
|
trigger: workflowVersion.trigger ?? undefined,
|
|
steps: workflowVersion.steps ?? [],
|
|
});
|
|
};
|