You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/english/legacy/steps-from-apps.md
+3-9Lines changed: 3 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,8 +20,6 @@ A step from app is made up of three distinct user events:
20
20
21
21
All three events must be handled for a step from app to function.
22
22
23
-
Read more about steps from apps in the [API documentation](/legacy/legacy-steps-from-apps/).
24
-
25
23
---
26
24
27
25
## Creating steps from apps
@@ -55,14 +53,12 @@ app.step(ws);
55
53
56
54
## Adding or editing steps from apps
57
55
58
-
When a builder adds (or later edits) your step in their workflow, your app will receive a [`workflow_step_edit` event](/legacy/legacy-steps-from-apps/legacy-steps-from-apps-workflow_step_edit-payload/). The `edit` callback in your `WorkflowStep` configuration will be run when this event is received.
56
+
When a builder adds (or later edits) your step in their workflow, your app will receive a `workflow_step_edit` event. The `edit` callback in your `WorkflowStep` configuration will be run when this event is received.
59
57
60
-
Whether a builder is adding or editing a step, you need to send them a [step from app configuration modal](/legacy/legacy-steps-from-apps/legacy-steps-from-apps-configuration-view-object). This modal is where step-specific settings are chosen, and it has more restrictions than typical modals—most notably, it cannot include `title`, `submit`, or `close` properties. By default, the configuration modal's `callback_id` will be the same as the step from app.
58
+
Whether a builder is adding or editing a step, you need to send them a step from app configuration modal. This modal is where step-specific settings are chosen, and it has more restrictions than typical modals—most notably, it cannot include `title`, `submit`, or `close` properties. By default, the configuration modal's `callback_id` will be the same as the step from app.
61
59
62
60
Within the `edit` callback, the `configure()` utility can be used to easily open your step's configuration modal by passing in an object with your view's `blocks`. To disable saving the configuration before certain conditions are met, pass in `submit_disabled` with a value of `true`.
63
61
64
-
To learn more about opening configuration modals, [read the documentation](/legacy/legacy-steps-from-apps/).
65
-
66
62
```javascript
67
63
constws=newWorkflowStep('add_task', {
68
64
edit:async ({ ack, step, configure }) => {
@@ -121,8 +117,6 @@ Within the `save` callback, the `update()` method can be used to save the builde
121
117
-`step_name` overrides the default Step name
122
118
-`step_image_url` overrides the default Step image
123
119
124
-
To learn more about how to structure these parameters, [read the documentation](/legacy/legacy-steps-from-apps/legacy-steps-from-apps-workflow_step-object).
125
-
126
120
```javascript
127
121
constws=newWorkflowStep('add_task', {
128
122
edit:async ({ ack, step, configure }) => {},
@@ -159,7 +153,7 @@ const ws = new WorkflowStep('add_task', {
159
153
160
154
## Executing steps from apps
161
155
162
-
When your step from app is executed by an end user, your app will receive a [`workflow_step_execute` event](/legacy/legacy-steps-from-apps/legacy-steps-from-apps-workflow_step-object). The `execute` callback in your `WorkflowStep` configuration will be run when this event is received.
156
+
When your step from app is executed by an end user, your app will receive a `workflow_step_execute` event. The `execute` callback in your `WorkflowStep` configuration will be run when this event is received.
163
157
164
158
Using the `inputs` from the `save` callback, this is where you can make third-party API calls, save information to a database, update the user's Home tab, or decide the outputs that will be available to subsequent steps by mapping values to the `outputs` object.
0 commit comments