Summary
The following Smart Forms have been migrated by Axsy from V1 to V2 format and are available in the FFABIT org as draft format Forms and the FFATEST org as version format Forms.
The above Smart Forms may be executed in an identical fashion to the V1 Smart Forms by association to a Work Order.
Test reports are available for each of the above Smart Forms at the following web link: https://drive.google.com/drive/folders/1Gt8viJ5PO10gi0cs4oGEP55pY8EzJdwr?usp=sharing
Updates to Previous Handovers
In addition to the above Smart Forms included in Handover 3, updates have also been made to Smart Forms that were included in previous Handovers.
Handover 1: Details of the changes to the Smart Forms originally delivered in Handover 1 are available here: Handover 1 - Update 19-Nov-21
Handover 2: Changes to the Smart Form originally delivered in Handover 2, i.e. MEX - Meter Exchange, are listed below with more details available in the Migration Implementation section:
Consolidation of multiple Picklist Elements in the New Meter Details and Current Meter sections into a single picklist through support of Dynamic Picklists with Two Controlling Variables
Configuration of specific Elements to have Mapping Override Default Values
Other minor changes may also be included as a result of updates to Handover 3 Smart Forms that share sections with MEX - Meter Exchange
Axsy Smart Forms Managed Packages
V1.47
Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1U000007smnv
Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1U000007smnv
What’s New
Bug fix to address Form Response viewer showing as blank under some circumstances
Axsy Field Service Mobile Apps
The following Axsy Field Service Mobile Apps are currently available. These are the same patch release apps shared previously:
Known Issues
The below known issues are in the app builds above and will be addressed via a new Axsy Field Service Mobile App build to be delivered as part of Handover 4.
Usage Limitations
The Axsy iOS and Android Field Service Mobile Apps are Beta apps made available for testing purposes only and must not be used for production purposes or distributed outside of test teams.
Migration Implementation
Dynamic Picklists with Two Controlling Variables
Overview
Previously, Axsy Smart Forms only supported dynamic picklists that could have a single controlling value
Since the picklist for Meter Model depends on both the selected Meter Type and Meter Manufacturer, implementation required using multiple Meter Model picklists all controlled via Visibility Formula based on the type and manufacturer
With Handover 3, the Meter Model picklist now supports dynamic picklists that can include two controlling values
This makes it possible to consolidate the Meter Model picklist into a single Form Element
Affected Sections and Elements
Implementation Details
Create a Lookup Table with Column Header values that contain the picklist values of the 1st controlling picklist, and Row values that contain the picklist values of the 2nd controlling picklist
Add picklist values separated by a delimiter of your choice into the cells of the table - in the screenshot below, it is ‘,’
Create a 3rd picklist that will display the output of the two controlling picklists
Navigate to the Picklist tab of this 3rd picklist and enter the formula SPLIT(LOOKUP_TABLE_NAME(ColumnHeaderControllingPicklist, RowHeaderControllingPicklist), ‘delimiter’) into the Value Formula field.
NOTE #1: The Form Designer will display an error for the SPLIT function. This can be safely ignored as it is supported in the Form Engine and works in the mobile app.
NOTE #2: Leave the Picklist value empty under the Picklist tab.
Mapping Override Default Values
Overview
Per design, the presence of a Default value on an Element will always override the presence of a Mapped value to that Element
By “pairing” an existing Element with a new, always hidden Element, which is then referenced in the Default value formula for the existing Element, it is now possible to effectively have non-empty Mapped values from Salesforce override any Default value
Affected Sections and Elements
Implementation Details
If Element1 represents the existing Element where a mapped value should override a default value...
Create a new Element, i.e. Element2, that contains the same mapping as Element1 under its Mapping tab
Make sure Element2 is always hidden under its Visibility tab by setting it’s visibility formula to true
Navigate to the Defaults tab for Element1 and update its existing Default formula by adding IF(ISNOTBLANK(Element2), Element2 as the first part of the default formula. The “else” part of the formula is what was originally intended as the default formula.
Salesforce Field Permission Changes
The fields listed below had ‘Hidden’ permissions which Axsy changed to be Editable in the FFABIT and FFATEST orgs.
Axsy recommends these fields are verified in any org used for testing prior to attempting to run the MEX - Meter Exchange Smart Form.