Release Notes | iStrada Web Portal
Web Portal
Sprint 47 – Closed
IST-2505 | FD 13917 – iStrada Map showing all Trucks on the map
• SUMMARY: Before the fix, when right clicking on a Truck on CG Tracking and selecting Truck Map, iSTrada Map would display showing all trucks.
After the fix, only the truck selected is shown on the iStrada Map
IST-2498 | FD 13885 – Issue with dates on Snail Trail
• SUMMARY: Before the fix, when changing the time on the Snail Trail, the dates would change. After the fix was put in place, changing the time on the Snail Trail will not affect the dates.
Before changing the time
After changing the time > the dates did not change
Sprint 46 – Closed
IST-2073 | FD 10227 – Improve DVIR “Send Alerts” feature to allow setting alerts when all “Types” in the section are not set as Checkbox
Features Added
• SUMMARY: Before this improvement, all “Types” within each section were required to be set as “Checkbox” for the option to appear for sending alerts. After this improvement, if at least one “Type” in each section is set to Checkbox, the option will be available to set “Send Alerts”.
Sprint 45 – Closed
IST-2464 | FD 13536 – Order not showing on the map
Fixed
• SUMMARY: Orders in Will Call status are automatically filtered to not show on the map. After the fix Will Call orders will show on the map with the jobsite geofence
Sprint 44 – Closed
No items for change log
Sprint 43 – Closed
No items for change log
Sprint 42 – Closed
No items for change log
Sprint 41 – Closed
IST-2276 | FD 12295 – Allow transfer of custom fields on Ticket from CG to iStrada
Features Added
• SUMMARY: Previously custom field information was entered on an Order in CG, the custom field information was not flowing to the iStrada ticket. After the fix custom field information shows on the iStrada ticket on the Web UI and app.
IST-2350 | FD 12552 – Add Order code to the Add on Product Report
• SUMMARY: Previously the Add on Product Report did not show the order code. Now the report and Download XLS show the Order code.
Sprint 40 – Closed
No items for change log
Sprint 39 – Closed
No items for change log
Sprint 38 – Closed
IST-2277 | FD 11522 – Un-assign Truck from the device on Clock-Out
Features Added
• SUMMARY: Previously when a Driver Clocked Out, the truck would remain attached to the device. This would cause a license to remain in use. A New Feature was added to Un-assign the Truck from the device once the Driver clocks out, which will decrease the number of licenses in use. This Feature is configurable per Division in Settings > Organization > Timekeeping.
The “ON” setting will remove the truck from the device upon Clock Out. The “OFF” setting will keep the truck assigned to the device upon Clock Out.
Sprint 37 – Closed
No items for change log
Sprint 36 – Closed
No items for change log
Sprint 35 – Closed
No items for change log
IST-2250Time Log entries not showing on Time Reports
• SUMMARY: Previously when employees had Time entries, when going to Reports > Time Reports – the time was not showing on the report.
After the fix was applied, the time shows correctly on the Time Report
Sprint 34 – Closed
No items for change log
Sprint 33 – Closed
No items for change log
Sprint 32 – Closed
IST-2152 | FD 10045 – Configurable option to not require Drivers to press ‘Pouring’ status
Features Added
• SUMMARY: Previously the iStrada Dashboard showed Totals from NON Mix Items (like Blocks or Aggregate Items) from ConcreteGO or dispatch systems. Some producers include NON mix transactions from dispatch which caused totals to be confusing and not accurate. The change applied will only display price units of m, m3, /y, cy, yd, yd3, otherwise it will not be included in the Dashboard.
Example of Dashboard with Change applied:
Details: The dashboard data aggregations are based on the Order Products Schedules (+ related data) and Tickets data.
Schedules contain information about the plant (used for permission rules) and quantity. A product related to the schedule includes information about the unit.
Schedules are used to calculate qty ordered, and tickets are used to calculate qty loaded/delivered.
The logic in CG and iStrada assumes that each order needs to have at least one mix product item (and schedule).
Customers also use the orders to handle non-mix items by entering non-mix items as mix items.
Technically, it is not possible to recognize reliably if the ordered product is a non-mix item.
Beacuse of that schedules are filtered by the related product price unit. Tickets are filtered by the unit related to the mix item product from the ticket product list.
If a unit of the scheduled product/ticket is NOT one of the following: /m, m3, /y, cy, yd, yd3, it will not be included in the data aggregation/computations.
Units capitalization does not matter. CY and cy will be treated the same way.
A product that should be included in the aggregation must contain information about the unit, otherwise, the dashboard data will be incorrect/corrupted.
IST-2152 | FD 10045 – Configurable option to not require Drivers to press ‘Pouring’ status
Features
• SUMMARY: Added logic for sites to not require iStrada Driver App users to press “Pouring” status. Previously, “Pouring” status was required to trigger next status “To Plant”. This option allows Driver App to transition from “On Job” to “To Plant” without pressing “Pouring” for accurate status when Driver leaves Jobsite GeoFence.
Steps to enable this feature
- In iStrada Web Portal, Go to Settings > Company > iStrada Driver App
- In the iStrada Driver app form click the Edit button
- Disable (unselect) Option “Pouring” status required then click SAVE (NOTE: Selecting option Requires Pouring Status to Trigger “To Plant” When leaving jobsite GeoFence)
Note: Once this option is unselected Driver has option to Press Pouring or NOT press pouring to trigger “To Plant” when leaving jobsite geofence