Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
The command results are written to the log document.
If you enable trace logging you can see all the output.
It's any output from the command-line.
We cannot capture the return code based on how the programs are called because we decided the returned output stream is more important.
The returned text is the stdout. If you redirect the stderr via 2>&1 you will also be able to capture the error output. And it makes sense to redirect the error output as well.
The field name the stream is returned is: "ret_CommandResult"
In case the result is valid JSON the result is parsed in fields starting with "retJSON_Command..."
I hope this helps?
By the way there is a new GitHub repository for exactly this type of questions:
We really want to hear from the field what customers and partners and building.
There is currently no command-line example.
Most integrations don't require command-line integration.
We build one for AWS Route 53 DNS integration. But it's not published yet.
And we would like to understand what your use case for command-line integration is.