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

Requirements

639 8/31/12 0:00 ESS: My Tickets Sub Page Requirements "ESS: My Tickets Sub Page Requirements

Remove left navigation items (common questions, current issues, my recent updates, etc)

Hide 'Something Broken'

Rename 'Ask a Question' to 'Common Questions' and link to http://its.yale.edu/how-to

Rename 'Status' to 'My Tickets' and link to a new page with client view of open tickets called 'My Tickets' page." Rejected
640 8/31/12 0:00 ESS: Customers should be able to view the status of their tickets "Page should be styled with https://projects.yale.edu/ITS506/Project%20Documents/Forms/AllItems.aspx?RootFolder=https%3a%2f%2fprojects%2eyale%2eedu%2fITS506%2fProject%20Documents%2fSiteSkinningCSSFiles&FolderCTID=0x01200069438C30116D8F4A835D999C65CBD6CE

Add content block that show the the logged in person's Incidents:

Tickets to display: All open Incidents where the logged in person = the client or the contact

Field to output in query:

Short description

Open Date

Ticket Number

Sorted by open date descending order

Add cotent block below the Order Things, Knowledge and My Tickets boxes that show the logged in perso's Requests:

All open Requests where the logged in person = the Requestor or the Client

Fields to output in query:

Requested Item

Open Date

Ticket Number

Approval Status

Stage

Clicking on any ticket in self service should display the ticket in a window styled like this: https://projects.yale.edu/ITS506/Project%20Documents/Forms/AllItems.aspx?RootFolder=https%3a%2f%2fprojects%2eyale%2eedu%2fITS506%2fProject%20Documents%2fSiteSkinningCSSFiles&FolderCTID=0x01200069438C30116D8F4A835D999C65CBD6CE" Rejected
642 9/4/12 0:00 ESS: Enable Help Desk Chat ESS: Enable Help Desk Chat. See attachment for requirements. They are on the last page of the document in RED. Under Review
648 9/7/12 0:00 ESS: Match nav bar blue to production blue style ESS: Match nav bar blue to production blue style Approved/Signed Off
649 9/7/12 0:00 ESS: Hide left nav content blocks on My Preferences Screen ESS: Hide left nav content blocks (example My Requests, My Recent Updates, Current issues) on My Preferences Screen (the screen that allows the user to see their data and change notification preferences). Approved/Signed Off
650 9/7/12 0:00 ESS: New Incident Button should be hidden from the User's view ESS: If the button cannot bring up this New Incident (Something Broken) screen then then button should be hidden from the user's view. Approved/Signed Off
652 9/7/12 0:00 ESS: Make changes to the 'Submit New Incident' screen for clients ESS: Make changes to the 'Submit New Incident' screen for clients. See attached screenshot. When noted with red the text should be removed and replaced with the red text. Approved/Signed Off
653 9/17/12 0:00 ESS: ITS Logo goes to ITS home page ESS: Logo should go to ITS home page its.yale.edu Approved/Signed Off
654 9/17/12 0:00 ESS: New (Incident button) New Incident Button should bring up the Service Catalog Item - Create New Incident (Something Broken) screen. The button can be found on this screen https://yaledevelopment.service-now.com/ess/main.do. See screenshot for a picture of the button. Under Review
655 9/17/12 0:00 ESS: Enhance ticket drill down Clicking on any ticket in self service should display the ticket in a window WHICH HAS The same TOP NAV as the HOME PAGE but styled like this: https://projects.yale.edu/ITS506/Project%20Documents/Forms/AllItems.aspx?RootFolder=https%3a%2f%2fprojects%2eyale%2eedu%2fITS506%2fProject%20Documents%2fSiteSkinningCSSFiles&FolderCTID=0x01200069438C30116D8F4A835D999C65CBD6CE Under Review

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