Pre-Release Announcement: AODocs V43

Dear AODocs Users,

We are preparing the launch of the version 43 of AODocs planned for May’17!

Please find the list of changes and features that will impact the end-user and administrator experience.
This post is not an exhaustive list of the features launching with AODocs version 43, subscribe to our Announcement List to receive our Release Note.

Document editor

Improvement of the Dates fields (can navigate the month of years)


Visible by:
Contributors
Category: Changed element in existing screen


Comments on AODocs documents




Visible by:
Contributors
Category: Changed element in existing screen


Make the field types explicit in the document form

Visible by:
Contributors
Category: Changed element in existing screen


New Save button


Visible by:
Contributors
Category: Changed element in existing screen


Set comments on manual workflow transitions as mandatory


Visible by:
Users (configurable by Administrators)
Category: Changed element in existing screen


Display text for URL fields

Visible by:
Contributors
Category: Changed element in existing screen


In a Document Management Library, “Attach a file” to a document directly from the sidebar, even in “view” mode
Visible by:
Contributors
Category: New elements in existing screen


Library configuration

Set Properties as Mandatory or Hidden according to the workflow state
Visible by: Administrators
Category: New elements in existing screen


Modify the visibility of a workflow state from the workflow basket or the "browse by" in a view

Visible by:
Administrators
Category: Changed element in existing screen


Miscellanous

Reorganize "Create" tab in AODocs homepage


Visible by:
Library creators
Category: Changed element in existing screen


Hidden properties are now also hidden to non-administrators in the views (as in the document editor)

Be it for properties always hidden or properties hidden depending on the workflow state, the properties will also be hidden in the views where the columns are displayed.

Visible by:
Viewers
Category: Changed element in existing screen

5

Comments

2 comments
  • Thibault,

    These all look like great improvements, and we are looking forward to seeing them in production. I know this is just a preview and perhaps these things will be changed before they are rolled out, but I have a couple of picky comments on the wording of some of these items shown in this preview.

    -- In the prompts next to field types, the prompts you show in your example aren't all properly-formed English. For instance, "Please enter a text here" should be "Please enter text here." "Please enter an URL here" should be "Please enter a URL here."

    -- In the new prompts for attaching a file, the choices don't all match. It would be more proper to be consistent and just have the choices "Attach," "Upload and convert" and "Create." Or, "Attach file," "Upload and convert file" and "Create file." Or, "Attach a file," "Upload and convert a file" and "Create a file."

    -- Is there any way that the primary action name (e.g., "Approve," "Reject," etc.) could be capitalized on the action validation window?

    Minor points, probably, but they just jump out to me when I view the UI.

    Thanks,

    Amy Gannon

    1
    Comment actions Permalink
  • Hello Amy,

    Thank you for your feedbacks.

    Everything was taken into consideration. Please let us know afterwards if we missed some.

    Among the other enhancements to expect in production this month:

    • library statistics for super administrators (domain administration)
    • ability to create document templates with one attachment for Team Folder and Secured Folder libraries

     

    Regarding some impacts you may experience from release 43:

    • "revert to this version" action will no longer be available from the previous version page (as a preview).
    • message "No value" displayed in edition for read-only empty fields (for the contributors) will be removed (it was introduced in release 42). Those fields will be hidden as previously until a value is inputted by an administrator or the field is no longer read-only.

    Finally, regarding the properties becoming mandatory per workflow state, the workflow transitions will be prevented until mandatory properties are filled with a value.

    1
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post