Fixed In This Release
Reuse Existing Parent Identifier Attributes
Let’s say you have a SmartPin type, Node Maintenance, with an Attribute named NodeName to identify the node the maintenance if for. But now you want to make use of our new Tasks feature that lets you create a parent Node SmartPin and then create child tasks from the parent Node SmartPin.
So you make the NodeName attribute a parent identifier. And then you edit the Node SmartPin type and choose the NodeName as the parent identifier attribute. Then you choose the children for the Node SmartPin, such as Node Maintenance. When you tried to save that Node SmartPin definition, you got an error that looked like this:
java::OrgPostgresqlUtil::PSQLException: ERROR: duplicate key value violates unique constraint "region_context_attributes_region_context_id_attribute_id_index" Detail: Key (region_context_id, attribute_id)=(0682e096-9155-474d-bf2d-65e92722a063, 242ea943-bd50-4c44-91f2- 9f8e1b6bc403) already exists
The code used to assume that the parent identifier attribute needed to be added to all of the child SmartPin definitions, when sometimes, the child might already use it.
So we fixed that assumption.