Debugging RPC

In the case that you are using RPC inside your app, you might need to debug it. After this article, you will know how to debug RPCs on Make and be an ace of it!

Location of debug tool in RPC

The RPC debug tool can be found by following:

1. Go to Custom apps tab.

2. Select your custom app from the list.

3. Go to the Remore Procedures tab inside the custom app.

4. Select an RPC you want to debug.

5. Click Test RPC.

Location of the "Test PRC" button inside every RPC

Navigation inside RPC

Compare the tabs below to understand how things work inside RPC on Make.

By default after creating a new RPC, you have a template of the communication code, which should be modified based on your needs.

Inside RPC, you can use the relative path and the full form of the URL. However, we advise you to stick to the relative path across all your RPCs and Modules. A relative path is added to the "baseUrl", that you are supposed to specify inside the App Base (Located: Your App -> Base tab).

Default Communication

Default RPC communication template.

Customized Communication

Example of modified RPC communication template.

Also, there is Parameters tab, which by default is empty. Here you can add any parameter needed. In the same way, you can also do it in the Mappable parameters from a module.

Default Parameters

By default RPC is created without any paramaters.

Customized Parameters

Example of RPC with parameters.

Any parameter created inside an RPC will be available only for RPC debugging. It will not be visible inside your modules or inside scenarios.

To preview and test parameters, click on the Test RPC button.

Default Preview

RPC debug tool without parameters.

Customized Preview with Parameters

RPC debug tool with parameters.

RPC debug tool

RPC debug tool works the same way modules do.

1. Specify the connection and other fields (i.e. parameters) if needed.

2. Click the Test button.

3. The call, which you specified before in the RPC communication, will be executed.

Notice that you will see the output which you specified in the RPC communication.

If you specified output as "label" and "value"(with the purpose of using it inside a Select parameter), do not expect to see the full server response there.

Sometimes you might get an empty array as a response. If that's not the response that you expected. Check that you correctly specified the path to the object, which you use inside iterate.

Input

Output

Communication code