diff --git a/docs/developer-guides/debugging-workflows.md b/docs/developer-guides/debugging-workflows.md index 6592f44c..71024e27 100644 --- a/docs/developer-guides/debugging-workflows.md +++ b/docs/developer-guides/debugging-workflows.md @@ -14,7 +14,17 @@ All recent workflow executions are listed on the **Executions > Workflow** page.

Workflow Executions page

-Data on this page can be filtered by searching through workflow name, ID, status, time period, and past days’ executions. Click on the required execution to view the individual execution of a workflow. +Data on this page can be filtered by searching through workflow name, workflow ID, correlation ID, status, time period, and past days’ executions. Click on the required execution to view the individual execution of a workflow. + +In addition, you can also view the workflow execution as code directly from the UI. For this, click on the arrow in the Search button, and choose “**Show as code**”. + +

Show as code option in Workflow Search

+ +This would show the workflow search data in different codes. Currently, you can get them in cURL and Javascript. + +

Workflow search data in code

:::note You can also search for workflow names by inputting partial values with wildcards (*) support. For example, if you want to search for workflow names containing “test”, then search for **test***, and it will display all the workflow definitions with **‘test’** in their name. diff --git a/docs/developer-guides/scheduling-workflows.md b/docs/developer-guides/scheduling-workflows.md index be7b4d07..8e5ccfa8 100644 --- a/docs/developer-guides/scheduling-workflows.md +++ b/docs/developer-guides/scheduling-workflows.md @@ -49,6 +49,15 @@ The following parameters can be used to configure the schedule: Non-admin users can create a schedule only if they have "execute" permission over the workflow to be scheduled. You must also provide “read” permission to list the workflows in the scheduler or workflow definitions. ::: +Once the schedule is created, you can carry out the following actions on the created schedule: + +

Actions that can carried on a Schedule

+ +- **Pause**: Use this option to pause your schedule during situations such as maintenance. You can resume the schedule once you're done. +- **Clone**: Use this option to duplicate your schedule, making it easier to reuse your existing schedule settings. +- **Add/Edit Tags**: Use this option to add a new tag to the scheduler or edit an existing tag in the scheduler. +- **Delete**: Use this option to permanently remove the schedule from the Conductor console. This is a one-time action that cannot be undone. + ## Cron Expression :::tip diff --git a/static/img/actions-on-scheduler.png b/static/img/actions-on-scheduler.png new file mode 100644 index 00000000..671111f2 Binary files /dev/null and b/static/img/actions-on-scheduler.png differ diff --git a/static/img/show-as-code-in-workflow-search.png b/static/img/show-as-code-in-workflow-search.png new file mode 100644 index 00000000..3ca7944d Binary files /dev/null and b/static/img/show-as-code-in-workflow-search.png differ diff --git a/static/img/workflow-search-in-code.png b/static/img/workflow-search-in-code.png new file mode 100644 index 00000000..78e5ca47 Binary files /dev/null and b/static/img/workflow-search-in-code.png differ