-
Notifications
You must be signed in to change notification settings - Fork 2
QUA-1254: Update "Flows" userguide as per the latest release. #929
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
QUA-1254: Update "Flows" userguide as per the latest release. #929
Conversation
RafaelOsiro
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
docs/flows/trigger-node.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The text says four options but lists five bullet points (lines 11-19).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RafaelOsiro Done
docs/flows/trigger-node.md
Outdated
| - 30 14 1 * * - Runs at 2:30 PM on the first day of every month. | ||
| - 0 22 * * 6 - Runs at 10:00 PM every Saturday. | ||
|
|
||
| To define a custom schedule, enter the appropriate Cron expression in the "Custom Cron Schedule (UTC)" field before specifying the schedule name. This will allow for precise control over the timing of the operation, ensuring it runs exactly when needed according to your specific requirements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awkward phrasing - before specifying is unclear
before specifying the schedule name
Suggested
Consider removing or clarifying this phrase
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RafaelOsiro Done
docs/flows/trigger-node.md
Outdated
|
|
||
|  | ||
|
|
||
| **Step 2:** Once the filter conditions are set, users must click the **Save** button to finalize the configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Orphan "Step 2" - There's no Step 1 in the Anomaly Detected section
**Step 2:** Once the filter...
Suggested
Once the filter... (remove "Step 2:")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RafaelOsiro Done
docs/flows/trigger-node.md
Outdated
|
|
||
| * Operation Completes. | ||
|
|
||
| * Anomalous Table and File Detection. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inconsistencies in lines 15 vs 108 .
Bullet says Anomalous Table and File Detection. but section header says Anomalous Table and File Detected
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RafaelOsiro Done
docs/flows/move-an-action-node.md
Outdated
|
|
||
| Users can move an existing action node within a flow to change its position and execution order. The action node moves along with its downstream actions, helping reorganize the flow without recreating actions or breaking the flow logic. | ||
|
|
||
| **Step 1:** Click the vertical ellipsis (**⋮**) on the action you want to move, then select the **Move option** from the menu. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider changing Move option to Move for consistency with UI terminology
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RafaelOsiro Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On this file some image paths use ../assets/ while the rest of the codebase uses .././assets/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RafaelOsiro Done! I’ll use the ../assets/ path .

Overview
This PR includes updated screenshots and content as per the latest release.
Key Changes