New in This Document

Use the New In This Document topic in the following situations:

  • You are republishing an existing RUCKUS document for a new or updated release.
  • You are adding, updating, or deleting features in existing RUCKUS documents.
  • You are adding, updating, or deleting commands to a command reference document.
  • The New in This Document topic should not be used as a Document History table.
  • The New In This Document topic should not be used for Command Reference Guides.
  • If there are no changes in the document, there should be no indication in the table to the effect that “No changes or updates were made to the guide.” Nor should the table show “None” in the rows. Doing so leaves the reader to wonder why the document was rereleased if there were no changes to it. You want to also avoid leaving the table cells blank.
  • For complete New In This Document guidelines see https://commscope.sharepoint.com/:b:/r/sites/ARR_CSS/TechPubs/SDL/Documents/new-in-this-document-guidelines-v1.0.pdf

The New in This Document section normally appears in the About This Document chapter.

The Key Features and Enhancements table is the main feature of the New in This Document section.

The table title includes the release number (and version number if warranted) and the publication date of the document, as shown in the following example.

  • Feature Column

    The Feature column shows the name of each new, updated, or deleted feature in a separate row.

  • Description Column

    The Description column shows a brief description of the new, updated, or deleted feature.

    The Description need not be too lengthy. Begin each description with the notation New, Updated, or Deleted before including a description of the feature or change.

    Note: Keep in mind that the descriptions are likely to be used in the release notes too.

  • Reference Column

    The Reference column shows a cross-reference (live link whenever possible) to the appropriate section in the document.

Key Features and Enhancements in RUCKUS Network Director 4.0.0.47

Feature Description Reference
License requirement for the Copy Zone feature

An active license is now required to access and use Copy Zone capabilities. If the license is expired or not activated, the Copy Zone functionality will be disabled.

Copying Zone Settings from the Inventory Window

Key Features and Enhancements in RUCKUS Network Director 4.0.0.45

Feature Description Reference
Editorial updates and corrections Editorial corrections were made throughout the document. Throughout the guide

Key Features and Enhancements in RUCKUS Network Director 4.0.0.29

Feature Description Reference
RND Upgrade

Updated: RUCKUS Network Director can be upgraded only using encrypted .pkg (package) file.

Upgrading the RUCKUS Network Director Version

Key Features and Enhancements in RUCKUS Network Director 4.0.0.23

Feature Description Reference
Troubleshooting CLI commands

New: This feature allows you to troubleshoot a network issue that occurs during the installation and deployment of RUCKUS Network Director using the CLI.

Troubleshooting using CLI

Minor editorial updates

Minor editorial updates were made throughout the User Guide.

All chapters

Key Features and Enhancements in RUCKUS Network Director 4.0.0.13

Feature Description Reference

Setup recovery email setting before first login

New: When you initially log in, you can use this feature to create your login ID, password, and recovery email. You can also use it to reset your password.

Logging In to the RUCKUS Network Director Admin Portal
Gracefully Shutdown RUCKUS Network Director Using CLI

New: This feature allows you to safely shut down the RND using the CLI.

Gracefully Shutdown RUCKUS Network Director Using CLI

Updates to address defects

Minor updates on content throughout to address defects.

All chapters

Minor editorial updates

Minor editorial updates were made throughout the User Guide.

All chapters

There must be some indication of what has been updated in the released document because there must be some form of change that requires the republication of the document. For documents in which there are no new features or only minor changes, some mention of updates to the guide should be included in the table. For example, some forms of general updates could be listed in the following ways:

  • Editorial updates and corrections
  • Addressing reported defects
  • Unsupported software
  • Unsupported hardware
  • Unsupported feature

The reference to these types of changes could be “Throughout the guide” or “References have been removed throughout the guide.” The goal is to indicate that the change or deletion has occurred throughout the document.