[Yandex Cloud documentation](../../../../index.md) > [Yandex Serverless Integrations](../../../index.md) > [Step-by-step guides](../../index.md) > Workflows > [Workflow step constructor](index.md) > Integration steps > Managed Service for YDB

# Interacting with document tables in Yandex Managed Service for YDB

{% list tabs %}

- Management console {#console}

  1. When [creating](../workflow/create-constructor.md) a new workflow or [editing](../workflow/update.md) an existing one, in the management console, under **Create workflow** / **Edit workflow**, select `Constructor`. 
  1. From the **Integration steps** section on the left side of the screen, drag the ![ydb-icon](../../../../_assets/ydb-icon.svg) **Managed Service for YDB** element to the relevant workflow location in the constructor window.

      You can drag and drop steps into areas marked by the dotted line in the workflow schema, such as **Add a step**, etc.
  1. In the workflow schema window, click the new **Managed Service for YDB** section to select it.
  1. At the right of the window, on the **Settings** tab.

      1. In the **Step name** field, enter a name for the workflow step.
      1. In the **Database** field, select a database. Only databases created in [Serverless](../../../../ydb/concepts/serverless-and-dedicated.md#serverless) mode are supported.
      1. In the **Path to table** field, specify the path to the table the workflow will interact with. Only [document tables](../../../../ydb/concepts/dynamodb-tables.md) are supported.
      1. Under **Action**, select:

          * `Get` to get the contents of an element in the database; in the **Key** field, specify the value of the DB primary key related to the element in question.
          * `Put` to write data to the table; in the **Attributes** field, specify an associative array of attributes in `key`/`value` format.
          * `Update` to update data in the table. Configure the update options:

              1. In the **Key** field, specify the primary key value of the database element you want to update.
              1. In the **Expression for update** field, specify an expression describing the update of the element's attributes in the database. Learn more about the `UpdateExpression` parameter in [this Yandex Managed Service for YDB guide](../../../../ydb/docapi/api-ref/actions/updateItem.md#parametry).
              1. In the **Attribute values** field, specify the attribute values used in the expression above. Learn more about the `ExpressionAttributeValues` parameter in [this Yandex Managed Service for YDB guide](../../../../ydb/docapi/api-ref/actions/updateItem.md#parametry).

          * `Scan` to search the database. Configure the search parameters:

              1. In the **Key** field, specify the value of the primary key of the database element the search will start from.
              1. In the **Limit** field, set a limit on the maximum number of elements in the list of results.

      1. Optionally, in the **Timeout, ms** field, set the maximum execution time for the current step.
      1. Optionally, to set a custom retry policy for a step, expand the **Retry policy** section and click ![plus](../../../../_assets/console-icons/plus.svg) **Retry policy**. In the form that appears:
         
         1. Optionally, in the **Initial delay, ms** field, set the initial value for a delay between step retries.
         1. Optionally, in the **Backoff rate** field, set the multiplication factor for delay before each step retry.
         1. Optionally, in the **Maximum delay, ms** field, set the value for a maximum delay between step retries.
         1. In the **Errors** field, select the errors for which the step will or will not be retried.
         
             For detailed information about possible errors, see [this section](../../../concepts/workflows/execution.md#errors).
         1. Optionally, in the **Maximum number of retries** field, set the maximum number of step retry attempts.
         1. In the **Error selection mode** field, select:
         
             * `INCLUDE`: Retry executing a step when errors specified in the **Errors** field occur.
             * `EXCLUDE`: To retry executing the step on any errors other than those specified in the **Errors** field.
         
         If you want to delete a retry policy you created for the step earlier, click ![ellipsis](../../../../_assets/console-icons/ellipsis.svg) and select **Delete** in the **Retry policy** row.
         
         If no custom retry policy is configured for a step, the retry policy [set for the whole workflow](setup-restart-policy.md) will apply.
  1. Optionally, navigate to the **Input** tab and set a [jq template](../../../concepts/workflows/templating.md) to filter the [workflow state](../../../concepts/workflows/workflow.md#state) fed into the step.
  1. Optionally, navigate to the **Output** tab and set a [jq template](../../../concepts/workflows/templating.md) to filter the step outputs added into the [workflow state](../../../concepts/workflows/workflow.md#state).
  1. Optionally, [add](setup-catch-rule.md) an [error transition rule](../../../concepts/workflows/yawl/index.md#catchrule) for the step you are creating to handle errors you may get during this step.

{% endlist %}

## Useful links {#see-also}

* [YaWL specification](../../../concepts/workflows/yawl/integration/ydbdocument.md)
* [Creating a workflow using the constructor](../workflow/create-constructor.md)
* [Updating a workflow](../workflow/update.md)