We've done some customizations along those lines for specific clients.  We haven't built a generic "meeting clone" or "meeting create" capability yet, but we're considering that for a client now.

At this point, neither iBO.NET or SOA ventures into setup areas, so any solution would have to resort to SQL.
--
Bruce Wilson
Director, Technical Services
RSM McGladrey, Inc.

We are just wrapping up a project to integrate a legacy FoxPro applications with iMIS Events and Public View.

Since FoxPro no longer interacts effectively with SQL Server, we copy the critical elements of the event into an SQL based model of the event (using DBConvert and DBSync) and use that to build the iMIS Event. There are some oddities having to do with how functions are managed during setup, but it does not require much setup support from the iMIS Destop.

Our member will be able to register for events on-line with iMIS and then another set of SQL scripts and stored procedures generates the updated model of the event in our SQL clone of the FoxPro event, which is then merged back into the FoxPro application that we still use in the field.

We will be running 15 or 20 events a years using this setup and it is going to deploy a couple of windows batch files for import and eport.

I am still disappointed in the iMIS Events capabilities around managing functions. There really should be some hooks for custom actions on functions. The user class screening is useless for us.

Tom McIntyre Treasurer/Consultant NAWCC