Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Update Set (Original Names)

Description

2013/04/04 - 1

Defect 469 - Incident: reopen notification not received by mgr, team leads

 

2013/04/04 - 1

Defect 469 - Incident: reopen notification not received by mgr, team leads

2013/04/06 - 1

Defect 420 - Incident: priority 1 incident scroller on IT homepage has wrong query - invalid. Must escape ampersand as well.

 

2013/04/06 - 1

Defect 420 - Incident: priority 1 incident scroller on IT homepage has wrong query - invalid. Must escape ampersand as well.

2013/04/04 - 2

START 77 - PTAEO point backend SOAP at webmethods PRODUCTION instance.

2013/04/03 - 2

Defect 465 - Request: SSG Enhancement Request fixes: limit ROM field to 10 chars, put client team field after dept. field.

2013/04/01 - 4

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values, some incidents with illegal priority (6,7)
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?
Also, some incidents have (unrelated) priority statements in the body which are being parsed by the inbound action - this should be disabled."

2013/04/01 - 3

"Defect 459 - Request: ""Propose a New Service Request Type"" request is not rendering fields properly in the RITM/SC Task

  • added all fields to the task carryover lists"

2013/04/01 - 2

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?

https://yaledevelopment.service-now.com/sc_task_list.do?sysparm_query=state!%3D3%5EORstate%3DNULL%5Estate!%3D1%5EORstate%3DNULL%5Estate!%3D2%5EORstate%3DNULL

Thanks"

2013/03/26 - 1

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?

https://yaledevelopment.service-now.com/sc_task_list.do?sysparm_query=state!%3D3%5EORstate%3DNULL%5Estate!%3D1%5EORstate%3DNULL%5Estate!%3D2%5EORstate%3DNULL

Thanks"

2013/04/04 - 2

START 77 - PTAEO point backend SOAP at webmethods PRODUCTION instance.

2013/04/03 - 2

Defect 465 - Request: SSG Enhancement Request fixes: limit ROM field to 10 chars, put client team field after dept. field.

2013/04/01 - 4

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values, some incidents with illegal priority (6,7)
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?
Also, some incidents have (unrelated) priority statements in the body which are being parsed by the inbound action - this should be disabled."

2013/04/01 - 3

"Defect 459 - Request: ""Propose a New Service Request Type"" request is not rendering fields properly in the RITM/SC Task

  • added all fields to the task carryover lists"

2013/04/01 - 2

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?

https://yaledevelopment.service-now.com/sc_task_list.do?sysparm_query=state!%3D3%5EORstate%3DNULL%5Estate!%3D1%5EORstate%3DNULL%5Estate!%3D2%5EORstate%3DNULL

Thanks"

2013/03/26 - 1

"Defect 434 - FRU0013980 - Request: some SC Tasks with 'illegal' state values
One or more workflows or business rules have a bug whereby some SC Tasks settle at a state of (4) or (-5). I don't yet know how to reproduce, but I'm sure it's just a programming error somewhere. Could someone please investigate?

https://yaledevelopment.service-now.com/sc_task_list.do?sysparm_query=state!%3D3%5EORstate%3DNULL%5Estate!%3D1%5EORstate%3DNULL%5Estate!%3D2%5EORstate%3DNULL

Thanks"

...