What’s new in VIC Runtime application?
We are announcing a new capability in VIC Runtime application, used to run interface flows: the detection of errors raising during the execution of stored procedures.
How will this help you?
The user benefits include improved control of interface execution, providing a reduction in analysis times for behavior induced by errors occurring during the execution of the stored procedure, and the exploitation of the interface log.
What does “Stored procedure” message do?
As you know, the configuration of an interface relies, among other things, on the choice of the business object to use.
For example, the standard business object provided by DELMIA Ortems to manage a Planning environment (PS, PS+SRP, MP, or MP+SRP) is configured to automatically trigger some stored procedures in the database for certain flows: the ‘SUIVI’ stored procedure to process some production follow-up events, ‘CREER_TOUT_PREC’ to create precedence links between phases of linear routings and ‘LANCEMENT’ to insert the work orders into the plan.
In the previous mentioned example (adding/updating/deleting data from a Planning-type environment), when an error was occurring during the execution of a stored procedure in an interface based on VIC Runtime, the error was only written to the JOURNAL table of the Planning environment, but the interface was not reporting the error. Now, the error is detected by VIC Runtime, it is possible to define its severity level and the behavior of the interface when such an error occurs, as it is already possible for other types of error.
How does it work in practice?
The message behaviors are configurable from the VIC Runtime application in the ‘Message settings’ tab:
Resources / Links / References
For more detailed information about the message settings, please refer to VIC Runtime help, and more particularly the following file:
The message default configuration is as follows:
Key violation | WARNING, no Stop |
Master record missing | ERROR, no Stop |
Check violation | ERROR, no Stop |
Field value required | ERROR, no Stop |
Master has detail record. Cannot delete or modify | ERROR, no Stop |
Record/key deleted | ERROR, no Stop |
Others | ERROR, no Stop |
Exception | ERROR (you cannot change that value for exceptions), Stop not selected |
Stored procedure error | OK, no Stop |
Common mistake to avoid:
To see the new error type ‘Stored procedure’ appear, you must have launched a Configuration database update from the VIC Editor application, under Tools > ‘Update version’:
