Notice types not unified criteria ("nodeId"s)

[AlexAS81]

For example, in the notice types from 1 to 6 (1.json, 2.json, 3.json, 4.json, 5.json, 6.json) in the group "GR-Procedure-Scope-MainClassification" it is not indicated a "nodeId", in the rest of the notice types there is.

Group in 4.json:

Group in 10.json:

This makes it impossible for us to correctly generate the conceptual model. We understand that the notice types should be unified and the same groups should have the same nodeId. Is there an intention to correct this? Or do we have to adapt the SDK to make it work? Since before, the lack of unification of criteria is making it quite difficult for us to use the SDK.

Thanks in advance

[rouschr]

Hello,

it is indeed a bit strange that this same group has a nodeId in some notice sub types but not in others.

          "id" : "GR-Procedure-Scope-MainClassification",
          "contentType" : "group",
          "nodeId" : "ND-ProcedureMainClassification",

As ND-ProcedureMainClassification is not repeatable, you can create it in your conceptual model before going to the physical model.
But we will look into this to see if there is a reason for it to be missing.

[AlexAS81]

In addition to not being unified through the nodeId, in one of the notice types it is repeatable (10) and in the other (4) it is not. Does this make sense?

[rouschr]

I looked into this and created a ticket, maybe some of these changes will make it into SDK 1.9