Add a conditional VI that will log an error that occurs in the engine to the Veristand Log so that more than just the error code can be recovered when an error is encountered in the engine.
Why should this Pull Request be merged?
If no errors occur (which should be the norm), this will skip all added behavior -- otherwise, it should allow for quicker troubleshooting during development or when unexpected error occur from the AIM api or elsewhere.
What testing has been done?
Tried adding an error that would ordinarily say a generic "parameter missing" by including unsupported xml:
The specific part of the xml is now identifiable.
Here's what is shown from Veristand (not really useful) because error handling has not been added yet with custom error codes:
Also tested with no errors, and nothing weird shows up in the logs since case structure is skipped:
What does this Pull Request accomplish?
Add a conditional VI that will log an error that occurs in the engine to the Veristand Log so that more than just the error code can be recovered when an error is encountered in the engine.
Why should this Pull Request be merged?
If no errors occur (which should be the norm), this will skip all added behavior -- otherwise, it should allow for quicker troubleshooting during development or when unexpected error occur from the AIM api or elsewhere.
What testing has been done?
Tried adding an error that would ordinarily say a generic "parameter missing" by including unsupported xml: The specific part of the xml is now identifiable.
Here's what is shown from Veristand (not really useful) because error handling has not been added yet with custom error codes:
Also tested with no errors, and nothing weird shows up in the logs since case structure is skipped: