Skip to main content

Errors in Web Services

How should linked actions be executed and errors handled in Web Services?

H
Written by Huzayfah Patel

How Should Linked Actions Be Executed and Errors Handled in Web Services?

Linked actions in Web Services play a crucial role in automating processes within the Access Legal Proclaim application. This article outlines the correct execution format for linked actions and provides guidance on handling errors effectively.

Overview of Linked Actions in Web Services

Linked actions are predefined workflows or operations that can be triggered programmatically via Web Services. They are often used to perform specific tasks on a case or record within the system.

Execution Format Requirements

When invoking a linked action using the proRunLinkedAction method, it is essential to follow a specific format to ensure the action executes correctly. The required steps are:

  1. Use the OPEN(WebCaseNo, "") command to open the case specified by the WebCaseNo parameter.

  2. Execute the logic defined within the linked action.

  3. Conclude with the UPDATE(WebCaseNo, "") command to save changes to the case.

This sequence ensures that the linked action operates on the correct case number passed in the Web Service call.

Error Handling and Limitations

Linked actions have certain limitations when it comes to error handling:

  • Custom Errors or Status Codes: Linked actions cannot return custom errors or status codes directly to Web Services. This limitation requires alternative approaches to manage error scenarios.

  • Workaround for Error Handling: To handle potential issues such as case locks, it is recommended to call the proCaseLockStatus method before executing proRunLinkedAction. This allows you to check for conditions like case locks and address them on the client side.

Best Practices for Debugging and Error Resolution

To ensure smooth execution and error handling of linked actions in Web Services, follow these best practices:

  • Always adhere to the required execution format (OPEN, execute logic, UPDATE) to avoid runtime errors.

  • Use pre-checks like proCaseLockStatus to identify and resolve potential issues before invoking linked actions.

  • Log Web Service calls and responses to facilitate debugging and identify recurring issues.

By following these guidelines, you can maximize the reliability and efficiency of linked actions in your Web Services integrations.


For further assistance, consult the Access Legal Proclaim documentation or contact support.

Did this answer your question?