Provide configuration options in administrative UI (Director) to specify for a Change Request class whether or not to automatically create prototypes for all affected documents and tags for a Change Request class whether or not to instantiate addi...

With the recent improvements to user experience of distributing documents in ALIM Web, it is now possible to Recall a distribution order. It would be beneficial to allow users capturing the reason why a recall is performed, and reflect that reason...

Currently, reworking a task sends an email to every user whose skill is linked to the task being reworked. Since a single user accepted and completed the task, there should be an option for the rework notification to only be sent to the user who c...

Currently, if a user has its email notifications on, the user will receive an email notification when a work task he's assigned to appears in his Work Exchange Inbox. Sometimes though, actions to take are spread out to multiple work tasks for the ...

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

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.

It would be very useful to have the possibility to have some kind of structure to the Basket feature, like folders for Favorites, where a user could organize his/her basket the way they want. This way, they could have multiple basket folders depen...

Action 'Reclassify object' should allow users to select not just Class but also one of the Templates from that Class (if it exists), so that: Object is updated with Template-specific properties of the newly assigned Template, e.g., security (to ma...

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

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...