- Improve the design of the right drawer - Allow to update the trigger of the workflow: the object and the event listened to - Allow to update the selected serverless function that a code action should execute - Change how we determine which workflow version to display in the visualizer. We fetch the selected workflow's data, including whether it has a draft or a published version. If the workflow has a draft version, it gets displayed; otherwise, we display the last published version. - I used the type `WorkflowWithCurrentVersion` to forward the currently edited workflow with its _current_ version embedded across the app. - I created single-responsibility hooks like `useFindWorkflowWithCurrentVersion`, `useFindShowPageWorkflow`, `useUpdateWorkflowVersionTrigger` or `useUpdateWorkflowVersionStep`. - I updated the types for workflow related objects, like `Workflow` and `WorkflowVersion`. See `packages/twenty-front/src/modules/workflow/types/Workflow.ts`. - This introduced the possibility to have `null` values for triggers and steps. I made the according changes in the codebase and in the tests. - I created a utility function to extract both parts of object-event format (`company.created`): `packages/twenty-front/src/modules/workflow/utils/splitWorkflowTriggerEventName.ts`
17 lines
292 B
TypeScript
17 lines
292 B
TypeScript
import { SelectOption } from '@/ui/input/components/Select';
|
|
|
|
export const OBJECT_EVENT_TRIGGERS: Array<SelectOption<string>> = [
|
|
{
|
|
label: 'Created',
|
|
value: 'created',
|
|
},
|
|
{
|
|
label: 'Updated',
|
|
value: 'updated',
|
|
},
|
|
{
|
|
label: 'Deleted',
|
|
value: 'deleted',
|
|
},
|
|
];
|