Release Notes guidelines

This site provides a guide on what to include on the release notes document for the changes you've produced.

All release notes
Please include the following sections:

Contents
This is the index for the document - it will be produced automatically when using Silverlink's template.

Changes introduced

 * This section should include the detail of all changes or features of the window.
 * Each change/feature should be listed as bullet points
 * If the change is result of a support call or change request, please include the reference number if bold and italics
 * Screen shots detailing the change or fix. Please do not add all screen shots at the end as it's not helpful.

Impacts
This section should contain changes on other areas of the system which were caused by the item the release note is about.

Database Changes
This section should contain all structural database changes made as part of your changes.

Local codes
Please include a list of local codes used by the window so administrators can populate each code correctly.

Examples
If the window is brand new, include here screen shots displaying all DWs of the window.

Rebranded windows only
If rebranding a window from the old core style (with the toolbar), please include the following under "Changes introduced", IF APPLICABLE.
 * New look and feel (Rebranding) has been implemented to the .
 * We’ve introduced New & Delete buttons on the right-hand side of each record/area, where applicable.