You may have received an email from the MSIX team last week with subject "Changes to the Batch Submitter Accounts for MSIX Data Submission". I just wanted to make sure everyone knows we're aware of the change and have been working with the MSIX team to test our support for the new authentication protocol. There's nothing any of the states need to do. We'll take care of the whole thing.

Back in blog post Enrolled Students filter in Web Search I talked about having added an Enrolled checkbox for filtering student search results. Some time after that we decided to add the additional ability to filter by enrolled within a particular school year. It looks like this:

I mentioned a couple posts ago that we were overhauling flash messages in the web app: Spiffy New Flash Messages! We've now completed that effort. The most noticeable change is that messages will no longer auto-hide and they'll be "stuck" to the top of the window instead of stuck to the top of the page. This means they'll always be visible regardless of how you've scrolled or how long ago they were displayed. So now when a message first display, it might look like this:

I apologize in advance for this post being a little extra geeky. If you prefer the posts with pretty pictures and screenshots to look at, this would be a good time to scroll back through some of the ones you've missed in the past.

There's been a good bit of spiffication (spiffifying?) going on with the web app over the past year or so, and there will be quite a bit more coming up as we find time to fit it in. One of the latest is a rework of all the things that we call "flash" messages throughout the app. Flash messages are the little informational messages that show up at the top of the page to indicate the outcome of some process or request. For example, when you add a new student to a list from the Search page, you used to get a flash message like this:

We've had for a few years in MIS2000 the ability to send out emails to people about events that have happened in the system. The earliest example of this is the "COEs Needing Attention" email that looks like this:

We've used a variety of methods over the years to control which users can edit which enrollments and so forth, but bringing Michigan on over the past year presented some challenges because they already had a lot of processes that worked well for them but weren't in line with anything we'd ever done in MIS2000. One of these was the ability to lock enrollments for an entire school year from editing by anyone. I'm always a little amazed when something like this comes up because I don't think anyone across all these years in all these states has ever asked for that. And yet it seems like something lots of folks would want.

Some of you may have noticed our spiffy new menu in the web app that looks like this:

States have varying needs about which Enrollments should be displayed on the Student page in the web app. There are states who show all enrollments for a student and states that only show the most recent enrollment for a student. Some states have altered which enrollments they display based upon the Role of the User. Just to make clear which part of the app I'm talking about, here's a screenshot:

If you're not already up to speed about how Student Lists work in the web app, you can look at this post for an overview. So thanks to the gals in the Minnesota MEP, we have a new Student List feature - exporting to Excel. You can access it from the Student List menu on the Search page like this: