DocRead Roadmap

To allow DocRead to be used in different languages and also different use cases (such as "watch video", "take test", "list to webcast") it's necessary to control the messages that get displayed.

This will be made possible via a series of user defined templates.

To support other features such as 'Message Templates' and new Globally scoped Reports a new group will be people picker will be added to Central Admin. This control will represent all of the 'Global Administrators'. If you are a member of this group you will be able to do everything that DocRead Admin can do (aswell as the new features).

A change will be made to allow Active Directory Groups to be directly input into the 'Required' and 'Recommended' Audiences Fields.

This means that you won't be required to create a SharePoint Group that embeds an AD group.

sk user to electronically sign reading acknowledgements to make DoCRead compliant with the FDA’s 21 CFR Part 11 regulations.
The FDA requirements are:

A method of identifying an individual’s identity based on at least two distinct identification components such as ID code and password. Requires that at least one component be known only to the individual. The combination must be unique to the individual user.
Signed electronic records shall contain information associated with the signing that clearly indicates all of the following:
- the printed name of the signer (we retain these records manually, so this is a nice to have for us),
- the date and time when the signature was executed and
- the meaning (such as review, approval, responsibility or authorship) associated with the signature.
- The items in (2) shall be subject to the same controls as for electronic records and shall be included as part of any human readable form of the electronic record (such as electronic display or printout).
In other systems, such as HP Quality Center, there is an icon to select from the Toolbar (in that case it is a pencil icon), then a pop-up box displays where the user has to enter a user id and password, here is an example…although in this case it would not be about approval, it would be about ‘Read and Confirmed’. After inputting the user name and password, a box comes up with what this signifies.

To improve the usability of DocRead, when a new user clicks on 'View Document' a change will be made so that it opens in a new browser window. This will prevent users from getting confused to where the document is.

To prevent very large reports from slowing down SharePoint it is necessary to introduce a system that allows them to be scheduled in the background. Once this in place a new threshold can be set by a Central Administrator to disallow large Reports from being requested.

For documents that must be re-read on a regular scheduled basis (e.g. every year), a facility will be made available that allows the publisher to specify a date and time to automatically reset all tasks and create new ones.

It should be possible to target a single user in the Required and Recommended Audiences field.

Currently, to edit email templates it must be done manually by editing a table in the DocRead database. As part of this feature a new screen will be created to allow them to be developed using a Rich Text HTML editor.

When assigning a large number of policies at one time to users, is it possible to group/aggregate them in one email when assigned rather than sending an individual email per policy? We often release 6-10 policies at a time which triggers 6-10 emails multiplied by the number of staff can trigger thousands of emails in a release.

Provide a feature that allows DocRead Admins to be able to recreate tasks only for users who are overdue.

When a user confirms a document it will be converted to PDF and stored in the DocRead database. This will ensure the exact copy is always accessible, even it if is deleted from SharePoint.