This section lists the fixes made to MoversSuite.
MoversSuite Administration: Order Number Setup
Invalid numbers are no longer permitted within the Year Length field.
To ensure only the correct data is set for the Year Length field, a dropdown was created to offer the only valid options: 1, 2, 3, or 4.
INTERNAL REFERENCE:
MOV-1444
MoversSuite Administration: Account Profile
Addresses saved within Office & Industrial as Preset are now reflecting within Account Profile > Preset Addresses.
Previously within the Office & Industrial module, when a Location address was edited within the MoversSuite > Office & Industrial module > Contacts and Locations tab, the update was not reflecting within MoversSuite Administration > Account Profile > Account Profile record > Preset Addresses. The record is now being properly updated.
INTERNAL REFERENCE:
MOV-5682
MoversSuite Administration: GL Code
“GL Control Code” has been renamed to “GL Code.”
This is to provide name consistency throughout the Admin Tool and GL the Item Code Mappings. The Online Help topic was also renamed to from GL Control Code Setup to GL Code Setup.
RELATED INFORMATION:
INTERNAL REFERENCE:
MOV-1848
MoversSuite Administration
When passwords are set, they will show as obfuscated.
Sometimes when a password was set, the Administrative records did not clearly show that the password had been set. Additionally, the password field was sometimes showing outlined in red, indicated it is mandatory and further implying it was not set. Now the passwords will show as in the image below which indicates that a password has indeed been set. Of note, the number of obfuscated characters does not reflect the number of characters set as the password.
INTERNAL REFERENCE:
MOV-6852
MoversSuite Administration: Personnel Setup
Within Personnel Setup > User tab, the calendar functionality was removed from the “Last logged into MoversSuite” field.
The “Last logged into MoversSuite” field is a read-only field; therefore, there is not a use for the Calendar icon.
INTERNAL REFERENCE:
MOV-4685
VendorsConnect
Error message better reflects the error.
VendorConnect integrators that run stored procs would return “Invalid JSON primitive” as the error message anytime the MoversSuite API service would throw an exception. What should have been reported was the true exception such as:
•Bad Parameters
•The stored proc threw an exception.
•An exception while processing the results of the stored proc.
•...and so on.
INTERNAL REFERENCE:
MOV-6991