Release Features
In certain customer environments where invoice numbers are mandatory during PO receiving, if a user forgot to enter a supplier invoice SDC throws a message asking for one. The receive button is greyed out at this point and the user had to refresh the screen in order to save the invoice number. safsCP260 has been modified to keep receive button enabled in this instance.
Browser: Last Reading
As in SDC users liked the ability to see the last reading in a job checklist when a trigger code is present. The SmartAsset browser will now show this value in order to help the user at the time of entering the data.
Last reading and last reading date are now also available in the mobile app
SDC: PO screen cuts off text once a large amount of lines are entered
When creating a PO with a large number of line items users were experiencing usability issues with viewing and editing data. We have enhanced the PO line item data table and screen scrolling for a better user experience.
Info | Tip
Purchase order approval will be available in the next release of the mobile app. Full PO function is coming to the browser in 2020.
ODC: Not logging off on exit.
ODC licenses were being consumed by users who were closing down the SmartAsset add-in while keeping the office application (outlook, excel) opened. This was causing issues with license numbers. In order to logout of the application users had to close down their office product. This has been addressed. Now closing the SmartAsset workbench, users have the ability to expire their session while remaining within their office product.
App: Default zero response
When entering in checklist responses via the mobile app users were given a default response of zero '0'. If the user did not remove the zero while entering a statistical reading, the zero was included in the response. We have modified the app to now automatically remove the zero as soon as the user starts to key their response.
Browser: Job Request Status Filter
When viewing a list of job requests in the browser the Status filter was not filtering the data correctly. This issue has been resolved.
Comments
0 comments
Please sign in to leave a comment.