fix: ai flow prompt fix + explanation in ui (#2374)

This commit is contained in:
HugoCasa
2023-10-02 19:40:06 +02:00
committed by GitHub
parent c8543d7ed4
commit 78742e2d3e
2 changed files with 20 additions and 2 deletions

View File

@@ -40,6 +40,24 @@
<ToggleButton value="sequence" label="Sequence" />
<ToggleButton value="trigger" label="Trigger" />
</ToggleButtonGroup>
{#if flowCopilotMode === 'trigger'}
<Alert title="Trigger flow builder">
Build a flow with two scripts, one that regularly checks for changes in an external system
and a second that is executed for each change using a for-loop. For both steps, you can
either choose a script from the hub or generate one from scratch using Windmill AI. The
inputs of the for-loop action are automatically filled in with the ouputs of the trigger
step. At the end of the process, flow inputs are inferred and you just need to fill them
in. <br /><br />
The flow is automatically set to run every 15 minutes when deployed.
</Alert>{:else}
<Alert title="Sequence flow builder">
Build a flow with a sequence of scripts that are executed one after the other. For each
step, you can either choose a script from the hub or generate one from scratch using
Windmill AI. Each step inputs are automatically filled in with the previous step's
outputs. At the end of the process, flow inputs are inferred and you just need to fill
them in.
</Alert>
{/if}
{#each $modulesStore as copilotModule, i}
<div>
{#if i === 1 && $modulesStore[i - 1].type === 'trigger'}
@@ -141,7 +159,7 @@
name="description"
type="text"
placeholder={copilotModule.type === 'trigger'
? 'describe what should trigger your flow'
? 'describe what should trigger your flow e.g. "new slack message"'
: 'describe what this step should do'}
bind:value={copilotModule.description}
on:input={() => {

View File

@@ -79,7 +79,7 @@ const triggerPrompts: {
python3: string
} = {
bun: `I'm building a workflow which is a sequence of script steps. Write the first script in {codeLang} which should check for {description} and return an array.
You can use "const {state_name}: {state_type} = getState(...)" and "setState(...)" from "windmill-client@1" to maintain state across runs.
You can use "const {state_name}: {state_type} = await getState(...)" and "await setState(...)" from "windmill-client@1" to maintain state across runs.
{additionalInformation}`,
python3: `I'm building a workflow which is a sequence of script steps. Write the first script in {codeLang} which should check for {description} and return an array.