Service Failure Simulator - Overview - OutSystems

Login to Download

Traditional Web

5.0

(2 ratings)

0 reviews

6

2

Created on 11 March 2018

Login to Follow

Details

Developer Utility to trigger different exceptions while performing a Server Action call. Very useful for testing integrations with third party API's. To enable set the Site variable Simulation to true (default value).

Utility to test your exception dandling code. All you need to do is add a call to the action ProxyFailureSimulation in the Server Action you want to test and add the Proxy Instruction to trigger a runtime exception.

What’s new (2.0.1)

Target attribute is now mandatory for a Proxy Instruction.

Reviews (0)

Category

Applications, Developer Tools

Tags

Exception Handling

Support Options

This component is not supported by OutSystems. You may use the discussion forums to leave suggestions or obtain best-effort support from the community, including from Adrian who created this component.

Dependencies

Lisbon Template

Requirements

Platform:

10.0.0.402

Database:

All

Stack:

All

Team

Component Consumers

No consumers yet.

Weekly Downloads

Related Components

Discovery is a visual tool to help analyze, measure and understand how to improve your factory architecture

OutSystems Now brings your OutSystems experience to any device.

The component to help you keep your database neat and tidy.

More from Adrian

This application provides a simple yet aggressive removal of the massive amounts of useless data on your Cloud Personal Environment. It may work on non cloud environments but has not been tested outside a Cloud Personal Environment. I used LogsManagement and DBCleaner for inspiration, many thanks to Carlos Alfaro the author of LogsManagement (http://www.outsystems.com/forge/component/1195/logs-management/) and to Acácio Porta Nova the author of DBCleaner (http://www.outsystems.com/forge/423/)

An Enterprise Glossary Application with Specifications Management capabilities, advanced import/export capabilities and synchronization to/from Enterprise Architect and JIRA.

A mobile app with offline cache using REST services. Local app cache is used when: - there is no connection to the server; - there is an error retrieving information from the server; Server-side cache is used when: - there is a timeout retrieving information via REST - there is an error retrieving information via REST - call throttling dictates cache should be used instead of the REST api. Server cache throttling allows one call every 15 seconds. Example on how to send error codes via REST and handle REST errors.