Performance and Stability Enhancements:
•When changing an Asset’s Asset Type, the Asset now inherits all of the Asset Type settings
•Creating a new Asset with a Dimension value for the ‘Dimension to Value By’ set on the Asset Type now sets the Measurement to the same value
•‘Split Asset’ now creates a Depreciation Transaction before the Split, if the System Option ‘Force depreciation before Action completion’ is ticked
•Assessed Residual Value is no longer being Calculated 'on the fly', instead the Residual Value from the Asset record is used
•A Purchase Action Completed on a Proposed Asset now correctly calculates the Assessed Residual Value
•Issue to Printer with multiple PDF Attachments are now appended to the Work Order. This requires the ‘Adobe PDF Reader’ plugin in Internet Explorer
•Succeeding Actions will now be related to a Request on their predecessor
•Repeatable Actions now always recur according to Duration value
•General
•“Check Box” data values of (1,-1,True,Yes) and (0,False,No) are all accepted
•In all cases, errors in the Import data can be Output to CSV with an Error Message, whereas all valid data is accepted
•For Asset transactions, if the transaction is not a Valuation then the existing ValueBy value is used. If the transaction is a Valuation and ValueBy is not provided, the current Username is used
•Asset Inspections no longer set the next Condition Inspection Date
•When Importing Journal Entries the transactions are now being created correctly
•‘Split Asset’ Imports now create a Depreciation Transaction before the Split, if the System Option ‘Force depreciation before Action completion’ is ticked
•Multiple new Actions with the same Description are now accepted
•When Importing new Actions with User Fields, the inclusion of either StdActionID or ActionCategory will allow the User Fields to be validated against the Attribute Set. For existing Actions being updated, which already have an ActionCategory, the User Fields will be validated against its Attribute Set, if not, either of StdActionID or ActionCategory must be included in the CSV file to update the Action and allow the User Fields to be validated
•Updating an Action’s EstQuantity is now handled correctly
•Updating existing Actions using ReferenceID is now handled correctly
•Importing new Actions with Tasks and Resources will now acquire the Standard Rate for the Resources and calculate the values correctly
•Imported multiple Defects to the same Asset, “Groups” them into a single Inspection
•Multiple Readings on the same Log Book are now accepted
•When a Log Book has the Cumulative checkbox ticked, new Readings being imported must not be less than the most recent existing Reading. This rule applies in the Log Book Form too
•General:
•A side effect of the work performed in delivering version 3.0329 is that, temporarily, the System Option ‘Allow Contractors to Complete Actions’ must be ticked for Users to be able to Complete Actions. This issue will be resolved in subsequent versions
•Database Connection timeouts no longer give an exception error, instead they retry and give the option to retry again
•The identifier for Conquest III Client Sessions is now always unique
•The “Current User” value is retained for the full lifetime of any a function that uses it, so that the ‘Editor’, ‘Created By’, ‘Completed By’, values are always correct
•The "Clear" Function of the Hierarchy Picker Control for Org Unit, Function and Location Fields now refreshes the associated field
•Reference IDs generated for Requests and Actions are now always unique, regardless of whether Conquest III and II are being used together
•The ‘Adobe PDF Reader’ plugin for Internet Explorer must be installed and enabled, if multiple PDF Attachments are required on a Work Order, when using the ‘Issue to Printer’ option