diff --git a/docs/_config.yml b/docs/_config.yml index 3e73b9979..63d00e632 100644 --- a/docs/_config.yml +++ b/docs/_config.yml @@ -45,6 +45,7 @@ t: deployments: Deployments contribute: Contributing deprecated: Deprecated + beta: Beta ja-jp: basic: 基本的な概念 advanced: 応用コンセプト @@ -55,6 +56,7 @@ t: reference: リファレンス contribute: 貢献 deprecated: 非推奨 + beta: Beta # Metadata repo_name: bolt-js diff --git a/docs/_functions/listening.md b/docs/_functions/listening.md index 61d48f7c5..6305d10bb 100644 --- a/docs/_functions/listening.md +++ b/docs/_functions/listening.md @@ -9,9 +9,9 @@ order: 3 When your custom function is executed as a step in a workflow, your app will receive a `function_executed` event. The callback provided to the `function()` method will be run when this event is received. -The callback is where you can access `inputs`, make third-party API calls, save information to a database, update the user’s Home tab, or set the output values that will be available to subsequent workflow steps by mapping values to the `outputs` object. +The callback is where you can access `inputs`, make third-party API calls, or set the output values that will be available to subsequent workflow steps by mapping values to the `outputs` object. -Your app must call `complete()` to indicate that the function’s execution was successful, or `fail()` to signal that the function failed to complete. +Your app can call `complete()` to indicate that the function’s execution was successful, or `fail()` to signal that the function failed to complete. To learn more about listening to custom function executions, see the [Slack API documentation](https://api.slack.com/automation/functions/custom-bolt#listener). diff --git a/docs/_includes/sidebar.html b/docs/_includes/sidebar.html index 1cd8a247c..df37df835 100644 --- a/docs/_includes/sidebar.html +++ b/docs/_includes/sidebar.html @@ -66,8 +66,11 @@