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.
Table 1 - Smart Form Handover 2 Delivery Schedule
Migration Highlights
During the migration of the Smart Form the following changes were made:
For valid meter serial numbers the meter type, manufacturer, year of manufacture and number of meter dials will be automatically populated for New Meters only
The following Sections and the number of possible repetitions were condensed into Repeating Sections:
PRS Filtration Stream (4)
PRS - PRS Stream (4)
PRS - PRS - Metering Stream (8)
Operational Pressure Settings Stream (4)
Reduction by approximately 50% in JSON file size
Details of all the changes to the Smart Forms above are described in further detail in an update to the Design Documentation available at the following link:
https://docs.google.com/spreadsheets/d/1xWJSbQZ23ugdtZpVkJi30bzmg-8Mzr3-n4BWeHVSDrs/edit#gid=0
The above MEX - Meter Exchange Smart Form may be executed in an identical fashion to the V1 Smart Forms by association to a Work Order.
A test report is available for the MEX - Meter Exchange Smart Form in the following web link:
https://drive.google.com/drive/folders/1kQJJNEkcpCjWdYTjlMR8VeN9vQrpULdP?usp=sharing
Axsy Smart Forms
Managed Packages
V1.46
Sandbox:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1U000007cOdiProduction: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1U000007cOdi
What’s New
Bug fix for upper limit on loops in Repeating Sections
Recent Revision History
v1.45 29/09/21
Bug fix for Repeating Sections selection
v1.44 27/09/21
Performance improvements for Smart Form designers
Bug fix for erroneous error message in Smart Form Preview
v1.43 14/09/21
Compatibility bug fix for loop Element references
v1.42 08/09/21
Compatibility feature for V1 Smart Forms formula evaluation via strict or lenient modes
v1.41 20/08/21
Bug fixes and general improvement
v1.40 19/08/21
Enhancements to broaden flexibility of formula inputs
v1.39 03/08/21
Enhancement to allow whitelisting of salesforce objects to be used with Mapping
v1.38 29/07/21
Further improvements to Smart Form preview
v1.37 23/07/2021
Fix for Smart Form preview feature
v1.36 22/07/2021
Added support for picklist value formula
v1.35 20/07/2021
Added legacy mappings UI setting
v1.34 22/06/2021
Updates to repeated sections feature set
Change over to Lightning Web Components (LWC) Smart Form Designer
v1.33 22/06/2021
Added support for Salesforce Summer ‘21 sobjects
Form Response resilience enhancements
v1.32 16/12/2021
Fix for user permissions for FR location fields
Configuration Options
Object Schema Whitelisting
The Axsy Smart Form Designer includes a lookup tool in the Mapping Syntax Builder to help Smart Form designers in the construction of their mappings. The Mapping Syntax Builder will, as a default, load all the Salesforce objects present in the org into memory to to support mapping lookups.
In orgs where a large number of Salesforce objects are present it may not be possible for the Mapping Syntax Builder to load all of the Salesforce objects into memory and an error message will be shown.
Figure 1 – Mapping Look-up Unable to Load Large Number of Salesforce Objects
Notes:
The schema data error may take up to 30 seconds to be displayed
If the schema data error message is not displayed you do not need to whitelist any objects
Field Mappings may still be entered manually if the object and fields are known even if the schema data error message is shown, please refer to our knowledge article at the following link for details on field mappings:
https://smartformssupport.axsy.com/support/solutions/articles/76000045454-new-mapping-syntax
To accommodate Salesforce orgs that have a large number of objects present, a white list can be used so that only the Salesforce objects necessary in Smart Form construction are loaded into memory, which allows the Smart Forms Designer auto-completion features to function normally.
The white list file must be named: axsy_smart_forms_config.json and is created outside of Salesforce on a workstation computer.
The contents of the file lists the API names of the reference objects to be white listed the format below:
{
"metadataSObjectAllow": ["CustomeObjectAPIName1__c", "CustomObjectAPIName2__C", "StandardObjectAPIName1"]
}
To load the file into Salesforce:
In Salesforce, from the app launcher, search and select Files
Figure 2 – Files
2. Select the Upload Files button
3. Locate and upload the axsy_smart_forms_config.json file on your computer
4. Confirm the file has loaded successfully
Figure 3 – Uploaded the axsy_smart_forms_config.json file
Notes:
When updating the axsy_smart_forms_config.json file with an updated file, the old file must be deleted and only a single file present.
The file axsy_smart_forms_config.json must be manually shared with other Smart Form designers. Select the Share drop down option to add sharing permissions to the file with other designers.
Figure 4 – Sharing the Config File
Smart Forms V1 Compatibility Features
Strict / Lenient Mode Validation Formula Evaluation
Axsy Smart Forms default (and recommended) setting for validation formula evaluation is Strict Mode – i.e., formulas are evaluated for all known implementation errors. For backward compatibility with Version 1 Smart Forms, which does not have the same depth of formula evaluation error checking, Strict Mode may be disabled and a Lenient Mode used instead.
Strict mode may be disabled at Smart Form level by the introduction of the text: "strictFormulaEvaluation": false in the Config formula.
Note: You may need to add the Config field to your page layout.
See the example in Figure 5 below:
Figure 5 – Strict Mode Formula Configuration Disabled (Lenient Mode)
After saving the change the Smart Form must also be published, to do so, double click on any Element in a Smart Form Section, do NOT make any changes to the Element, Save the Element, Save the Smart Form and then Publish the Smart Form.
Draft Import Considerations
When importing draft Smart Forms into an org that has previously had a V1 Smart Form of the same name in the org, this may result in Smart Form Mappings used in V1 that are not required for the newly imported V2 Smart Form.
Check the Related tab for the relevant Smart Form and if there are any Form Mappings then these must be manually deleted.
Figure 6 – Removing V1 Mappings
Axsy Smart Forms V1.46 Known Issues
Jump To Elements cannot be located in a Section in isolation.
The Jump To Element must have at least one other Element (which can be invisible) before it, to enable the Jump To to function.
An example solution is shown in Figure 7.
Figure 7 – Inserting an Element before a Jump To Element to Cause the Jump To to work as Expected.
2. Form Response preview does not show content from empty Sections
When viewing FR content in the Designer FR Preview for Sections that have no FR content causes the FR Preview to white screen. Workaround: reload the Preview to restore normal functionality if this occurs.
3. Form Response preview does not show content from Repeating Sections
When viewing FR content in the Designer FR Preview content in Repeating Sections is not displayed.
The issues above will be resolved in a future update to Axsy Smart Forms
Axsy Field Service (FS) Mobile Apps
The following Axsy FS mobile apps are available:
iOS:
install.appcenter.ms/users/js-axsy.com/apps/axsy-field-service/distribution_groups/public%20accessAndroid:
install.appcenter.ms/users/js-axsy.com/apps/axsy-field-service-1/distribution_groups/public%20accessWindows: App link will be provided later.
Note: The above apps share the same version number as the apps used in the Handover 1 release but must be updated for use with Handover 2. Please verify the date of release: Oct 29, 2021.
What’s New
Flow Navigation Buttons
Axsy has recently introduced navigation buttons for Flow that enable backward and forward navigation of Flows, note the Previous and Next buttons present Figure 8 below.
Figure 8 – Flow Navigation Buttons
Draft Form Response (FR) Content Saved to Mobile App
Axsy Smart Forms save draft FR content to secure storage within the mobile app and, when there is an online network connection, also sync the same draft FR content to Salesforce. If at any time, the size of the draft FR content exceeds approximately 132,000 characters then the draft content can no longer be synced to Salesforce – this can only occur with very large Smart Forms.
If the 132,000 character limit is exceeded, draft FR content is only stored locally in the secure storage of the Axsy FS mobile app. When the Smart Form is completed, the completed Smart Form FR content is synced to Salesforce. Completed Smart Form FR content sizes are much smaller than draft content file sizes and can be readily synced back to Salesforce when there is a network connection. Axsy has not seen any situations where a completed Smart Form FR content exceeds 132,000 characters even with very large Smart Forms.
Usage Limitations
The Axsy iOS and Android FS apps are beta apps made available for testing purposes only and must not be used for production purposes or distributed outside of test teams.
Known Issues
1. Loss of the Close X button in Smart Form Summary view occurs after navigation of summary content. Workaround: navigate to the last Section completed and press the next button to return to the Summary / Submit buttons view.
2. Pressing the submit button rapidly at time of Smart Form completion may cause duplicate content to be sent to Salesforce. Workaround: ensure a single press of the submit button takes place.
3. [iOS only] Picklists that are controlled by another picklist for their content sometimes do not update their controlled values set when the controlling picklist is updated.
4. Elements that have dependent Elements whose default values normally update when the controlling Element is updated, do not always update automatically when complex relationships are present between the controlling and the dependent Elements. Workaround: update the element controlling the dependent element manually until the default is refreshed.
5. An ongoing issue has been identified in the FS Windows app relating to image capture which must be resolved before release for beta testing.
The issues above will be resolved in future Axsy FS mobile apps
Migration Implementation
Meter Barcode Look-ups
Based on the details provided to Axsy in the Excel spreadsheet “Live Models_MSN Checks_v2 I&C (2).xls” Axsy has implemented the derivation of meter fields from the meter serial number. Additionally for meters produced by Actaris, Itron and Schlumberger Industries the following additional logic has been applied based on their year of manufacture:
2000—2002 → Schlumberger Industries
2003—2008 → Actaris
2009+ → Itron
Axsy applied the following changes to the New Meter Details Section to allow for derivation of meter fields from the serial number.
Table 2 – Meter Barcode Capabilities
Except for the invisible Element “Is the Serial Number Valid” all of the above Elements may be manually entered. Valid scanned (via the mobile device camera) or manually entered meter serial numbers will populate the remaining meter fields.
Compatibility of Smart Form Elements to Salesforce Data Types
Axsy Smart Forms V2 requires Smart Form Elements types (text, numeric, etc) to be compatible with the corresponding Salesforce field types they are mapped to. Please see Axsy’s knowledge article at the following location:
Axsy noted that certain Elements were not compatible with their mapped Salesforce fields. Axsy made no changes to the Salesforce data model but did change some Element types so alignment was achieved, this is summarised in Table 3, below.
Table 3 – Modification of Element Types for Salesforce Field Compatibility
BarCode Enablement
Text fields in V2 Smart Forms have the option for barcode scanning entry to be enabled on or off, the default is off. Barcode scanning has been enabled for Elements where a serial number is expected, including Meters, Regulators, Boilers, Heat Exchangers, Water Baths, Electric Heaters, Valves, Filters, Slam Shuts and Creep Reliefs.
Time Dependent Element
Date and Time data fields differ from V1 to V2 forms, accordingly In the Meter By Pass Section, the Element Time meter put on/taken off by-pass has been modified so it works with a 24 hour clock system, the supporting invisible Element datetimenow has also been modified.
Validation Formula Changes
The following changes were made in the Site Section to validation formulas, the changes reflect the length of the Salesforce fields
Table 4 – Validation Rule Changes
Jump To’s
Within the following Sections:
Jump to Job Data; and
Skip Reg Section
an invisible element has been added before the Jump To Element to ensure the Jump works normally, the end-user experience is unaffected.
Use of Non-Unique Salesforce ID’s
Axsy noted in the I&C analysis that some Elements in MEX - Meter Exchange are affected by non-unique Salesforce ID’s, accordingly Axsy performed the migration activities in Lenient Mode.
Unmapped Loops
Elements contained within a Loop adopt the mapping specified for the Loop. During the migration Axsy noticed Elements with mappings contained within Loops that had no mappings. The net result of which is the Element mappings would not function. Smart Forms V2 will not accept mapped Elements within Loops that have no mapping configuration, therefore Axsy removed the mappings from the Elements listed in the table below.
Table 5 – Unmapped Sections containing Elements with Mappings
Essential Salesforce Field Permission Changes
The fields listed below had ‘Hidden’ permissions which Axsy changed to be Editable in the FFABIT and FFATEST orgs.
Table 6 – Essential Permissions Changes
Axsy recommends these fields are verified in any org used for testing prior to attempting to run the MEX - Meter Exchange Smart Form.
ISBLANK Correction
Smart Forms V1 uses an incorrect application of the ISBLANK expression, this has been corrected in the migrated V2 Smart Forms. Close inspection of the formulas previously using ISBLANK may be required to detect these changes.