Hello Tessiturians,
I was wondering if anyone has created a service interceptor that has pop-up messaging. Here is the situation, we have a few patrons who have past due accounts and we do not them to be able to make future purchases until their past due amount is fulfilled. We are in a consortium, so making the account inactive is not an option as this would affect all consortium members as well. I was chatting with our programmer and he had made mention of the possibility of having an interceptor that would pop up with information about this type of situation for that account. Ultimately what would be most awesome would be messaging that pulls directly from notes on the research tab. I could create both a constituency and a notes reason that are an exact match.
I guess what I'm wondering is - is anyone out there doing anything like this?
Chris
Hello Chris,
There is the ability in an interceptor to throw a PluginValidationException with a message and a code. Tessitura will log the error and then display this as a message box in the application. Throwing an exception and getting the message box I believe only works with adding or editing data , not selecting. The PluginPlacement setting also matters as well, I beleive this message box displays only with a PluginPlacement set to PRE. Since the PluginValidationExceptions are intended as a means to stop an operation from occuring.
Jon
Hi Jon,
Good day.
we have some plugin code using this PluginValidationException but it does not work any more since we upgrade to v12.5.
in the log file, it recorded this.
2015-09-21 16:26:06.8387|Error|Error: Failed to create an instance of the plugin type 'MTC_REST.TessituraPlugins.ConstituentService.DupEmailLoginPrevention'. Please review the logs for details.2015-09-21 16:26:06.8856|Error|Exception has been thrown by the target of an invocation. at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters) at Tessitura.Services.Common.Interceptor.PluginEngine.ExecutePlugin(PluginData pluginData, PluginConfig pluginConfig)This email address already exists in account 154578. Please review whether this customer has a duplicate account, or if this email is assigned to the wrong person. Duplicate emails are not allowed except in limited circumstances (please ask the Ticketing Manager if you have a reason why a duplicate should exist in this circumstance). at MTC_REST.TessituraPlugins.ConstituentService.DupEmailLoginPrevention.Operation(PluginData input)
The blue part should be display at client message box.
now it kept in logs only.
Are there any new method be used to replace the client message box function?
have fun.
Ben
Hello Ben,
The I would suggest opening a ticket on TASK they should be able to help you with troubling shooting the cause.
In case anyone stumbles across this thread trying to troubleshoot issues with PluginValidationException, we've lodged a TASK ticket for a very similar issue to the one that Ben is seeing. I don't think it's appearing in the Tessitura known defects list yet, but will be there soon as reference #71283.
The issue is that plugins fired from the General Tab are unable to return Validation Exception messages to the application and instead throw errors. There is no fix at this point.
In our experience the issue is only occurring when editing an existing record, but works fine when a new record is being created.
CheersSarah