A user with rights to edit a blueprint can add a secure attribute which the user does not have rights to view or edit, but after publishing the blueprint, the secure attribute is not shown anymore even though it is in the blueprint.
Steps to Reproduce:
Expected Results: The attribute is displayed in the published blueprint.
Actual Results: The attribute is not displayed in the published blueprint.
Expected results: The attribute is displayed in the blueprint (edit mode). The attribute is grayed out in the list as available to add, as it is already in the blueprint.
Actual Results: The attribute is not displayed in the blueprint (edit mode). The attribute is shown in the list as available to add (i.e.: not grayed out).
Expected Results: This step should not be possible as the attribute is already added into the blueprint.
Actual Results: An error is displayed BLP-1705: Could not add field as it already exists for the same blueprint.
Clarity 16.2.3
DE156254
This issue is fixed in Clarity 16.3.1.