Don’t allow Reviewers and RO Editor only users save changes to Word attachments and library documents
Put a Create PDF button on the Review ribbon
Don’t allow Reviewers and RO Editor only users move procedures and folders on the tree
Added a menu item to create an Import file from an approved procedure.
Converted PDF RO References to Uppercase so that the PDF Links to the complete RO Report would work.
Eliminated Unit ROs from ROCompleteReport references in the PDF Links
Convert RO Links to Uppercase to be consistent.
Use static function to check user’s security level in allowing the insert or change of a transition
Use static function to check user’s security level in allowing the user to edit a table cell
Use static function to check user’s security level in allowing text modifications when keyboard shortcuts are used
ROEditor only security is now also considered a Reviewer. Don’t allow a Review goto an RO (run the RO editor), Don’t allow a Reviewer toggle out of view mode from the context menu, for Reviewers, don’t allow the Enter key enter new steps and substeps.
For Reviewers, when on a table (grid) have the Enter Key move down to the next step element, don’t allow Reviewers edit a table
Pass user security info to the panels, fix security related issues on the V button (B2015-188, B2015-193)
Added static functions to check the user’s security level
Use static function to check user’s security level in allowing applicability changes
Use static function to check user’s security level in enabling Inserting and RO and in Editing an RO
B2015-138 When Importing a procedure that has a customer RODB location, and the RODB locations in the Database have been updated to local locations, the user is given the choice of RODBs. If the user answere OK the RO Database is set for the procedure set (Working Draft). If the user presses the Cancel button, the import is canceled.
B2015-195 When trying to set an RO Path for a procedure set, the OK button was not being enabled. This has been fixed.
B2015-196 If you change an RO Path to match an existing path you will be giving a message saying that this cannot be done.
During D.C. Cook training I noticed that there are two items in the tool bar that should only be available in DEBUG mode. These are LastChange and StepRTF which are used for debugging Multiuser. They have been changed to not be visible for production mode.
Remove locked or unlocked from toolbar. It was not connected to anything.
Allow the existing (Customer) FSTs to be used without a local copy of the RO database.
B2015-166 Summary of Changes - Remove duplicate records for new steps.
