Bulk Edit

 
In addition to renaming a larger number of objects, IRM also allows larger numbers of objects to be edited via a dedicated Bulk Editor dialog.
 
CAUTION: As with any option that can potentially affect a very large number of objects, care should be taken when using this operation.
 
Users are able to open the Bulk Editor dialog using:
 
  • drop-down menu opened by a designated button located in the top Function panel. In that case, it operates on the Filter basis, where the updates will be applied to the filtered objects in the Object Grid. If no filters are applied to objects of a particular super category, a warning popup is shown saying “Bulk Editor Error - Please apply at least 1 filter.”;
  • context menu item, when selecting multiple objects in the Object Grid or Design World. In that case, the updates will be applied to the selected objects.
 
Once opened, the dialog shows relevant data-value pairs for the selected object type, with some additional filtering options:
 
The Bulk Editor dialog has different modes for editing multi-valued fields, located at the top of the editor:
 
Otherwise, all other UI elements are standard and well-known throughout different object Editor dialogs.
 
Some of the rules the dialog operates by:
 
  • All non-editable fields are excluded, as well as fields not suitable for bulk edit operation, such as name, position, etc.
     
  • The Bulk Editor does not put any restrictions on constant fields in Managed Object Types, i.e. all constant fields will be shown. If users try to edit them, and there are objects that have a reference to them, the client will show an Error dialog and the whole operation will fail. Constant fields for Managed Objects are excluded.
     
  • There are no restrictions on non-semantic fields as well, that is, all non-semantic fields will are shown. If a field is inherited and overridden from two or more different categories/types, all the overridden values will be replaced by the specified value.
     
  • Only edited fields will be updated, i.e. if a field remains unedited despite having some default value (0 or false or empty string), it’s not going to be updated.