to inactivate a custom field you have to edit the entry where we used to be able to just check the box- this is where we (database admins) also notice that maybe there are others that need to be inactivated... at least offering the same "completed" option in the elipsis (like in actions) would be helpful!!!
This is another example of webview requiring more clicks. Seems to be a step backwards to have to more upfront options.
This would be great, or adding an "End Date" field.... currently we add an additional attribute that says something about being a "former", etc... so we have the historical record.
Yes! The way we currently interact with Attributes in database view--being able to see on one screen which attributes are active, which are required, which can only appear once on a record and what data type they are is very efficient and time saving.
It encourages review of these settings every time we, the dbas/dbms, go to this part of Configuration, whether to update an existing attribute or add a new one. I, for one, after dealing with the attribute for which I turned to this screen, always look through the list of attributes to see if any need to be deactivated, made or unmade required etc. If we don't have that, this part of keeping the db clean will inevitably get put off.
Yes - this would make daily work much easier - more frictionless, some might say - and would also provide consistency with other ways we interact with the system. Clicking the ellipses to mark actions as complete, for instance.
the other checkboxes would be helpful as well!!!