Explanation
To configure the Filter Data Table Wizard to keep all invoices with a Total value that is over 10 000 USD, you should choose the following options from the drop-down lists:
Column: Total Operation: > Value: 10000
The reason for choosing these options is to filter the data table based on the condition that the Total column value is greater than 10000. This will keep only the rows that satisfy this condition and remove the rest. You can learn more about the Filter Data Table activity and how to use it from the following sources:
Four Ways to Filter Data Tables in UiPath Studio | UiPath
How to Filter Data Table - Help - UiPath Community Forum
Filter Data table with specific column - UiPath Community Forum

Explanation
The Convert.ToBoolean method converts a specified value to a Boolean value, which can be either True or False. The method can accept different types of values, such as numbers, strings, objects, etc. However, the conversion rules depend on the type of the value. For numbers, the conversion rule is as follows1:
If the value is zero, the method returns False.
If the value is non-zero, the method returns True.
Therefore, if the IntVar variable is an Int32 variable with the value 0, the expression Convert.ToBoolean(IntVar) will return False. The Log Message activity will display the value False in the Output panel after the execution. References: Convert.ToBoolean Method from UiPath documentation.

Explanation
A screenshot of a computer Description automatically generated

The correct sequence for the computation of the signature for client apps that receive Orchestrator requests and need to check their authenticity is:
Retrieve the X-UiPath-Signature HTTP header. This header contains the signature of the request body, encoded in Base64. (UiPath Orchestrator documentation1) To obtain the raw signature bytes, decode the value of the header from Base64. You can use any tool or library that supports Base64 decoding. (UiPath Orchestrator documentation1) Compute the hash using SHA256 and the signing key (UTF-8 encoded). The signing key is a secret value that is shared between Orchestrator and the client app. You can use any tool or library that supports SHA256 hashing. (UiPath Orchestrator documentation1) Compare the computed signature to the value from X-UiPath-Signature HTTP header. If they match, then the request is authentic and has not been tampered with. If they do not match, then the request is invalid and should be rejected. (UiPath Orchestrator documentation1) References:
1: Webhooks - UiPath Orchestrator.

Explanation
The correct sequence of steps the developer needs to perform is:
Step 1 = Create the ProcessPurchaseOrders.xaml file
Step 2 = Open the ProcessPurchaseOrders.xaml file and create the arguments Step 3 = Invoke the ProcessPurchaseOrders.xaml file in the Main.xaml file and click Import Arguments Step 4 = Pass the values of the arguments to/from the variables in the Main.xaml file This sequence will ensure that the developer can create a reusable workflow, invoke it from the main workflow, and pass data between them using arguments.
https://forum.uipath.com/t/import-arguments-in-invoke-workflow-file/1923
https://forum.uipath.com/t/pass-arguments-invoke/132595

Explanation
Triggers are a feature of UiPath Integration Service that allow you to react to key events in third-party systems, such as data updates, insertions, deletions, or custom events. By configuring triggers, you can start your UiPath processes automatically from Orchestrator when these events occur, enabling near real-time automation workflows across different applications. (UiPath Integration Service documentation1) References:
1: Integration Service - Triggers - UiPath Documentation Portal