We need to customize the web interface for our client. I am new in iMis, and our version is iMis15.
Seems simply change the master pages under /templates/masterpages/ folder doesn't affect the front-end look. However if I delete public.master, it reports error. If I put an empty public master page there, it still works as before I made the changes.
I notice all pages are inherited from Asi.Bae.Web.xxxx, does that mean we don't have any easy ways to modify the interface?

Has anyone added pages to the iMIS 15 Public View and secured the page by Security Groups or by a person's committee affiliation? We have added several pages to the Public View and have secured them by roles and by having you log in, however, we would like to take it a step further and secure the page by committee affiliation or by the security group.

Has anyone done mapping from Raiser's Edge to iMIS for a Fundraising Conversion? Would you be willing to share any mapping or table layout information you have collected?

Has anyone had any problems with INFORMZ tables being dropped (for unknown reasons) and the iMIS system crashing as a result?

A staff member receives an error and I was curious if anyone else has encountered this issue and what the resolution was.

Error: The customer portfolio is shutting down due to an internal error. Contact System Administrator.

Symptom: If you're seeing random, periodic extremely slow page refreshes on your iMIS app server (full or public view, either one), check the first section of this Howto for the ASP.Net "idle worker process timeout" setting.

The issue is that by default, IIS kills the ASP.Net worker process after 20 minutes of inactivity, causing the next page access to restart the appdomain (leading to that annoying "first hit" slowdown as all the business objects are loaded, iBO initialized, etc).

Does anybody know of any iMIS training courses in the Washington metro area. I've been working with different versions of iMIS for roughly 7-8 yrs, mostly reporting and data entry. I want to become a more in depth user.

When switching to a new website most clients want this to be as "seemless" as possible for the members. We would like to populate the public user username and passwords with the values they already know. eSeries allowed this type of functionality with a process to populate the username and password, however the public view does not. Has anyone developed a process to do this for the public view? I am thinking some webservice or stored proc could be leveraged to cycle thru exsisting passwords in a table so that they coulld be encrypted and then stored correctly in iMIS ready for the public view to use. Open to other thoughts or ideas too....

we would like to eliminate the directory selection from the imis public view. anybody know how to change the top nav bar?

Hi all,

I was wondering if there is an option to enable E-mail redirecting to a single account to prevent Customers in the database from receiving test E-mails?

Thanks.