Allow limiting editing capabilities to only assigned individuals while object is a subject to a workflow
It would be beneficial to introduce a setting (per scope), which would allow restricting editing object properties/attributes only to those individuals who are currently working on an active workflow task - while the object is a subject to an acti...
Implement ability to retrieve Asset information Document or TAG's (with related docs) by use of Tablet/mobile device. Also implement barcode scanning to enable TAG barcode's so we can scan them in the filed for easy information gathering.
In editing mode, allow users to filter out only empty mandatory fields
In editing mode, allow users to filter out only empty mandatory fields. Currently users sometimes have to scroll through 50-60 attributes trying to locate which one is mandatory and is not populated
Extend "Download files" action to all object types which support file containers
Currently, the wizard only supports documents. Would be great to support objects which allow configuring file containers (e.g. CRs, physical items, etc.)
Change package wizard: when initiating from the basket only add selected objects
The current design of the change package wizard assumes that all contents of the basket will be added to the package. It would be more consistent user experience if we allowed selection of objects as well (if no objects are selected, we can keep t...
Provide ability to specify equipment classes to be related to a document (e.g., to a standard operating procedure)
On Document attribute X being saved, relate any physical items that are not obsolete and have the same class(es) as the value(s) set in the attribute with relationship type Y to that Document (X, Y to be provided in corresponding settings per scop...
Show "locked" icon for those objects where a corresponding file container has been checked out
Currently, the "locked" icon only applies to Documents but not to other objects which support adding files directly (e.g. Change Requests, Tags, etc.) The change should apply to both the object page and relevant tree navigators
Simplify check-in process for files with duplicating names
Clicking on the check in option opens a drop zone for the file, and if user drops in a file that starts with the leaf name of a checked out file (and same extension) we could ask if they want to use it to check in the original file
Allow formatting output columns in eQL search/reports
Examples: Support different date formats (to avoid having to use CAST function in eQL which causes not being able to sort by that column later) Allow defining precision for number fields Allow specifying width of columns