Mobi Release Notes 1.74

Ticket Number/TitleDescription of FunctionalityDescription of Usage
Charges edit screenPreviously, in the Accounts screen, users may have faced an issue where decrementing the value field does not calculate the tax correctly.

This has now been fixed to show the gross amount after tax. Also, an error in tax calculation has been corrected an error when the value for a charge is changed.
No change required in usage or settings.
373611, 381958 Reports – Add Tax Column to BOLThe Charges Section in Reports now has an “Inc Tax” Column and a “Tax” column. Each charge line displays a tax amount and a tax type subtotal.Heading “Inc Tax” can be changed to “Ex Tax” by adding a parameter in the report settings as “tax” with a value of “Ex Tax”.
378739 – Extended Charater Set – IOS – Report PDFsPreviously, IOS users may have faced an issue while generating PDFs with setting “ExtendedCharacterSet”.

This has now been fixed to work with network connectivity in IOS.

For Android, this works fine in both Online and Offline mode.
No change required in usage or settings.
381958 – Displaying Ex Tax values in reportsEx Tax values are now displayed in reports.No change required in usage or settings.
382473 – Materials display Tax AmountThe Tax Column Heading in Material Screen has been changed to highlight as ‘Ex Tax’.No change required in usage or settings.
382667 – Tax types in accountsEnhancement in Accounts Section of Reports:
Added a tax column and a break down of tax type.

Enhancement in Accounts Screen:
– Added break down of tax type.
– Added the ability to toggle between Inc Tax and Ex Tax.
– Added the setting: AccountTax to default Ex Tax or Inc Tax.
Setting Default Tax Display:
Code Type:  Setting
Code code: “AccountTax”
Code desc: “Default Tax Display”
Answers: Ex Tax, Inc Tax
Default answer: Ex Tax
control type: Toggle
Lookup sort: 100
382873 – Mobi Location search by StringPreviously, when users looked up locations in Mobi, they did not have the option to search for a specific location by its partial text.

This has now been implemented. Users can now search for locations using partial location strings.
Setting:
Code Value: “BlankLocationSearch”
Description: “Allow blank location searches”
Answers: “Yes,1,2,3”
Parent: “User”
Comments: “This setting only controls if a blank search is allowed, and if not, then how many characters must be entered in the search.”
Control Type: “toggle”
Lookup Sort: 369
Admin only: “Y”

Usage:
The Default answer, from Mobi settings for users, can be set to “Yes” for blank searches or can be set to a minimum number of characters that have to be entered to do a search.
The refresh button on the lookup screen on the right top corner acts as the search button.
382988 – Reports – Packtype does not display in certain conditionsPreviously, users might have faced an issue where pack type and pack method would not be displayed in reports for inventory.

This has now been fixed. Also, the destination condition has been added for inventory items.
In the report setup, for the report, a parameter “destinationcondition” can be added with value set as yes to show the destination condition for inventory in reports.


385224 – Auto-created diary actions should be marked as complete throughout the appPreviously, diary actions auto-generated by Mobi were not getting marked as completed. One example is auto-generated diary actions when a message, SMS or email is sent.

This has now been fixed.
No change required in usage or settings.
385642 – Inventory displaying weight but not changing the headerPreviously, in the Inventory section of reports, the Volume headers would not change or set according to the user settings.

This has now been fixed.
If weights are disabled in Mobi, then the values and headings would show as what is set by the users in the app – Meters/Feet.
385850 – Accounts and Timesheet – Failed to refreshPreviously, users may have faced an issue where while updating timesheets, times for vehicles may not get updated, or, times for labour and vehicles would not refresh immediately after an edit.

This has now been fixed.
No change required in usage or settings.