Panel | |
---|---|
On This Page:
|
Include Page | ||||
---|---|---|---|---|
|
About this Release
This release adds some existing new functionality to the mobile application with the new Flex-Forms capabilities. The Mobility ESB has been greatly enhanced with numerous new REST APIs.
- Mobility
- Support for BlackBerry OS 10+
- New Flex-Forms
- New Flex-Form Rules
- Activities now Support Flex-Views
- Enhanced pricing with support for discounts, credits and deposits
- Job estimates
- Process flow optimizations and improvements
- ESB
- New WorkCenter REST API
- New WorkCenter Query REST API
- New v3 Bulk User Import REST API
- New Users REST API
- New Users Query REST API
- New Storage Location Query REST API
- Auto creation of storage locations
- Updated Existing REST API to support Flex-Forms
- Bug Fixes
- Unicode character support in ServiceCodes, FlexAttributes and System Categories
- Web Management Portal
- Updated based on enhancements to REST APIs and new functionality
Include Page | ||||
---|---|---|---|---|
|
Mobile Application Release Notes
New Features
Status | ||||
---|---|---|---|---|
|
ServicePower is pleased and excited to announce our support of BlackBerry devices running OS 10+.
Note |
---|
While ServicePower now supports BlackBerry OS 10, older BlackBerry devices with lower end CPUs may run the application more slowly. Please contact ServicePower to discuss your specific BlackBerry requirements. |
Status | ||||
---|---|---|---|---|
|
The ServiceMobility application now provides order level discounts. Discounts are percentage based, applied before taxes and can be restricted to specific line item types. For example, apply a 10% discount on travel charges; apply 15% senior citizen discount on all parts. Each order can have zero or more discounts.
- The
Order Summary
andOrder Totals
screens have been updated to support displaying discounts - The PDF Invoice has been update to included new sections for discounts
- If the work order does not contain any discounts then the discount lines will not be displayed
Order Summary Screen showing total discounts
Order Totals Screen Showing Discounts
Status | ||||
---|---|---|---|---|
|
A work order can now be configured to collect a deposit from the customer when parts must be ordered and a return trip is required. A deposit can either be a fixed amount, a percentage of the total ordered amount or both. If both options are specified, then the higher of the two values will identify the required deposit.
- The
Order Summary
andOrder Totals
screens have been updated to support displaying deposits - The PDF Invoice has been update to included new sections for deposits
- If the work order does not contain any deposits then the deposit lines will not be displayed
Order Summary Screen Showing Deposits
Order Totals Screen Showing Deposit
Status | ||||
---|---|---|---|---|
|
Work orders now support zero or more credits. Credits are fixed dollar amounts that are applied to the work order after taxes. Each credit contains a description of the credit being applied.
- The
Order Summary
andOrder Totals
screens have been updated to support displaying credits. - The PDF Invoice has been update to included new sections for credits.
- If the work order does not contain any credits then the credit lines will not be displayed.
Order Summary Screen Showing Credits
Order Totals Screen Showing Credits
Status | ||||
---|---|---|---|---|
|
The Activities module now supports the use of Flex-Views
Status | ||||
---|---|---|---|---|
|
Note |
---|
Starting with this release, all Flex-Fields must be associated with a Flex-Form. |
Flex-Forms are a new ServiceMobility capability that extends the usefulness of Flex-Fields. A Flex-Form definition consists of a description and one or more Flex-Fields grouped into one or more sections. Existing Flex-Field definition can be used with Flex-Forms. All of the rules defined by the Flex-Field, for example a field being required, are still enforced by the Flex-Form runtime. The real benefit to Flex-Forms is that more than one form can be associated to any area of the application where they are supported.
Prior to Flex-Forms, Flex-Fields provided a way to collect additional information at key areas within the application. For example, under the Work Order module there was a screen called Form, however this screen was simply a collection of Flex-Field definitions and did not support the concept of groups fields or multiple distinct forms.
FlexForms are now available in the following locations:
- Work Order Module
- At the work order level
- Assets sub-module
- Tasks sub-module
- Activities
- Inventory Transfer Module
- Time Entry Module
Example of Two Collapsed Forms
Example of an Expanded Form
Flex-Form Rules Status colour Green title new
Note |
---|
Flex-Form Rules are in an early stage and currently require the assistance of the ServicePower Consultant group to properly configure. ServicePower is working on a web based visual rule designer that will allow the customer to create and maintain their own rules. |
Flex-Form Rules are a very exciting new enhancement to the mobile application. With Flex-Form Rules you can define external rules that determine if a field is visible, if it is required and if a field is valid. Flex-Form Rules can use the values of other Flex-Form fields or values from the current running business process. For example, if an RMA Form is created, its visibility and requirement to be filled in can be controlled by specific items being returned on the work order.
The real benefit of the rules is that they allow your business to inject custom business logic based on your own internal processes while staying on an existing upgradable product.
Application Changes
Status | ||||
---|---|---|---|---|
|
We continue to improve the usability of ServiceMobility by reducing the number of screens and clicks required for a user to edit a field. To this end, we have introduced more inline editing capability within the application.
Status | ||||
---|---|---|---|---|
|
The start and end times have been separated into two distinct edit fields that are now edited in-line. This eliminated one entire screen from the process flow.
Status | ||||
---|---|---|---|---|
|
The mobile application logging has been improved to provide additional details. This information will assist ServicePower in tracking down future issues.
Resolved Issues
A Work Order with a Long Description Without any Spaces Caused UI Rendering issues Status colour Red title fixed
If a work order contained a very long description without any spaces, the application's default word-wrapping logic would not work. This caused the UI to auto expand pushing buttons off-screen and making them unreachable. This issue has been resolved.
Deleted Activity was not Removed from Device Status colour Red title fixed
Resolved an issue where, at times, a deleted Activity was not being removed from the mobile device.
Uploading Transactions out of Order Status colour Red title fixed
A bug was found and resolved that, under specific conditions, could cause the order of uploaded transactions to be out of order (not in the order they were created). Even if the transactions were uploaded out of order it would only cause an issue if all of the transactions were for the exact same object.
Toolbar Icons not Correct after Application Update Status colour Red title fixed
Resolved and issue where after an application update the toolbar icons were not correct.
ESB Release Notes
New Features
This release brings a number of new REST APIs to ServiceMobility
- Updated Existing REST API to support Flex-Forms
- System Catagories
- Bug Fixes
- Unicode character support in ServiceCodes, FlexAttributes and System Categories
Status | ||||
---|---|---|---|---|
|
This release includes a v3 implementation of the User Bulk Import REST API with the following capabilities:
- Supports both JSON and XML data formats
- Additions to the data model
DGroupID
- The deployment group ID can now be specified for each user during bulk loadExtensions
- The Extensions object is now available during bulk loading
The old v1 REST API still exists and has not changed.
Status | ||||
---|---|---|---|---|
|
A new WorkCenter REST API has been created to manage work centers.
Status | ||||
---|---|---|---|---|
|
A new WorkCenter Query REST API has been created to run queries against all work centers.
Status | ||||
---|---|---|---|---|
|
A new Users REST API has been created to manage individual users.
Status | ||||
---|---|---|---|---|
|
A new Users Query REST API has been created to run queries against all users.
Status | ||||
---|---|---|---|---|
|
A new StorageLocation Query REST API has been created to run queries against all storage locations.
Application Changes
Status | ||||
---|---|---|---|---|
|
When creating a new User or Location, if the assigned storage location identifier does not exist the system will automatically create it.
Status | ||||
---|---|---|---|---|
|
The following existing REST APIs have been enhanced to support the new Flex-Forms capabilities:
- Activity REST API
- Inventory Transfer REST API
- SystemCategories REST API
- WorkOrder REST API
- Time Entry Related REST APIs
Resolved Issues
Status | ||||
---|---|---|---|---|
|
There is an issue where a technician who was originally assigned and dispatched a work order (Tech-A) makes status changes to the work order while offline (e.g. disconnected from the network). While Tech-A is still offline, the work order is reassigned to a different technician (Tech-B). Tech-B begins making updates to the work order and uploading them to the system. Eventually Tech-A reconnects to the network and begins uploading the cached work he has completed which then might overwrite the status changes made by Tech-B.
In the above scenario the ESB will ignore updates from Tech-A when he is no longer the technician assigned to the work order.
Web Management Portal Release Notes
Application Changes
Status | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|