Contents

Helpful Links

• Release Control 6.2.1 Release Notes
• November 2017 Plugins Release Notes
• June 2017 Plugins Release Notes
• August/November 2016 Plugins Readme
• ALM Connector 6.1.4 Release Notes
• Documentation Center

Supported Configurations

Although plugin support is typically backward compatible, due to architecture changes, plugin versions released in June 2017 will work only with Release Control 6.2 or later and plugin versions released in December 2017 will work only with Release Control 6.2.1 or later.

Earlier versions of the plugins will not work with Release Control 6.2 or later without manual updates.

Detailed information about supported platforms and software configuration is available in the Supported Platform List.

Third-party Tools

For more information regarding third-party software copyrights and license information, see the Attribution Report.

Enhancements

The following enhancements are included in the latest plugin releases:

• Enhanced ServiceNow Plugin

  The ServiceNow plugin has the following enhancements:

  • Base Configuration Options
    • Custom Request Header: If ServiceNow is setup behind a firewall or proxy that requires specific information be passed in the request header for authentication, you can now enter the code given to you by the ServiceNow administrator.
    • API URL Overrides: For some versions of ServiceNow, you may need to change the default API locations. You can now configure the location for the base API, the Dictionary table, Choice table, DB Object table, Properties table, and User table.
  • Action Configuration Options
    • Reference Fields: You can now use reference fields using the format referenceField.fieldName, such as cmdb_ci.name to get the Name field of the related Configuration Item. Reference fields can be used in the Fields for Check Item list. You must specify the reference field before adding a specific field name inside the table, otherwise the field will not be displayed.
    • Fields for Update Item: You can specify a list of fields to be used in an Update Item task. Supported field types are text, number, choice, boolean, date, and user.
    • Fields for Check Item: You can specify a list of fields to be used in a Check Item task. Supported field types are text, number, choices, boolean, date, user, and reference. When accessing a field within a reference table, only text, number, choice, and boolean fields are supported.

    • Action Filter: You can specify a list to control the list of actions that are available when creating a ServiceNow deployment task.

  • Item Configuration Options
    • Textual Search: There is now a check box to enable searching for existing ServiceNow objects using Text Fields for Search. In Text Fields for Search you specify a comma-separated list of fields that can be searched as text. Supported field types are text, number, choice, boolean, date, user, and reference. When accessing a field within a reference table, only text fields are supported.
    • Category Search: There is now a check box to enable one choice field to be used for searching for existing ServiceNow objects using Category Field for Search. In Category Field for Search you specify a single field to search.
    • Field Filter: There is now a check box to enable additional search options for more field types. The list of fields searched are from Title Field, Name Field, Description Field, and Custom Fields. Supported field types are text, number, choice, boolean, date, user, and reference. This is not supported when accessing fields within a reference table.
• Enhanced ChangeMan ZMF Plugin

  The ChangeMan ZMF plugin has the following enhancements:

  • A Department Filter text field for searching ChangeMan ZMF Packages on the deployment unit widget
  • Configuration override features to auto-add values to the Department Filter field

  • A read-only Deployment Filter option on plugin configuration to prevent users from changing the value on the deployment unit widget

• Enhanced SBM Plugin

  The SBM plugin has the following enhancements:

  • New Create Item action

    Due to limitations with the Create Item actions it was not possible to dynamically resolve fields of the specified process-app and to display them on the task form. To fix this issue and introduce new features a new Create Item action has been introduced. For compatibility with existing tasks, the old action has been renamed Create Item (deprecated).

  • A new action that dynamically gets all the fields in the target process-app and displays them on the task form using SBM widgets for these field types:
    • Binary/Trinary (checkbox\drop-down controls)
    • Date/Time (calendar\time picker widgets supported)
    • Multi-Group (check-boxes and searchable forms are supported)
    • Multi-Relational (check-boxes and searchable forms are supported)
    • Multi-Selection (check-boxes and searchable forms are supported)
    • Multi-User (check-boxes and searchable forms are supported)
    • Numeric
    • Single Relational (check-boxes and searchable forms are supported)
    • Single Selection (searchable forms are supported)
    • Text (password type is not supported)
    • User (searchable forms are supported)
  • Enforcing supported process-app fields

    Fields marked as required in a process-app must be completed when creating a task.

  • Hiding the project field

    If the Project field on a task form contains a single value, administrators can hide the list by selecting Hide Project Selection Field in Action configurations.

Manually Upgrading Plugins

After you upgrade to Release Control version 6.2.2 from version 6.2 or later, or after you manually install the latest plugins in Release Control version 6.2 or later, the earlier versions of plugins are retained. You can manually upgrade plugin instances at your convenience.

When new plugin versions are available, an alert appears at the top right of the Release Control Administration UI.

Click the alert icon and then click Show to view the list of plugins that require upgrade.

Post Upgrade Activities for Plugins

You must do the following after upgrading to the latest versions of the plugins, especially if upgrading from a version earlier than version 6.2.

1. If you have existing deployment tasks for the upgraded plugins, in each release package in the Deployment Tasks tab, edit and save the deployment tasks to populate them with the provider data that was stored differently in the earlier release.
2. If you have plugin configurations that were created using the August 2016 version of the CA Nolio (now CA Release Automation) plugin, you must change the notification URL or use polling only. For details, see the plugin documentation on the Documentation Center.
3. If you have existing requests or deployment units for the upgraded plugins, in each release package in the Requests or Deployment Units tab, click Reload Request Data or Reload Deployment Unit Data respectively to pick up any new data available due to plugin changes.

Related Upgrades

You may need to upgrade other related products when you upgrade to RLC 6.2.2 and the latest plugins.

• When you upgrade the ChangeMan ZMF plugin from a plugin version released earlier than June 2017, you must upgrade ALM Connector (formerly known as ZMF Connector) to version 6.1.3 or later. For upgrade instructions, see the ALM Connector Release Notes on the Documentation Center.

Troubleshooting Plugin Upgrades

After upgrading, you may encounter one of the following issues:

• Custom columns you added are no longer in the table

  The columns in the Deployment Units and Requests tabs no longer show fields previously configured in the RLC Custom Columns auxiliary table Default DU Custom Columns and Default Request Custom Columns entities. This means those table entries may have reverted to the defaults. This happens if you upgrade without deselecting the Include entity data check box in the Entities step when promoting the Release Data process app.

  If this occurs, you will need to reconfigure the default custom column entries as needed.

• New configuration fields don't appear in the existing configurations

  After upgrading, the new configuration fields for some plugins do not appear in existing plugin configurations in the Release Control Administration, so it isn't possible to configure them. If you do not do this after upgrading the Dimensions CM plugin, an example error message you may get is the following:

  Could not resolve placeholder 'deploy_unit_custom_attributes' in string value "${deploy_unit_custom_attributes}"

  If this occurs, you will need to open each existing configuration in the Release Control Administration, click Update Configuration, then re-open the configuration and configure the new fields as needed.

Upgrading from Custom or Earlier Versions of Plugins

Any custom plugins are automatically backed up in the ..\Program Files\Micro Focus\Release Control\rlc_lib_backup directory when upgrading to Release Control 6.2.1 from version 6.1.0 or 6.1.1.

If you want to upgrade your custom plugins or want to upgrade earlier versions of the plugins, see Knowledgebase item S142171.