[OPENIDM-9897] 5.5.0.1 Backport OPENIDM-9362: Managed.json does not contain all attributes within order array for default managed object types Created: 21/Dec/17  Updated: 03/Jan/18  Resolved: 29/Dec/17

Status: Closed
Project: OpenIDM
Component/s: Module - Configuration
Affects Version/s: OpenIDM 5.0.0, OpenIDM 5.5.0, OpenIDM 6.0.0
Fix Version/s: OpenIDM 5.5.0.1

Type: Bug Priority: Minor
Reporter: Mark Offutt [X] (Inactive) Assignee: Mark Offutt [X] (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backport
is a backport of OPENIDM-9362 Managed.json does not contain all att... Closed
Target Version/s:
Verified Version/s:
QA Assignee: Jakub Janoska [X] (Inactive)
Support Ticket IDs:

 Description   

Within managed.json, the 'order' array is used to define the order in which attributes should be returned. However, for the 'assignment' managed object type the following attributes are included within managed.json by default:

_id
name
description
mapping
attributes
linkQualifiers
roles

But within the 'order' array, we only have the following defined:

        "order": [
          "_id",
          "name",
          "description",
          "attributes",
          "linkQualifiers"
        ]

There is a similar situation for 'role' where the following are included by default:

_id
name
description
members
authzMembers
assignments
condition
temporalConstraints

But the 'order' array only contains:

        "order": [
          "_id",
          "name",
          "description",
          "assignments",
          "members",
          "condition",
          "temporalConstraints"
        ]


 Comments   
Comment by Jakub Janoska [X] (Inactive) [ 03/Jan/18 ]

Verified onĀ OpenIDM version "5.5.0.1-SNAPSHOT" (revision: 8fc15e9) jenkins-OpenIDM - 5.5.x - postcommit-138 origin/sustaining/5.5.x.

Properties and order arrays contain the identical attributes for default objects in managed.json.

Checked OK.

Generated at Sat Oct 31 01:54:10 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.