+7The AttributeManager accounts for all attributes, including those without action. If I remove an attribute that is listed in a following AttributeManager, the transformer turns red, indicating an error. This should be ignored for all 'Do Nothing' and 'Remove' attributes - the list of attributes in the AttributeManager should simply be updated.
+7
+7I have one more thing to add to this: At the moment all attributes within an AttributeManager are subject to workspace search, including do-nothing attributes. This means that the search for an attribute will list mostly all AttributeManagers even if no action is applied to it. This is rather confusing as I'm usually interested in where attributes change. I would suggest to exclude all do-nothing nothing attributes in an AttributeManager from the workspace search.
+7I have one more thing to add to this: At the moment all attributes within an AttributeManager are subject to workspace search, including do-nothing attributes. This means that the search for an attribute will list mostly all AttributeManagers even if no action is applied to it. This is rather confusing as I'm usually interested in where attributes change. I would suggest to exclude all do-nothing nothing attributes in an AttributeManager from the workspace search.
+7Another note on this - all attributes listed in the AttributeManager are subject to workspace search, even those I do nothing with. This is slightly confusing when searching for a certain attribute as the search will list all AttributeManagers although the do nothing attributes are only carried through without action. Therefore I think that do nothing attributes should also be excluded from the workspace search.
+1
I'm finding AttributeManager almost impossible to use as I work on a REST/JSON-related development due to these downstream errors. But I still need to modify properties...
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
