|
The XORIT control Iteration for IBO .NET (XII abbreviated) is congruent with the web parts methodology of web development.
Controls are placed on a page, such as contact information, billing information, event registration, book orders, basket summary and credit card information.
When the user clicks the button to process the selection, the XII is called, and based upon the controls that are on the page, processes the credit card and saves the information in iMIS using iBO .NET.
XII comes with an executive level design tool, XII Designer. The way XII knows the difference between a contact info control and an event registration control is the ID of the control.
The XII designer generates basic C# ASP .NET web pages, with the controls placed with their correct ID's and procedural calls to the XII. Any iMIS user such as the membership director, can easily
use this XII Designer, it requires no technical skills. The pages can be handed off to a .NET programmer with no skills or knowledge of iMIS to finish the esthetics of the web pages.
XII is a concept that is the happy median between having a rigid application, with custom controls, such as the iMIS Public View, where there are lots of setup pages, but little can
be customized on the actual pages. In order for the admin pages of the iMIS Public View to handle every possible client configuration, it would require an infinite number of options to
be set. XII uses only basic .NET controls. Instead of creating a screen designer, it is intended that the free Microsoft Visual Web Developer 2008 Express Edition be used to set the final
layout of the pages. XII is not a tool for selecting esthetics. It is a tool which allows esthetics to be easily applied.
The XII concept does require a web programmer to make HTML edits and possibly .NET edits to improve the esthetics, but so does the iMIS Public View.
ASP .NET 3.5 AJAX can easily be applied. .NET 3.5 AJAX controls do not replace simple .NET controls, they are added to pages to improve the esthetics of the pages, and are designed to work with simple .NET
controls. There are too many .NET 3.5 AJAX controls to put into the XII Designer. And why should they when they can be easily added using the free Microsoft Visual Web Developer 2008 Express Edition?
This also allows for other rapid application development tools, such as TELERIK to be used to improve esthetics.
Installation is simple. XII is a dll that is placed in your .NET web applications bin folder.
A few app settings are added to the web.config file. The XII Designer is copied to any iMIS executive's workstation for designing the pages.
XII handles all the iBO .NET coding! It also maintains the session state between pages, saving all information on the
XII controls in one session variable in XML format. It also handles sending the confirmation emails.
If changes are required, the whole process of applying the esthetics does not have to be redone. The XII works off the ID of the .NET control, so the XII Designer can regenerate the basic ASP .NET pages,
and the web developer can copy and paste the control to be added to the finished pages. Then esthetics need only be applied to the new control that is added.
If you don't have e-Series or the iMIS Public Views, there is a Lite version! It does not save the transactions into iMIS, as it cannot use iBO, if you
don't have the license fees paid for that. What it does is save all the information in the audit table, and one of the iMIS administrators receives a carbon
copy of the confirmation email. There is a utility to review the audit, where confidential information such as encrypted credit card numbers can be reveiwed.
You will have to key in the transactions into iMIS, but this has the highest return on investment for small associations who cannot affort the e-Series or iMIS Public View
license fees due to low transaction volume.
Can be used in
- iMIS 15 Public View
- iMIS 15.1 e-CM
- ASP .NET applications
- ColdFusion 8 (consuming ASP .NET pages)
- Linux/php – and any other platform with the use of HTML IFRAME’s
|