IT:
•This version requires:
•The Web Server to have the Microsoft .NET Framework version 4.6 or later, installed on it
•The Conquest Management Console updated with the latest version 1.0.11
•For Databases being upgrading from versions before 3.1:
•If you intend to use CMTPC 4.0021, substitute 3.2 as the target database version in the following bullet points
•Obtain a version 3.1 database script from the Management Console, Management Console Products, and apply it to your database(s)
•Perform Refresh System Objects with the 3.3 Data Objects, to be performed from the Management Console, on the Conquest database for the Conquest III web site being upgraded
Stability:
•General Fixes:
•The "Please Wait" message during batch Valuations/Depreciations/IndexationsGroups is no longer being left behind
•Fixed a problem with the length of the path for an Icon file being exceeded after security encoding. This is unlikely to affect many people but, if it does, use the Management Console to download a database script to upgrade the database to version 3.3 and apply it from SQLServer Management Studio
•Assets
•The ‘Batch Valuation tool’ was resetting the Expiry Date of all Assets in the Filter instead of just those without an Expiry Date, and was doing so for all Valuation Methods instead of just Replacement Value and Age. This has been corrected
•When an Asset is locked due to being Checked-Out, the message is now given in a message box in the Asset Form header panel, “Read Only: Checked out to Mobile”.
•The ‘Log Book’ Form:
•Now allows initial creation of the ‘Log Book’ and entry of the first Reading, all in one operation, without error
•Allows the Log Date to have a Time part
•Allows multiple Readings on the same day, provided that the Time is properly configured
•Importing ‘Log Book’ Readings will now accept multiple Readings on the same day with or without a Time part to the Log Date. In the absence of a Time part, it generates the Time part by one second per row, from the latest Time for existing Readings on the day, if there are any
•Actions and Requests
•Fixed a problem when you create/use a Log Book Standard Action with no value in the 'Reading for Advanced Warning' field, causing a prompt to create a new Action when you enter the first Log Book ReadingKnowledge Base
•Moving, Copying and Adding an Organisation Unit is now handled consistently, with reuse of hierarchy gaps
•A proper message is now given if you try to create an RSM “Special Type” of Asset Type on an existing Asset Type that is not an RSM Road
•Fixed a problem with the Standard Action Form, Estimates and Costs Tab not refreshing correctly