New & Noteworthy for Jazz Foundation 7.0.2


Description
Global Configuration Management Work item linking and navigation in a GC context

You can now manage associations between global configurations and Engineering Workflow Management (EWM) releases in the Global Configuration Management (GCM) application.

The following changes are made in GCM:
  • The Release link type is included in the Global Configuration artifact type by default.

    Image of the Release link type added under the Global Configuration artifact type:


     
  • A wizard is created that imports release links into the new format that is required for version 7.0.2 and later.

    Image of the Import Release Links wizard:


     
  • You can use a release picker dialog box to add release links in a global configuration.

    Image of the release picker dialog box:


     
  • You can use the Release link in query conditions and view it as a result column in the tables.

    Image of a query with Release in the condition and the result:


     
  • The Release link information is added to the rich hover previews of global configurations in the Configuration Context.

    Image of a rich hover preview with Release information:
To know more about the changes that are made to support the work item linking and navigation in a GC context feature, see IBM Engineering Workflow Management: Work item linking and navigation in a GC context and Jazz Reporting Service: Work item linking and navigation in a GC context.
Add configurations between trees by using the drag-and-drop function in different browser windows

When you open global configuration trees in separate browser windows, you can now drag configurations between the trees. The drag-and-drop gesture moves configurations within a tree and adds configurations between trees. This feature helps you to quickly build a configuration tree from another one like it.


Image of adding three configurations from an existing tree to a new tree through the drag-and-drop function:
Update tags when you are creating a baseline

Earlier, the Create Baseline dialog box contained two fields: Existing Tags to show the tags of the stream the baseline is being created from, and Additional Tags to add new tags. Also, to remove tags, you had to first create the baseline, then edit it and remove tags.

The dialog box now has only one field, Tags. It is pre-populated with the existing tags of the stream, but you can add or remove tags as needed. The new baseline uses the exact set of tags from the field. To create a new tag, you need the Create Tag privilege as usual.

Image of the Create Baseline dialog box (before and after):
Use link properties in query conditions and result columns

You can now use link properties in query conditions and result columns. Link properties include both built-in link types, such as References and Release, and custom link types.

Links in query conditions
  • Generic links -  A condition against a generic link matches the URI of the link. You can use the same set of operators as are used by string attributes, such as exact match, contains, existence, and non-existence.
     
  • Release links - Links that target Engineering Workflow Management (EWM) Release objects are treated specially. Instead of a URI string, you select releases from the EWM release picker dialog box. Therefore, the set of operators (is any of, is not any of, exists, and does not exist) available here is different than for generic links. A single release condition can match as many releases as necessary.
Image of available operators in query conditions:


Links in query results
  • Link types (including Release) are now available as columns to show in the query results table. You can save them with the query in edit mode, or choose to see them ad hoc by using the Add or remove columns menu on the query results page.
     
  • In the query results table, release link types exhibit rich hover behavior while generic links (such as References) show their URIs directly. In either case, you can navigate to the artifact by clicking the link.
     
  • The list of columns (in the Add or remove columns menu, and the Columns tab of the query editor) now appears in alphabetical order to choose the required columns faster.
Image of link properties in query conditions and result columns:
View link properties in configuration pickers

You can now view link properties, such as Release and References, as a column in the results table of the following configuration pickers:
  • Add Configurations (for Global Configuration Management)
  • Select the Configuration Context (for setting a global configuration context in configuration-enabled applications)
To add a column to a configuration picker, use Add a column to the results on the toolbar.

Note: The choice of available links depends on the project area that is selected from the list.

Image of the Add Configurations dialog box with Release added as a column:
Links are enhanced in GCM

Links to OSLC artifacts now support the following enhancements:
  • Link labels show the artifact title rather than a plain text URL.
  • Hovering over the link shows a rich hover preview.
For example, the Engineering Workflow Management work item link https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/516108 is displayed as 516108: Add rich hover to link properties in the component/configuration editors, and hovering your mouse over the link shows a rich hover preview.
 
To support the link enhancements, links must be OSLC URLs (such as https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/516108) that are available on a friend server or are registered to the same Jazz Team Server. Non-OSLC URLs (such as https://www.ibm.com or https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=516108) do not support the rich hover feature.
 
Image of the rich hover in the global configuration editor:
 
Additionally, link properties are added as result columns in tables on the browse pages of both components and configurations, and support the rich hover feature.
 
Image of the Browse Configurations page with Release and References as columns:
Negation operators for a group of query conditions

Earlier, Global Configuration Management (GCM) queries supported only AND and OR operators for grouping query conditions. Now you can negate a group by using the NOT operator. Use an existing group or create one by using Add Group on the toolbar, and then select the operator from the list in the group header.

The following table illustrates the logic of each group operator:
Group Operator      Example
All match           Condition 1 AND Condition 2
Some match          Condition 1 OR Condition 2
Not all match       NOT (Condition 1 AND Condition 2)
None match          NOT (Condition 1 OR Condition 2)


The first two are not new but their labels are changed whereas the last two are the new negation operators.

Image of the query group operators:


Image of a query that uses None match group operator:
New query operator for enumerated attributes

A new operator is not any of is available in query conditions for enumerated attributes.

You can use this operator to return all configurations that do not have any of the entered enumeration values, including ones that have no values. If you want to exclude configurations for which the enumerated attribute has no values, you can add a separate condition for enum exists with it.

Image of the enumeration operator:


Image of the query results when you use both is not any of and exists in query conditions:
Additional attributes in query conditions and result columns

You can now use additional attributes in query conditions and result columns to enhance the query experience.

The following are the newly added query conditions:
  • Committed By [user]
    To find the person who committed the baseline.
  • Committed On [date]
    To find when the commit on the baseline was done.
Image of a query with Committed By and Committed On as conditions:


The following are the newly added result columns:
  • Committed By [user]
  • Committed On [date]
  • Created From [all configurations]
  • From Stream [baselines only]
Image of the new attributes available on the Columns tab:
REST APIs to find and run user-defined queries

You can now use new REST APIs to discover and run user-defined queries programmatically. Such queries can be created by using the Global Configuration Management (GCM) web interface only.

1. Query for user queries.
Look up the URIs of user-defined queries that match some criteria, such as project area, or name. You can then use the URI of a particular query to run it with the next API.

2. Execute a user query.
Run a query specified by its URI, fetching the query results as JSON data.

See the REST API documentation under gcContextRoot/doc/scenario?id=QueryingUserQueries for more details.
Redact sensitive data in a Global Configuration Management query

Global Configuration Management Administrators can now find and delete any user-defined query that contains sensitive information, even if it's a personal query of another user.
  1. Run the repotools-gc -dumpArtifacts command, and search the output files for sensitive data. This command is enhanced to include user-defined queries, in addition to components and configurations. For more information, see the Finding sensitive data topic.
  2. Note the URLs of the matching queries.
  3. Enter each URL into a web browser to run the query. From the toolbar, click Delete to remove the offending query.
You must have appropriate permissions to see the Delete action. The following permissions are required to delete arbitrary user-defined queries:
  • Delete other users' personal queries
    A new permission that is assigned to the Administrator role by default. On upgrade, it is automatically added to the Administrator role and ready for immediate use.
     
  • Modify and delete shared queries created by others
    An existing permission that is assigned to the Administrator role by default.

Image of permissions required to delete user-defined queries:
Jazz Foundation IBM Automotive Compliance licenses

You can now download the Automotive license from the License Key Center by downloading a compressed (.zip) file that contains all offering contents, including the templates, from Passport Advantage. When you assign Automotive Compliance licenses, make note of the following points:

  • Assign the Automotive Compliance content license together with a base license to use this content.
  • Do not assign multiple Automotive Compliance licenses to a single user.
Note:

If you access project areas such as Engineering Workflow Management, Engineering Test Management, and Engineering Requirements Management DOORS Next, that use the Automotive Compliance content, an extra token is used irrespective of the number of project areas that you access. The license does not provide access to the base applications, so a role-based license is still required. For example, if you open the Rhapsody ASPICE profile that is included in IBM Automotive Compliance, one token is used.

For more information, see IBM Automotive Compliance licenses.

Web UI Smart people picker component

A new people picker component is now introduced as part of the ongoing user experience transformation and alignment with IBM's open source Carbon Design System. The people picker is a dialog box for selecting users and can be used for assigning an owner or a set of subscribers to an artifact.

The new people picker is common across the following applications:
  • DOORS Next
  • Engineering Insights
  • Engineering Test Management
  • Engineering Workflow Management (including Rhapsody Model Manager)
  • Global Configuration Management
  • Jazz Team Server
The following improvements are included over the classic people picker component:
  • Access control scoping of users
    Only the relevant users are shown as defined in the Access Control setting of the current project area. For instance, if read access is set to Members of the project area hierarchy, then you can see only project area and team area members in the search results.
  • Recent users
    In addition to the current user, you can access the 10 most recently selected users.
  • Managing multiple users
    Existing users are preselected in the dialog box. You can add new users or remove existing users. Previously, the people picker only supported addition of new users. Now, you can manage an existing selection set in a single step.
Note: The classic people picker component is not entirely replaced. You can still use it in the Administration UI, and for selecting users when querying and filtering because these use cases require access to all historical users.

Image of the classic people picker component:


Image of the new people picker component (single-user mode):


Image of the new people picker component (multiple-user mode):

© Copyright IBM Corporation 2020  |   Contact  |   Privacy Policy  |   Terms of Use