Asset 360 Releases > Asset 360 Engage Release Notes > Important Considerations and Known Issues
Important Considerations and Known Issues
The following table lists the known issues.
Known Issue
Target Fixed
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.
The admin creates a configuration from Setup Home > Feature preferences > Create new config and saves the config without navigating to the Location tab.
The fields configured under Location details are not displayed in the Location Details screen in the Engage app while creating a Data Update for Location.
Resolution:
The admin must navigate to the Location tab and click save after creating a config in Feature preferences.
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.
If an Asset or a Location chat window is active, the other Push Notifications are not received.
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.
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.
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.
SFDC events must be public to see appointments, or the users should be added as attendees in the event.
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.
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 is distorted on Android phone on 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, then the user receives only one broadcast message in the Notification inbox. Zinc treats it as a single message.
Some of the 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
Asset
Account
Location
Parent Asset
Contact
Install Date
Product
Serial Number
Status
Location
Parent Location
Visitor Address
Location Type
WorkOrder
Asset
Description
Location
Work Type
ServiceAppointment
Scheduled Start
Scheduled End
Subject
Status
Parent Record
Was this helpful?