PanatrackerGP has an optional module that allows a user to gather general entered and scanned information and save it to our database. This feature is known as the “Generic Transaction” module.
The generic transaction module allows a user to enter or scan data and save it to the PanatrackerGP database. We facilitate a powerful customized integration through the use of a custom-code component in our software. Through this code, we are able to use the captured data to create custom eConnect data, or call a stored procedure, or perform other unique actions.
The custom development can be performed by our services team. A common approach is for the customized code to call a database stored procedure. The contents of that stored procedure can then be edited by the end-user company, or by a qualified GP partner. Basic configuration of this module is included in the purchase price of the module.
Additional development can be performed by the professional services team. In summary, these changes are made by altering code contained in “MyPlugin.cs” in the Panatracker.Customizations project. The resulting DLL file is loaded and invoked by the generic transaction during the submit process.
Invoking the generic transaction without a planned customization as mentioned above will, by default, result in a configuration error message by default. The simplest way to disable this is to remove (or comment out) a line in the AppSettings.config file on the portal installation. Simply comment-out the line containing the key TransactionPluginAdapter as shown below.
<!– Enable the transaction plugin adapter. –>
<!–add key=”TransactionPluginAdapter” value=”Panatracker.Customizations” / –>
The above change will disable the loading of the sample plug-in and remove the configuration error message.
For more information, contact our support group to arrange to speak with our team.