Summary
This release includes added functionality from deferred or new requirements affecting multiple modules. One defect fix is also included.
Release Notes
https://yale.service-now.com/sys_attachment.do?sys_id=887d97a82bb22400fde6a4bc59da1576
Documentation
Update Set (Original Names) |
Description |
06/18/2012 - 1 |
Defect 339 - SC task assigned to group notification is being sent to assignment group; should only be sent to queue managers. |
06/13/2012 - 4 |
Requirement 381 - Incident: Change 'knowledge' checkbox to 'Knowledge Candidate' |
06/13/2012 - 10 |
Requirement 386 - add a "save and stay" button to derived task forms
- ensures the context version is just for context (and not forms)
- removes the isAdvancedUI() condition on the form control version
|
06/13/2012 - 11 |
Requirement 386 - add a "save and stay" button to derived task forms
- make sure button is available for inserts
- match behavior of buttons called save & stay
- match behavior of buttons called save & exit
|
06/13/2012 - 5 |
Requirement 386 - add a "save and stay" button to derived task forms |
06/13/2012 - 6 |
Requirement 436 - Incident: Add 'Withdrawn by Client' to incident resolve code |
06/12/2012 - 3 |
Requirement 463 - delegate end date should not have a default value (comment out code in sys_dictionary entry) |
06/13/2012 - 9 |
Requirement 464 - New Call/Request: value in request's Client field should not be overwritten if it's already there from new call
- change onLoad() script for SC item to properly parse & massage redirect parameters
- change Wizard panel for New Call->Request to pass the Contact instead of the Client; there is currently no field for "client" in the only SC request we use, so this field is currently ignored and deprecated in this panel.
|
06/13/2012 - 2 |
Requirement 491 - Request Email Notification: send when SC tasks are assigned to unit/person
- turned on sc_task events business rule
- notification when group assignment occurs
- notification when user assignment occurs (this one has a higher priority)
- (temporary) change to sc_task email template to include description from parent item, since currently there is only one request type. This will have to be changed later; correct fix is for a meaningful description to be added to the sc_task.
|
06/12/2012 - 4 |
Requirement 509 - Categorization: rename some incident component categories.
- change "Backup Devices" to "Storage Device (e.g., Disk/Tape drive)"
- change "Storage Media" to "Storage Media (e.g., Diskett/Tape drive)"
|
06/19/2012 - 1 |
Requirement 523 - CMDB: change asset/device field to "Affected Component" and change type to reference (w/ modifications to requirement):
- We will create a new field called 'Affected Component'. This field will be a reference field instead of a string and therefore searchable.
- No data will be loaded into this new field. We will start from a blank table and allow folks to enter information or pick from items already in the list.
- This field will only show up on new and open tickets.
- The Asset/Device field will turn to read only. It will show up on open and closed tickets. It will not show up on tickets created after the release date.
- Closed tickets will not show this new field. There will be no data changes to closed tickets.
|
06/13/2012 - 7 |
Requirement 523 - CMDB: change asset/device field to "Affected Component" and change type to reference.
- collect existing entries (from all derived tables; i.e. incident, problem, change, request tasks/items replace CI refs)
- add a new table and import a coalesced/clean version of CIs (extends cmdb_ci)
- replace field w/ new reference field (put in Configuration app)
- hide unsupported CMDB items in the Configuration app
...this will be a holdover until CMDB goes live.
|
06/14/2012 - 4 |
Requirement 567 - Knowledge changes in support of the Drupal project
- add kb flag for "Publish to Web?"
- make web taxonomy visible/invisible based on "Publish to Web?"
|
06/07/2012 |
Requirement 567 - Knowledge changes in support of the Drupal project
- add u_audience (Audience) field to kb_knowledge schema and Knowledge form
- add u_web_category (News Category) field to kb_knowledge schema and Knowledge form
- add u_event_date (Event Date) field to kb_knowledge schema and Knowledge form
- make these fields mandatory & visible if Topic is News (via UI Policy)
|
06/11/2012 - 1 |
Requirement 567 - Knowledge changes in support of the Drupal project
- add read-only ACL/role for knowledge table to apply to service accounts pulling KB data
|
06/13/2012 - 8 |
Requirement 577 - permission/hide for impact in SC generic request
- removed from SC incident form
- removed from ESS view of incident form; still accessible/changeable from other views by anyone w/ itil role
|
06/13/2012 - 3 |
Requirement 578 - Incident - add Knowledge Inquiry to Incident Type dropdown
(note: some this was done in another update set but is repeated here to break it out; should be OK due to the type of change).
- add Knowledge Inquiry to Incident Type dropdown
- SC Task->Time Worked: Default the 'User' to the person who is logged into the system
|