Description of features / status

We have achieved sign-off on the current revision of ESS Portal.

This version displays:

• a header, which contains
  • a top-level menu bar, with ITS icon that links to its.yale.edu
  • related buttons, which include Real Name, ability to logout
  • other buttons which allow changing font size are hidden with CSS
• a menu bar, which contains
  • My Tickets, which links to the default landing page view
  • My Preferences, which links to Portal - Profile, and allows modifying name and mail settings if they drill one more step in
  • How To, which links to its.yale.edu/how-to

• the body of the landing page contains
  • a CSS-ified Tasks view, which shows three columns
    • Short Description
    • Date (which is date opened)
    • Number (includes INCxxxxxx and RITMxxxxxx)

There is also a pretty big problem:

• the body of the landing page, with the Tasks view will jump out of the nav frame set if you drill down to an individual ticket. Your only nav option at that point is to enter a URL in the browser bar, or to use Back feature in the browser.

Another possibility for landing page

Alternate ways to do this:

• there is already an iframe-ified version of the landing page, which displays the same Task data, and also keeps the Nav frame, such that the user can continually act the way they would expect.
• this page is accessible at: https://yaledevelopment.service-now.com/ess/iframed_tasks2.do

But this comes with the problem that the CSS is not applying to the Tasks body frame. I don't know whether it merely needs to be customized by Ken, or whether there's a deeper problem. If you view source, Ken's CSS seems to be getting sourced, but not having an effect on the elements as we have come to expect with the older views.

Associated update sets

In an ideal world, I would have a one-to-one mapping of System Updates to requirements. Instead, I was learning SN development by doing. It is also the case that we had multiple revisions to requirements, and as I got closer to what we asked for, we changed the way we wanted the product to behave.

2012/09/14 - 1
2012/09/13 - 1
2012/09/11 - 2
2012/09/11 - 1
2012/09/10 - 2
2012/09/10 - 1
2012/09/09 - 1
2012/09/07 - 3
2012/09/06 - 3
2012/09/07 - 1
2012/09/06 - 1
2012/09/05 - 1
2012/09/04 - 4
2012/09/04 - 1
2012/08/31 - 3
2012/08/30 - 1

Older versions

And here are the older views:

• https://yaledevelopment.service-now.com/ess/main.do
• https://yaledevelopment.service-now.com/ess/incidents2.do
• https://yaledevelopment.service-now.com/ess/requests2.do

Here are some screenshots

The landing page

The preferences page

Current state of iframed_tasks2.do