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.
Verify that the RO Path is not previously used (for a different RO Database) This will resolve an issue that we were seeing where AEP was changing the RO Path from ROAOP to ROEOP and the result was that the association was changed. The code will now check that this will not be able to happen.
Fixed Bug B2015-171 - when the Library Documents Report located Disconnected Data records. Previously, the code would crash.