There are some steps a robotic process must take to successfully start, execute, and complete on a resource. These default steps often require communication with the Appian RPA server. The Server low-code module contains methods that enable a robotic process's communication with the server, whether to retrieve information or send it to help a developer understand what's happening and when.
This page discusses the methods contained in the Server low-code module, which provides an easier and more robust development experience.
Developers who feel more comfortable working in the robotic process's code can use Java methods to configure server communication actions. These methods are contained in the Client module and can be found in the com.novayre.jidoka.client.api.IJidokaServer and com.novayre.jidoka.client.api.JUnitJidokaServer interfaces.
The methods contained in the Server module group are helpful throughout a robotic process execution. As an execution completes, a robotic process may have to send resulting files to the server. These methods are often used in the robotic process's clean up workflow to help reset the resource. Use the communication methods to send messages to the execution log throughout the robotic process, which may be helpful for debugging.
The Server low-code module contains these methods:
text. You can also enter the parameter name using plain text, a robotic process variable, or an expression. The files can be downloaded in the Output column on the List of executions page.
text. Enter a path using plain text, a robotic process variable, or an expression. The files can be downloaded in the Output column on the List of executions page.
As mentioned above, a robotic process may need to send a message to the server as part of its clean up workflow. However, you can use these methods at any time in the robotic process. The type of message you send depends on the type of event. For example, you may want to build logic into your robotic process to send an ERROR message when a particular action isn't completed successfully, but not send a message when it proceeds as expected.
To send a message to the execution log:
if()statement in the expression. Note that the expression changes the message content, not the message type. To use a different message type, see below.
To send a different type of message (Info vs. Error, for example) based on a condition in your robotic process, integrate a conditional action into the workflow:
To write an expression for the condition, open the Appian Services module and click Evaluate expression. In this example, the expression simply evaluates if a robotic process variable exists. If it is null, we want to send an error message to the console:
1 2 3 if(isnull(pv!stockPrice), "error", "success")
Name the connections so they match the possible outcomes exactly:
On This Page