Release Notes > ServiceMax Mobile Releases > ServiceMax Engage Releases > Engage 1.8 > Important Considerations and Known Issues
Important Considerations and Known Issues
The following table lists the known issues.
Known Issue
Status
Engage app does not support the Number field decimal notation.
Resolved
Issue:
Incorrect fields are displayed in the Engage app for the Location Data Update requests.
When creating a new Feature Configuration for a given Profile, if the admin does not review and save location field settings, and saves the Feature Configuration, then a blank layout is applied to the Feature Profile and fields are not displayed in the Engage App.
Recommendation:
The admin must always review the layout configuration for Location and Asset when creating feature profiles. This ensures that the current config is loaded into the Admin UI before saving.
Issue:
An error message is displayed when users access Reports for Product Object.
Resolution:
This is a Salesforce behavior. Create reports on Installed Products or Asset objects with a custom report type.
For more information, see Salesforce Help.
1.6
Issue:
Unable to search for records in Find An Asset from Quick Links in the Overview tab.
Resolution:
Clone the profile in the target org. Do not use the change set to copy the profile settings.
For more information, see Salesforce Help.
1.6
Issue:
Currently, you cannot delete the request configuration. You can mark them as inactive. The archive requests feature is scheduled for the next patch release or the major release of the server package.
Resolution:
If you want to delete the configuration data, you can remove the record from the EG__SME_Custom_Request_Details__c object.
1.5
Issue:
A change in the Experience Site name or the SFD Profile name after creating a configuration in Engage currently breaks the configuration for Asset Templates.
Resolution:
Update Developer Name SVMXEG__SME_Developer_Name__c in SVMXEG__SME_Configuration__c to reflect the updated Site or Profile Name.
1.5
The other Push Notifications are not received if an Asset or a Location chat window is active.
Preferred Window object: When you edit a Customer Request to delete the Preferred Window and save it, the Customer Request is not saved. The delete permission must be manually added to the Preferred Window object.
iOS Devices: Image annotation is retained after the CR creation is canceled.
Resolved
The object SVMXEG__SME_User_Activity_History__c introduced for Recent user activities in the 1.2 version is not included in the later version of the app. The following message is displayed: 'SVMXEG__SME_User_Activity_History__c\' is not supported.
Resolved
The splash screen on Engage presented on the Login screen resolves to a URL instead of displaying the text.
1.2
Date Installed in Update Service Request View does not display based on locale.
1.2
Location or Asset Name is not displayed on Google Native Map for Android devices.
Cause: Google Maps version 10.11
Future
The Branding Tab in Admin UI does not respond in the Incognito Mode of Chrome browser.
Future
Android 11: Adding Videos directly from Google Photos App is not currently attached during customer request creation.
Future
Scan To Text is undergoing continual improvement. As such specific scan-to-text scenarios may present issues; please send feedback within the app with examples as we improve this feature.
Resolved
If Enable Secure Static Resources for Lightning Components is enabled, some LWC components do not render in Admin UI (such as the Notifications Messages Tab). For more information, see Salesforce Help.
The recommendation is to disable the setting.
SFDC Winter '22
Custom fields are not displayed for the location details of the assets.
1.2
The start date and end date are distorted on Android phones for multi-day appointments.
1.2
The Customer Request Icon in the Asset details screen is always enabled, although Admin UI configuration is disabled.
1.2
The following lists are the limitations:
Push Notifications are not currently supported for reporting Missing Assets.
Engage app does not support dark mode with Android 10.
When the Engage user subscribes to two channels and both channels are the recipients of a single broadcast message. The user receives only one broadcast message in the Notification inbox. Zinc treats it as a single message.
The following Standard object fields as part of the Engage Standard Permission Set are not applied in the locked package. This is a Salesforce limitation.
Ensure that the Users have permission for the following standard fields used in Engage.
Account
Parent Account
Shipping Account
Contact
Account
Email
Phone
Name
Product
Family
Was this helpful?