ServiceMax Suite of Applications List of Fixed/Known Defects

Transcription

1 of Applications List of Fixed/Known Defects Copyright 2016 ServiceMax, Inc. All Rights Reserved. Designated trademarks and brands are the property of their respective owners.

2 Fixed Issues For : SMX SMX SMX SMX Summary: App crash while saving signature for a report Details: App was crashing while saving a large signature during generation of report. Summary: View process of source record not refreshed after source object update Details: View process of source record was not showing updated results after performing source object update while creating a new record from this source record. Summary: Data sync gets stuck frequently Details: Data sync got stuck frequently and user had to relaunch the app or peform reset app. Summary: SFM Search results not showing expected values Details: SFM search results was showing incorrect value if the display field belonged to other objects instead of the same object on which search was configured. for Android Signature Capture for Android Source object update for Android Data sync for Android SFM Search d on d on d on d on Report generated on 12:37 PM GMT Page 2 of 17

3 For : SMX SMX SMX SMX Summary: SFM Search not working as expected Details: SFM search was returning incorrect data if search was configured on date and datetime fields. for Android SFM Search Summary: Wrong datetime display in Work Order Summay field Details: The datetime field info showed for Android empty value or incorrect date in Work Order's Datetime fields summary section. Summary: Lookup search not showing expected results Details: Lookup search was not returning the expected results if Lookup Context was configured. Summary: Failure entries getting created in Sync log reports Details: Failure entries were getting created in Android sync log reports even if data sync was successful. for Android Lookup search for Android Sync reports d on d on d on d on Report generated on 12:37 PM GMT Page 3 of 17

4 For : SMX SMX SMX SMX Summary: Longer sync time issue Details: Sync took longer time if setting to capture sync job logs was enabled. Summary: App crash during data sync Details: If logged in user's event was re-assigned to a different user online and if data sync was triggered, then app was crashing during this sync. Summary: Source object update not working as expected Details: Source object update was not working as expected if checkbox and date fields of source record were updated. Summary: SFM Search not working as expected Details: SFM search was returning incorrect data if search was configured on date and datetime fields. Data sync Data sync Source object update SFM Search d on d on d on d on Report generated on 12:37 PM GMT Page 4 of 17

5 For : SMX SMX SMX SMX Summary: Unable to log into ipad classic app in Sandbox environment Details: User was not able to login into ipad Classic app in sandbox environment. On tapping 'Allow', user was redirected back to login page. Summary: Pulse app crashed after login Details: Pulse app crashed after login if Servicemax notifications were selected and if the region was set to EU in Pulse configuration. Summary: SFM Search returned incorrect results Details: SFM search was returning incorrect data if search was configured on lookup field. Summary: Sorting not working as expected in Output Documentation Details: Sorting was not working as expected if the page layout on which sorting was configured did not have any qualifying criteria. User login User login SFM Search Smart Documents d on d on d on d on Report generated on 12:37 PM GMT Page 5 of 17

6 For : SMX SMX SMX SMX Summary: App crash during data sync Details: If logged in user's event was re-assigned to a different user online and if data sync was triggered, then app was crashing during this sync. Summary: Online SFM Search results show wrong data Details: The datetime fields from the results of online SFM search showed incorrect value. Summary: Data sync failure in iphone app Details: Data sync failed in iphone app if data sync took more time than the device's auto-lock timeout value. Summary: Datetime fields show wrong time in 24 hours format Details: Datetime fields in SFM view and edit process were showing incorrect time if device's 24 hr format setting was enabled. Data sync Online SFM Search Data sync Datetime fields d on d on d on d on Report generated on 12:37 PM GMT Page 6 of 17

7 For : SMX SMX SMX SMX Summary: App crash if user taps on Actions in View process page multiple times Details: If user opened any record from Calendar and tapped on Actions (and repeat these steps mulitple times) and put app in backgorund, then app was crashing when it was launched from background mode. SFM Wizard Summary: App crash during data sync Details: If logged in user's event was re-assigned to different user online and if data sync was triggered, then app was crashing Data sync during this sync. Summary: SFM Search not working as expected Details: SFM search was returning incorrect data if search was configured on date and datetime fields. Summary: Data validation rules not working as expected Details: Data validation rules were not working as expected in some timezones if datetime fields were used. SFM Search Data validation rules d on d on d on d on Report generated on 12:37 PM GMT Page 7 of 17

8 For : SMX SMX SMX SMX Summary: Data purge not working as expected Details: Data purge was removing the data which was part of download criteria. Summary: Datetime fields show wrong data and SFM formula not working as expected Details: If device locale was set to Dutch, then datetime fields were showing wrong data. Also, SFM formula was returning wrong results for datetime fields. Summary: Record update fails if updated mulitple times Details: If a record was created and updated mutiple times continously, then some of the data was getting lost. Summary: Duplicate records are created if data sync fails Details: If records were created and synced to server from app and if this sync was interuppted, then duplicate records were getting created in next data sync. Data purge SFM Formula Data sync Data sync d on d on d on d on Report generated on 12:37 PM GMT Page 8 of 17

9 For : SMX SMX SMX SMX Summary: Unable to enter decimal point in Checklist answers Details: User was not able to enter decimal value while answering Checklist questions if answer type was numeric. Summary: Address info missing in Service report Details: If service report was generated in MFL, then address info was not displayed in the report. Summary: SFM Wizards not loading as expected Details: The SFM Wizards were not shown properly based on the criteria if includes/excludes operators were used. Summary: SFM Search results not showing expected values Details: SFM search results was showing incorrect value if the display field belonged to other objects instead of the same object on which search was configured. Checklist for Laptops Smart Documents for Laptops SFM Wizard for Laptops SFM Search d on d on d on d on Report generated on 12:37 PM GMT Page 9 of 17

10 For : SMX SMX SMX SMX Summary: Datetime fields show wrong time if timezone is set to time zone: UTC-4-Santiago Details: Datetime fields in SFM edit process were showing time subtracted by an hour when timezone was UTC-4-Santiago Summary: Field mapping and SFM Formula not working as expected Details: Field mapping and SFM formula were not working as expected if both configuration had same fields for a SFM process. Summary: User unable to login in MFL if there's no network connection Details: If MFL app was kept idle for a day, and if user tried to login the next day when there was no internet connectivity, then login fails and user wasn't able to use the application. Summary: SFM Search not working as expected on number fields Details: SFM search was returning incorrect data if search was configured on number fields. for Laptops Datetime fields for Laptops SFM Formula, Field mapping for Laptops User login for Laptops SFM Search d on d on d on d on Report generated on 12:37 PM GMT Page 10 of 17

11 For : SMX SMX SMX SMX Summary: Dispatch console event load is slow on Gantt Details: Refresh of large number of events with wider date horizons used to take more time and also Dispatch console used to show the Shockwave Flash not responding error sometimes during this command. An option to overcome this has been provided in Autumn 17 release through an enhancement of loading events only for technicians in expanded teams/territories. Dispatch Console Summary: The event dialog displays "None" value in picklist field when not expected Details: When a picklist field is configured to have a default value and is mandatory, then Salesforce visual force page does not display Dispatch Console "None" value in the picklist. But "None" value was being displayed for the picklist field in the event dialog in Dispatch console. Summary: Visual Force error: Maximum view state size limit (135KB) exceeded Details: In some specific orgs where the number of Objects and Fields are large in number, the Salesforce view state size limit exceeded error was reported while accessing the "Event subject rule" page in Servicemax setup. Summary: Unable to disable chatter feature after upgrading the org to Winter 17 Details: It was not possible to disable chatter feature in an org that was upgraded to Winter 17. This dependency has been removed in Autumn 17 release. Dispatch Console Dispatch Console d on d on d on d on Report generated on 12:37 PM GMT Page 11 of 17

12 For : SMX SMX SMX SMX Summary: Non work order events do not respect the default color setting Details: Non work order events created for Technicians with associated Salesforce user were using the colour coding rule defined for "Related to other objects" instead of "Default". This was a regression caused in Win 17 release. Summary: Few operators are not available in eligibility tab of configure ATS panel Details: The following operators are now available in the eligibility tab of configure advanced technician search panel - Greater or Equal To, Greater Than, Less or Equal to, Less Than Dispatch Console Dispatch Console Summary: Not all work orders within the defined radius are plotted on the map in DC Details: When the "Unit of measure to plot on map" setting SET055 (Module:Dispatch Management, SubModule:Dispatch console Dispatch Console flex) was set to miles, then in some cases work orders were not plotted on the map even if they were within the specified radius. Summary: Country Code in Work Order is misspelt Details: Country code for Azerbaijan and Kazakhstan in Work Order were mis-spelt. This is now corrected and will reflect in new installations. For existing installations, corrections have to be made manually. Work Order d on d on d on d on Report generated on 12:37 PM GMT Page 12 of 17

13 For : SMX SMX SMX SMX Summary: All record types are displayed in Details: In, all record types including the ones that are not active were displayed in SFM Delivery page. This is now corrected to show only the record types that are active and assigned to the logged-in user's profile Summary: Tab Key does not work after Date Type field in SFM Line Item Details: Filed navigation using Tab key was not working. Issue is fixed allowing user to access all the available fields in both header & child lines using Tab movement. Summary: SFM Transaction delivery page displays error with Data Validation Rules Details: In a scenario where the overall length of the data validation rule messages exceed 4000 characters, SFM transaction delivery displayed an "Undefined" error. Online SFM Delivery: Edit Process This is now fixed. SFM transaction delivery can handle any number of characters in the Data Validation rule messages. Summary: Error on performing entitlement check when there were large number of IB records Details: Error when performing entitlement on Work Order record if there are large number of child Installed Base records related to the IB of the Work order in the org. Error details : SVMXC:Too many SOQL queries: 101 An unexpected error has occurred. Your solution provider has been Check Entitlement notified. (SVMXC)' error is received when clicking the Check Entitlement SFM from a WO with related Work Detail records. Debug logs for this issue point to the SVMXC.EVER_Entitlement managed Apex Class. This is now fixed. d on d on d on d on Report generated on 12:37 PM GMT Page 13 of 17

14 For : SMX SMX Summary: SLA clock does not work if the SLA Term has only "Resolution" configured Details: If SLA term has only "Resolution" type of commitment configured and such a term is used on a Work order or record, the SLA clock did not count down. This is now fixed. Summary: Price calculation fails when there are too many records in Service Price Book Details: Price calculation fails with Salesforce governor limit error when there are more than 50,000 records in Service Price Book. Error : "System.LimitException: SVMXC:Too many query rows: 50001". This happened because Service Pricebook entries were queried only based on "Activity Type". SLA Clock Get Price d on d on SMX SMX This is now fixed by is optimizing the query to include "Activity Product" in the filter to make it more specific. Summary: SFM transactions take a very long time to load Details: SFM transactions took more time to load due to payload size being more than Online SFM 5MB and was not allowed to store in browser Delivery: Edit cache. As part of this fix we store response by process each field value instead of all fields in one single key. Summary: Duplicate contracts or warranties are displayed in a specific scenario Details: In a scenario where the Parent IB, Top Level IB and Child IB were covered by same Service Contract, entitlement check showed the same Service contract multiple times. This is now fixed. Check Entitlement d on d on Report generated on 12:37 PM GMT Page 14 of 17

15 For : SMX SMX SMX SMX Summary: User interface Issue when loading Linked SFM's Details: The delivery page scroll to the bottom showing blue screen instead of showing the invoked linked process from details line. Scrolling is handled to show process page layout on load. Summary: Target object update does not work when service report is generated Details: In a scenario where the logged-in user's profile does not have "Create" permission on the object, Target object update fails when Service Report is generated. This is now fixed and target object update will work if the user has "Edit" permission on the object Summary: Output Document Template Designer adds additional HTML tags in specific scenario Details: Output Document Template Designer adds additional tags ( <p> </p>) lines at the top of the source code when "meta" tags are used in source. This is now fixed Summary: All record types are displayed in Details: In, all record types including the ones that are not active were displayed in SFM Delivery page. This is now corrected to show only the record types that are active and assigned to the logged-in user's profile Online SFM Delivery: Linked SFM Smart Documents Smart Documents d on d on d on d on Report generated on 12:37 PM GMT Page 15 of 17

16 For : SMX SMX Summary: Smart document generation usability issues Details: Finalize button was enabled when smart doc page was loading which led to usability issues if the report was finalized before page load. As part of the fix the Finalize button will get enabled on complete page load. Online SFM Delivery: Smart Documents Summary: Error in SFM transaction delivery when webservice is configured Details: SFM transaction delivery displays an error when Webservice is configured on the Before Save/Insert Event. Error : An unexpected internal error occurred. Please report this to your ServiceMax administrator.::server Error=> There is no registered serializer for the type java.util.linkedhashmap Error Id: ( ) d on d on SMX SMX This is now fixed Summary: Error in SFM transaction delivery when webservice is configured Details: SFM transaction delivery displays an error when Webservice is configured on the Before Save/Insert Event. Error : An unexpected internal error occurred. Please report this to your ServiceMax administrator.::server Error=> There is no registered serializer for the type java.util.linkedhashmap Error Id: ( ) This is now fixed Summary: Checklist status label translation Details: It was not possible to translate checklists status labels. Now all Checklist related labels are driven through Tags and are translatable. Online SFM delivery:checklist d on d on Report generated on 12:37 PM GMT Page 16 of 17

17 For : SMX SMX Summary: Source Object updated fails in SFM Transaction Delivery screen Details: In a scenario where the logged-in user's profile does not have "Create" permission on the source object, Source object update fails on saving record from SFM Transaction Delivery screen This is now fixed and target object update will work if the user has "Edit" permission on the source object being updated Summary: Source Object updated fails in SFM Transaction Delivery screen Details: In a scenario where the logged-in user's profile does not have "Create" permission on the source object, Source object update fails on saving record from SFM Transaction Delivery screen. This is true for Checklists too. d on d on SMX This is now fixed and target object update will work if the user has "Edit" permission on the object being updated. Summary: Spinning wheel due to null value being mapped Details: Spinning wheel displayed infinitely Online SFM on adding a new line. This issue is handled by Delivery: Edit performing null check on the value being process mapped while adding a new line added. d on Report generated on 12:37 PM GMT Page 17 of 17