Data3Sixty® Govern March 3, 2019 Release is Now Available

The March 3, 2019 Release is now available and will be pushed on the following dates:

• DEV Environments: Sunday, March 3, 2019
• UAT Environments: Sunday, March 3, 2019
• PROD Environments: Sunday, March 10, 2019

The enhancements and fixes of this release are below.

 

Field type enhancements

'Decimal Number' and 'Number' field values (GOV-6299 and GOV-6287)

Additional setup parameters have been added to the Decimal
Number and Number field types to allow you to ensure that users
enter values that are within a specified range.

You can specify a minimum and a maximum value, and an
increment value which allows users to use the up and down arrows
on the field to select a value according to the defined increment,
within the specified range. For Decimal Number fields, you can
also specify the number of places to the right of the decimal place.

The specified parameters are validated when a user enters a value
in a Decimal Number or Number field, and users are warned if the
value that they have entered does not match the validation
criteria. For example:

Note: Existing Decimal Number and Number fields do
not contain any validation. You will need to edit existing
fields if you want to add validation.

Default field values (GOV-6377)

There is now an option to provide a default value when defining a
field that has an Input Type of Date, Html/Richtext or Link.

JSON fields (GOV-6526 and GOV-6592)

Technology Asset Properties and Normalized Asset Properties will
now display JSON formatted fields as an object that can be
expanded and collapsed.

Dates returned in JSON format have been changed to limit the
precision of the nanosecond piece to a fixed three digit precision,
for example:

2019-01-22T14:20:42.597Z

 

API v2.0 improvements

REST API v2.0 performance improvements (GOV-6490)

The performance of the v2.0 REST APIs has been improved in this
release.

Swagger API documentation (GOV-6495)

The v2.0 API Swagger documentation for the GET
/api/v2/assets/{assetTypeUid} request has been
expanded to include an Implementation Notes section, which
provides information on optional parameters that may be used
with the GET request in third-party API clients. Additionally, the
Parameters section has been expanded to include several optional
parameters that may be used with the request in Swagger or in a
third-party client. The options include:

• _pageSize
• _pageNum
• _order
• _predicateUid
• _subjectUid

Details on using these parameters are included in the parameter
descriptions.

To view the API documentation, navigate to Administration >
Integration > API.

Correlate API results with an asset (GOV-6589)

The Assets API v2.0 now provides an ability to tag each asset in
your array with an 'ExecutionItemUid'. This value is returned in
the API response, allowing you to correlate your submitted assets
with the assets in the response.

The ExecutionItemUid can be the asset Uid value, or any
unique value in the following format:

00000000-0000-0000-0000-000000000000

Note that if your request includes multiple assets, there is no
requirement to include an ExecutionItemUid value for all
assets.

 

Other changes

Relation Lookup fields (GOV-6315)

When creating a Relation Lookup field on an asset, a configuration
grid is displayed.

The fields available to display in the grid have been limited to
only those that are appropriate. The following field types are no
longer displayed in the Relation Lookup grid:

• Relationship
• Ownership Lookup
• Reference Item List from Relationship
• Fusion Lookup
• Filtered Lookup

Field definition (GOV-6354)

The Field Definition panel now only allows you to select field
types that are applicable to the asset type on which the field is
being defined.

 

Corrected Issues

Open Actions description (GOV-6561)

Fixed an issue that prevented the display of action descriptions in
the Open Actions grid when the Write Action Description to
Comments? setting was not selected on the Administration >
Settings page. Previously, the Description column would show
'null' or appear blank in the Open Actions grid of an asset.

List field value (GOV-6558)

Fixed an issue that caused a number to be shown in place of the
default value on list type fields in the artifact list page. This issue
occurred if an artifact had a list field with a default value specified
and the Is Listable? option was selected.

Rule values (GOV-6557)

Fixed an issue where values on a rule could not be completely
cleared out of the screen and would reappear after saving.

Custom export templates (GOV-6549 and GOV-6505)

Fixed an issue that caused custom export templates to generate
unreadable Excel files for artifact types when all fields had a Sort
Order of 0.
Fixed an issue that prevented ownership filters from being applied
to exports using custom export templates. This issue only affected
custom export templates.

Reference list value (GOV-6546)

Fixed an issue where Relation Lookups to a reference list
displayed an incorrect value.

Responsibility rules (GOV-6560, GOV-6621, GOV-6613, GOV-6276, GOV-6258, GOV-5761 and GOV-6517)

Fixed an issue that prevented non admin users from seeing the
Edit and Delete buttons in the Rules panel when a responsibility
rule granted them access to perform these actions.

Fixed an issue that prevented the Edit and Delete buttons from
showing in the Attributes section on an asset detail page for non
admin users who had been granted add, edit and delete
permissions via a responsibility rule that was not applied to an
entire type.

Fixed an issue that prevented the Edit and Delete buttons from
showing on the Policy list page for non admin users who had been
granted the permission to perform these actions via responsibility
rules.

Fixed an issue that caused users to have incorrect permissions as a
result of responsibility rules failing to build correctly.
Improved the scalability of responsibility rules when working with
large volumes of artifacts or users.

Fixed an issue that caused responsibility rules to become
ineffective when a responsibility type had multiple rules and one
was deleted.

Fixed an issue where the relationship Value list did not show the
full text path for models and policies when adding a condition on
the When Filter of a responsibility rule.

Assets API v2.0 (GOV-6545, GOV-6417 and GOV-6403)

Fixed an issue in version 2 of the Assets API where a child asset's
parent was not being taken into account when determining
uniqueness.

Fixed an issue in version 2 of the Assets API where submitting
simultaneous DELETE requests resulted in a transaction error.

Fixed an issue in version 2 of the Assets API where child assets
were not properly displayed in the user interface list page.

Relationships API v2.0 (GOV-6381)

Fixed an issue in version 2 of the Relationships Batch API where
errors were not properly indicated. Additionally, to reduce the
error rate, the load is now divided into chunks of 100 relationships
at a time.

Metrics API v2.0 (GOV-6305)

Fixed an issue that caused the Metrics API to return a 200 response
code instead of a 404 error code when the selected metric had
already been soft deleted.

Hover icon (GOV-6499)

Fixed an issue where the hand symbol was not shown when
hovering over the Edit and Delete buttons in the Shortcuts panel
on the Administration > Settings page.

Bulk load (GOV-6481)

Fixed an issue that prevented the successful completion of
Users/Groups bulk load actions when the mandatory Status
column was not populated. Previously, this resulted in the bulk
load being stuck in the Queued status instead of failing with the
correct error. Bulk loads now validate that the Status column
contains a valid value (Active, Inactive or Deleted).

Workflow (GOV-6502, GOV-6483, GOV-6616 and GOV-6611)

Fixed an issue that prevented workflows from being triggered
when the Object Type was a Rule Type.

A performance improvement was made when triggering a
workflow that included a form with 'Reassign to Object' enabled.
Previously, depending on system volume, this type of workflow
action could time out when a user attempted to complete the
form.

Fixed an issue that prevented some older workflow assignments
from being completed.

Fixed an issue where List fields on Action Types were showing as
blank when setting up a workflow form.

Models (GOV-6466)

Fixed an issue that caused search criteria for a selected model
type to remain in the search box even after navigating to a
different model type.

DB2 Fusion agent (GOV-5963)

Fixed an issue that prevented data from being returned from the
DB2 Fusion agent in some cases.

Markit lineage (GOV-4770)

Fixed an issue that prevented automatic Markit lineage generation
from successfully handling more complex diagrams.