...
| Case # | Description |
|---|---|
| MTW-2460 | If you would prefer the inspection report to be sent in the next sync after creation (instead of when the appointment is completed) then you can continue to do so by setting up Resco Cloud's organization email. See Set Up Organization Email in Resco Cloud (optional). You will also need to create a Resco process for each Inspection template that you want to send an automatic email. For more information about creating a process, see Resco's Wiki: https://docs.resco.net/wiki/Process. Please contact Key2Act contactWennSoft Support for help with setting up the process(es). |
...
| Case # | Description | ||
|---|---|---|---|
| MTW-2448 | When opening a task form after searching the task list that has at least 2 task lists with 2 different sublocations, users can now use the forward and back buttons to navigate between the taskstask forms. | ||
| MTW-2451, MTW-2467, MTW-2469 | Time entries are no longer removed from devices and the middle tier. The delete constraint has been updated from "No Action" to "Remove Link". | ||
| MTW-2453 | Users will no longer receive the FormsRule error when attempting to complete an appointment after upgrading. | ||
| MTW-2455 | After enabling an existing (or new) employee/technician as a TimeTrack user and then running the Integration Sync, users will no longer receive the error "The given attribute 'positionid' was not present in the entity metadata." | ||
| MTW-2457 | After enabling a TimeTrack user who is an employee but not a technician and then running the Integration Sync, users will no longer receive the error message "InnerExceptionMessage: Object cannot be cast from DBNull to other types." | MTW-2472 | When using Equipment Management Schedule Maintenance to create a new service call, users will no longer receive a MobileTech trigger error message. |
| MTW-2474 | When using Travel TimeLog (and roundInitialTimeInOut = true, gptimein and gptimeout ) are now rounding will no longer round to the same time on the 15-minute rounding, as expectedvalue if travel is started and stopped before the next TimeLogRoundingInterval. The timeout value will automatically be rounded up to the next rounding value. For example, if TimeLogRoundingInterval = 15 and Travel begins at 8:31 AM and ends at 8:36 AM, the gptimein and gptimeout should be rounded to 8:30 AM and 8:45 AM respectively. | ||
| MTW-2478 | Auditing is no longer enabled by default in the MobileTech Woodford project for using Sync Dashboard. (This had been enabled with the MobileTech 9.0 release.) For information on manually enabling Auditing, see Using Sync Dashboard (optional). |
...