Adalennis opened a new issue, #8970: URL: https://github.com/apache/hop/issues/8970
### What needs to happen? Each action page should say what the action passes on as its result, so it is clear which hop the workflow follows and what the next action receives. The general explanation of action results is in #2591 (workflow/action-results.adoc); this issue is about the part that is specific to each action. Proposal: a short "Result" section on every action page, with the same table everywhere: | Result | Value | |---|---| | True | When the action succeeds | | False | When it fails, and what the error count holds | | Result files | What it adds to the result files, and which option controls it | | Result rows | What it does with the result rows | plus a row for the metrics on the actions that set them (lines read or written, files retrieved, exit status, ...). What the code tells us so far, for the 85 actions: - 25 add result files, 6 set result rows, 20 set metrics. - 4 actions don't evaluate a result, so only their unconditional hops are followed: Start, Dummy, Delete execution information and Snowflake warehouse manager. Their table says so instead of True/False. - 5 actions keep the error count of the previous action instead of starting from 0: Abort, JavaScript, Join, Write to log and Wait for. - When an action returns true or false has to be read in each action's `execute()` method. Given the number of pages, this would go in batches, starting with a few actions (Pipeline, Workflow, Copy files, Mail, Simple evaluation, SFTP) to agree on the format before doing the rest. ### Issue Priority Priority: 3 ### Issue Component Component: Documentation -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
