ServiceMax Release Notes ServiceMax Spring 15 SP (Jun, 2015)

Transcription

1 ServiceMax Release Notes ServiceMax Spring 15 SP (Jun, 2015) (Reposted on Dec 31st, 2015) ServiceMax, Inc Hopyard Rd, Suite 300, Pleasanton, CA Note: Any unreleased features referenced in this release notes, other press releases, or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available. Copyright 2015 Copyright ServiceMax, 2011 ServiceMax, Inc. All Rights Inc. Reserved. Designated trademarks and brands are the property of their respective owners.

2 ServiceMax Spring 15 SP Release Notes About ServiceMax Release Notes This document provides a brief summary of enhancements, modifications, and resolved issues in the ServiceMax Spring 15 release of the ServiceMax suite of applications. It includes Brief, high-level description of the functionality Key setup information Best practices to ensure your continued success Reference to detailed help documentation as applicable The release notes also identify all other changes and provide details about how those changes might affect your organization. Resources and Links You can find out how to set up, upgrade, and use the ServiceMax Suite application at Training and Webinars ServiceMax offers extensive training and posts videos in ServiceMax Community for the ServiceMax Suite application. To sign up for or to receive information about our training services, contact training@servicemax.com. Page 2 of 29

3 Release Notes ServiceMax Spring 15 SP Table of Contents About ServiceMax Release Notes... 2 Release Notes Changes... 4 What s New in ServiceMax Spring 15 SP?... 5 Spring 15 SP Feature Summary and User Impact... 6 Backward Compatibility Matrix... 7 ServiceMax Suite... 8 ServiceMax Spring 15 for ipad Issues fixed in this release Known Issues/Limitations Upgrade Instructions Appendix Page 3 of 29

4 ServiceMax Spring 15 SP Release Notes Release Notes Changes December 31st, 2015 Added section ServiceMax Spring 15 for ipad Version Added section ServiceMax Spring 15 for iphone Version December 2nd, 2015 Added section ServiceMax Spring 15 for ipad Version September 14th, 2015 Added section ServiceMax Spring 15 for iphone Version September 2nd, 2015 Added section ServiceMax Suite Version Added section ServiceMax Mobile Issues Fixed in ServiceMax Server Version Added section ServiceMax Spring 15 for ipad Version Added section ServiceMax Mobile For Laptops Version August 5th, 2015 Added section ServiceMax Suite Version Added section ServiceMax Spring 15 for ipad Version Added section ServiceMax Mobile For Laptops Version July 10th, 2015 Added section ServiceMax Suite Version Added section ServiceMax Spring 15 for ipad Version June 19th, 2015 Added section ServiceMax Spring 15 for ipad Version Added section ServiceMax Mobile For Laptops Version June 5th, 2015 First version Page 4 of 29

5 Release Notes ServiceMax Spring 15 SP What s New in ServiceMax Spring 15 SP? The Spring 15 SP release of ServiceMax includes some important enhancements to features and apps. The highlights of this release are: Translations Update for all the eleven supported languages Translated picklist field values in Smart Docs Covered Product as the target header object in SFM transactions Dispatch Console Enhancements: Deployable user setting for Pinning of Extended Event Edit window & Support for Event Type field in non-work Order event window ServiceMax Linx for ServicePower Enhancements: Configurable scheduling horizon for Job Book Requests ServiceMax Spring 15 for ipad: Color-coding of Calendar Events, Sync conflict count as badges on Tools & Hamburger (navigation bar), Configurable Aggressive Sync Page 5 of 29

6 ServiceMax Spring 15 SP Release Notes Spring 15 SP Feature Summary and User Impact The Spring 15 SP Feature Summary and User Impact table shown below identifies the enhancements and indicates setup requirements. ServiceMax Suite Feature Enabled for all users Requires Administrator setup Contact ServiceMax Support to enable Dispatch Console Deployable User Setting for Pinning of Extended Event Edit Window Dispatch Console Event Type field in non-work Order event window Dispatch Console Auto-populate calculation enhancements Translations Update Smart Docs Display of translated picklist field values SFM: Covered Product as target header object Linx for ServicePower: Configurable Scheduling Horizon for Job Book Request ServiceMax Spring 15 for ipad Feature Enabled for all users Requires Administrator setup Contact ServiceMax Support to enable Color-coding of calendar events Sync conflict count as badges Configurable Aggressive Sync Page 6 of 29

7 Release Notes ServiceMax Spring 15 SP Backward Compatibility Matrix ServiceMax Suite versions supported for Spring 15 Mobile App versions Mobile App Version* Android ( ) ipad ( ) iphone ( ) Mobile for Laptops ( ) Supported ServiceMax Suite Versions Spring 15, Spring 15 SP Spring 15, Spring 15 SP Spring 15, Spring 15 SP Spring 15, Spring 15 SP Offline Client ( ) Winter 14 to Spring 15 SP * This is the lowest compatible version of the app. Any higher versions (within the same release) are automatically supported ServiceMax Mobile App versions supported with Spring 15 SP ServiceMax Suite Mobile App Supported ServiceMax Mobile app Versions Android Spring 15 ipad Spring 15 iphone Spring 15 Mobile for Laptops Spring 15 Offline Client Offline Client Page 7 of 29

8 ServiceMax Spring 15 SP Release Notes ServiceMax Suite Dispatch Console Enhancements Deployable user setting for Pinning of Extended Event Edit window Extended Event Edit window is displayed in create/edit event window for both Work Order and non-work Order events. This displays the fields configured in Dispatch Console Field Updates configuration screen. This window is collapsed by default. It can be expanded by clicking the Expand (right arrow) button at the top right of the event window. This expanded state can be pinned (persisted) by clicking the pin button at the top right of the event window and then clicking the Save Settings button. Though this persistence was previously supported, it was not a deployable user setting. From this release, this pinned state is saved along with the other user settings. This enables deploying of this setting to all users and the window to be expanded by default for all users if required. For more information about user settings, refer to Online Help. Event Type field in non-work Order event window Event Type field is now supported in Create/Edit non-work Order event window. This applies to both Salesforce and ServiceMax Event objects. Type field can be displayed in non-work Order event window by setting the associated group configuration setting SET005 (under Dispatch Management Event Management) to True. There is no out-of-the-box functionality related to Event Type field in this release. For more information about non-work Order event window, refer to Online Help. Auto-populate calculation enhancement Clicking the Auto-populate button next to the Duration area in Work Order Event window previously used to reset all other time components to 0 and set Service Time as the End Date Start Date. This has now been enhanced to be consistent with auto-synchronization of dates and durations. This means that changing the End Date and clicking the Auto-populate button will change the Service Time, and not change the other time components. For more information about Work Order event window, refer to Online Help. Page 8 of 29

9 Release Notes ServiceMax Spring 15 SP Other Enhancements Translations Update For all the eleven supported languages, translations have been updated to cover all the new features released till the Spring 15 release of ServiceMax. These translations include out-of-the-box translations for strings defined in standard SFM transactions, wizards, searches, and inventory processes also. For more details, refer to Online Help sections Language Support and ServiceMax Translation Workbench. Translated picklist values in Smart Docs Smart Documents (Output Documents) can now be configured to support display of translated picklist values. All the standard Smart Docs such as Work Order Service Report have been enhanced to support this feature by default. SFM Transaction & Docs Designer has been enhanced to provide this functionality by default. The suffix.label is automatically added to the merge Field Value of picklist fields in SFM Designer for this purpose. When upgrading from a previous release of ServiceMax, existing custom Smart Docs can be enhanced to use this feature by adding the suffix.label to the picklist field merge value. For example, replace {{$D.Work_Order.SVMXC Purpose_of_Visit c}} with {{$D.Work_Order.SVMXC Purpose_of_Visit c.label}}. Spring 15 SP version of mobile apps also support this enhancement. For more details about Smart Doc Templates, refer to Online Help section How to Manage Document Templates. Covered Product as target header object in SFM transactions SFM Transaction & Docs Designer now enables you to configure Covered Product as the target header object in any type of SFM transaction. For details about other supported objects, refer to Online Help. Page 9 of 29

10 ServiceMax Spring 15 SP Release Notes ServiceMax Linx for ServicePower Enhancements Configurable Scheduling Horizon for Job Book Requests For Job Book Request call to ServicePower on creating/updating a work order, default scheduling horizon was taken as the Work Order Preferred Start Time and Preferred End Time. These were mapped to the JobBookRequest API call parameters contractearliest and contractlatest respectively. If Preferred End Time were blank, it was being defaulted to the value Preferred Start Time + 7. If Preferred Start Time were also blank, Preferred End Time was being defaulted to the value Now + 7. In this release, group configuration setting SET012 has been introduced to enable modification of this scheduling horizon (promised response window). The default value of this setting is 7 days, for backward compatibility. Another enhancement introduced using this setting is as follows: Previously, the start and end dates of the Access Hours sent for JobBookRequest API call were derived from contractearliest and contractlatest parameter values. Now, the start and end dates of the Access Hours are set to the widest scheduling horizon between the following two ranges: Dates derived from contractearliest and contractlatest Dates derived from contractearliest and (contractearliest + value of SET012) For more information on Linx for ServicePower, refer to Online Help. Page 10 of 29

11 Release Notes ServiceMax Spring 15 SP ServiceMax Spring 15 for ipad Color-coding of Calendar Events Color-coding of calendar events in Day and Week views is now supported for Case and Work Order events, based on Priority. The colors are as per the global configuration settings SET001 to SET004 under module ServiceMax ipad Client and submodule Calendar. The applicable color is displayed in the accent bar, as a narrow vertical band on the left side of the event, not the entire event block. Sync conflict count as badges When data sync results in one or more sync conflicts, the count of sync conflicts is displayed as a badge on the navigation bar hamburger and also on the Tools option. This alerts the user to the sync conflicts as soon as they occur. So, the user can resolve the conflicts immediately. This ensures successful data sync on subsequent saving of local data and at scheduled intervals. Configurable Aggressive Sync A new configuration setting has now been introduced to control whether aggressive sync should be triggered when a record is saved in ipad app. This group setting SET019 (Enable Aggressive Sync, under module ServiceMax ipad Client, submodule Synchronization) is set to True by default for backward compatibility. This can be set to False for disabling aggressive sync. This enables the ipad app user to have control over when to sync data. User can use manual sync, or wait for scheduled data sync to sync the locally saved data. Page 11 of 29

12 ServiceMax Spring 15 SP Release Notes Issues fixed in this release ServiceMax Suite Version SMX SMX Dispatch Console created All Day events a day earlier than start date. The end date too was changed to previous day. This used to happen for both Salesforce and ServiceMax events, with some combinations of local, Salesforce, and Dispatch Console time zones. Attempt to book an appointment for a work order in ServicePower failed with the error message "SVMXC: Too many query rows: 50001", when using Calendar View screen. This was observed when there were more than 50,000 Service/Maintenance Contracts in the org. ServiceMax Suite Version SMX SMX SMX SMX In Work Order window launched from Dispatch Console, SFM processes did not load on clicking the SFM wizard buttons. Work order window was opened from Dispatch Console by selecting the Work Order Grid context menu option Show Record. When a child object's picklist field values were numbers, adding them using the SUMOF function in Smart Docs template did not work as expected. When the Smart Doc was generated, the value returned by the SUMOF function was 0, instead of the sum of picklist field values of all the child records. SFM Transaction & Docs Designer got stuck in a loop, when it was launched from SFM Wizard Designer. When clicking the Edit link associated with a wizard step, the SFM Transaction & Docs Designer successfully loaded the interface and the correct SFM transaction, but it never stopped loading and did not allow progressing into editing the SFM transaction. In Smart Docs, when a picklist field value was compared with a specific value in an IF function, the value printed in the report generated was incorrect when the condition was met. For instance, if the value of Purpose of Visit picklist field in a work order was 'Installation', the function {{$F.IF($D.Work_Order.SVMXC Purpose_of_Visit c == "Installation", 'For Installation', 'Not For Installation')}} printed Not For Installation instead of 'For Installation'. Page 12 of 29

13 Release Notes ServiceMax Spring 15 SP ServiceMax Suite Version SMX When selecting some custom Work Order Views in Dispatch Console, the following error message got displayed and the view did not get loaded: An error occurred while refreshing work order list. System.QueryException: unexpected token: '<EOF>'. This happened only with the custom views created or edited after upgrade to Spring 15 SP. Note: After upgrade, execute the following steps for each view which failed to load in Dispatch Console: 1. Go to ServiceMax Setup home page and launch Dispatch Management > Dispatch Console Views configuration page. 2. Select the failing custom view, click Edit, and save it. ServiceMax Suite Version SMX SMX SMX After the Salesforce platform upgrade to Summer 15, ServiceMax Search and ServiceMax Community components in the left pane of the Home tab were blank. For this fix to work, execute the following steps after upgrade: 1. Navigate to the Salesforce Setup page Home Page Layouts under App Setup / Build > Customize > Home. 2. Identify the layouts which include the components ServiceMax Search and ServiceMax Community. 3. Make the following edits in each layout identified and save: Remove (uncheck) the above two components. Add (check) the components ServiceMax SFM Search and ServiceMax Customer Community. Note: Search results page will be displayed with sidebar and header by default. If you would like to view the search results page in full screen mode, you can set the new global configuration setting SET001 (module SFM Transaction Manager, submodule SFM Search Engine) to False. Smart Document (Output Document) PDF generation used to fail with the error PDF generation failed. Check the page markup is valid for Partner Community users. Launching Territory Match Rule configuration screen from ServiceMax Setup home failed with the Visualforce error "Maximum view state size limit (135KB) exceeded. Same error returned on selecting a view in Dispatch Console Views configuration screen and clicking View, Clone, or Edit & Quick Save buttons. This happened in orgs having large number of objects and/or large number of fields in Work Order object. Page 13 of 29

14 ServiceMax Spring 15 SP Release Notes SMX018247, SMX SMX SMX SMX SMX SMX SMX Save operation failed in SFM Delivery screen with the error 'No matching record(s) found for this keyword' when user executed the following steps: 1. Entered or copied & pasted value into a lookup field in Extended Edit Window 2. Did not click the lookup search button and clicked Save/Quick Save. This happened if there was context configured for that lookup field, based on another lookup field. Events were not displayed in Dispatch Console when a Salesforce user was assigned to two Technician records and one of the Technician records was not active. Days of the week displayed in the Gantt area of Dispatch Console were not translated in languages other than Japanese. Note: This fix applies to all the languages supported out of the box by ServiceMax, except Dutch, Italian, and Swedish. In SFM Delivery screen, after the value of a read-only lookup field was copied and pasted to another field, save failed with the error id value of incorrect type for the read-only field. Whenever a work order with SLA was updated, Preferred Start Time got reset to current time. So the work order got rebooked with every update, even when it was not supposed to be rebooked. When any SFM wizard was opened for editing in the SFM Wizards configuration screen, the operation failed with the Visualforce error "Maximum view state size limit (135KB) exceeded. This happened in orgs having large number of objects, wizards, wizard steps, expressions, and configuration profiles. Submitting an inventory process failed with the error Upsert failed. First exception on row 0; first error: DUPLICATE_VALUE, duplicate value found: SVMXC ProdStockCompositeKey c. This happened when both the conditions given below were true: SET001 Calculate Composite Key for Product Stock under module Inventory and submodule Inventory Engine was set to True. Another inventory process was previously successfully submitted for the product stock referencing the same product and location. Note: For this fix to work, execute the following steps after upgrade: 1. Search for duplicate Product Stock records in your org. These are records which have the same Product, Location, and Status. 2. For each Product, Location, and Status key, merge any associated Stocked Serial records with one of the Product Stock records. 3. Delete the remaining duplicate records. Page 14 of 29

15 Release Notes ServiceMax Spring 15 SP SMX Submitting an inventory process failed with the error Attempt to de-reference a null object. This happened when the first location in the inventory process was not a stocking location and the Stock Updates configuration for the process was Location 1 May Be Non-Stockable, An example of such an inventory process is Process Receipts (Advanced) for RMA PORD009. ServiceMax Mobile Issues Fixed in ServiceMax Server Version SMX SMX ipad app initial sync used to fail inconsistently with the error 'System.DmlException: Update failed. First exception on row 0...; first error: UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record:[]'. This used to happen randomly, when the Mobile Configuration option 'Capture synchronization time logs' was enabled. When 'Capture synchronization time logs' option in Mobile Configuration screen was enabled, Smart Docs report got generated as HTML/PNG on synchronization to server from ipad app. PDF file was not generated. This happened after the upgrade of Salesforce platform to Summer 15 release. ServiceMax Mobile Issues Fixed in ServiceMax Server Version SMX When technicians' schedules were tracked using ServiceMax events for managing long-term projects, child records were not automatically downloaded for parent records related to events. Note: This issue and fix are applicable to ServiceMax Spring 15 for ipad and Mobile For Laptops applications. Page 15 of 29

16 ServiceMax Spring 15 SP Release Notes ServiceMax Configurator SMX SMX In orgs upgraded/migrated from the Winter 15 or older release of ServiceMax, some SFM transactions which created new target child records from existing source child records did not create the expected number of target records. This was due to an enhancement to the SFM transaction definition in the backend in the Winter 15 SP release. When the ServiceMax Configurator is run now for any release from Winter 15 SP, it will auto-update the definition of SFM transactions as appropriate and capture the list of these SFM transactions in the configurator log file. Where this auto-update is not possible, list of such SFM transactions will be sent as a csv file, to the id specified when running the configurator. The will also include step-by-step instructions for updating the listed SFM transactions. ServiceMax Configurator failed to load profiles when the org did not have Salesforce Platform licenses. Configurator log file had the following error details: {ErrorMessage=[errors.cancel[An error occurred during deployment. Please contact ServiceMax support for further assistance. Temp/profiles/ServiceMax Admin - Titanium (Platform).profile(ServiceMax Admin - Titanium (Platform)):In field: userlicense - no UserLicense named Salesforce Platform found. Page 16 of 29

17 Release Notes ServiceMax Spring 15 SP ServiceMax Spring 15 for ipad Version SMX SMX SMX SMX Unicode text (such as Japanese, Chinese, Korean characters) entered in Smart Doc templates did not render properly when the Output document was generated using the ipad app. Note: For such text to render correctly in PDF format, you have to remove the font family tag (.container {font-family:arial, Helvetica, sans-serif; fontsize:12px; margin:0 auto; width:100%} ) from the template's source code. When the ipad device's time zone is different from the time zone set for the logged-in user in the Salesforce org, dates displayed in Smart Docs reports were off by a day. The values shown were that of a day earlier. In Smart Docs, date fields were not being populated when the value had single digit months. In ipad Air devices running ios 9.1, app used to hang sometimes after execution of data validation rules. ServiceMax Spring 15 for ipad Version SMX SMX SMX SMX When connecting to internet over 3G through VPN, users were unable to login to ServiceMax for ipad app. The loading indicator was displayed continuously and Salesforce OAuth login page was not available to the users to enter credentials. When users generated and finalized Smart Doc reports in ipad, some signatures did not come through and were replaced with a tree image in the PDF, on synchronizing to the server. This used to happen inconsistently when new reports were generated, when previously generated reports were being synchronized to server in the background Some Smart Docs reports did not get generated when synchronized to server. This used to happen intermittently, under the following conditions: - Several reports (5 or more) were generated when the ipad was in offline mode. - When the connectivity was resumed, several more reports (5 or more) were generated in quick succession, when the reports generated in offline mode were being synchronized to server in the background. Data sync and service report sync were not getting completed for some users inconsistently, and the sync requests were timing out. Changing the request timeout value in the ipad device settings for the ServiceMax app did not resolve the issue. Page 17 of 29

18 ServiceMax Spring 15 SP Release Notes SMX SMX025467, SMX SMX In adherence to Salesforce s announcement of retiring all internal routing starting January 1, 2016, all references to API endpoint have been changed to For more details, refer to Salesforce Knowledge article - Note: Post January 1, 2016, using older versions of the app which use the old API endpoint will result in '404 (Page not found)' errors. When the volume of data to be downloaded is high for objects which have Advanced Download Criteria defined, Initial sync was not downloading all matching records. As result, lookups were not returning any matches. App was crashing on completion of configuration sync when there were multi-day events configured for download. ServiceMax Spring 15 for ipad Version SMX019566, SMX SMX SMX SMX SMX When a record was updated and update was still being synced to server, if a Smart Doc report was generated and finalized, target object field updates were not made as configured. This resulted in record reverting to previous status. For instance, a work order went from Completed state back to Assigned state, or a flag indicating completion of Service Report generation was not set, after report finalization. When both the master and detail record were created in the ipad app while in offline mode, synchronization failed with the error Invalid ID type for the referred parent record for the detail record. In some scenarios, PDF document was not generated properly on the online server when the user generated Smart Doc reports in ipad app. This used to happen inconsistently, when a large number of reports were generated in ipad app in offline mode, and then they were all synchronized to server in low connectivity conditions. Initial sync used to fail inconsistently for some users, with the error message System.LimitException: BlobValue length exceeds maximum: This used to happen in orgs having a large number of objects and a large number of fields in objects, when many of these objects were accessible to the ipad app user and were downloaded to ipad app. After logging in to a custom host and completing the initial sync, all the subsequent syncs failed. This happened when the ipad app device setting Session Auto Refresh was set to ON (default value). Page 18 of 29

19 Release Notes ServiceMax Spring 15 SP ServiceMax Spring 15 for ipad Version SMX SMX SMX SMX Even when the user's language in Salesforce org and the device were not English and the device locale was not English, date and datetime field values were displayed in English US locale. In edit screen, date picker showed the dates in the user's language, but on selection and save, dates were displayed in English language, with US locale. Some Smart Doc reports did not get generated and kept loading forever after upgrading to Spring 15 SP release. This happened when the Smart Doc template included a picklist field and one of the following conditions was true: 1. The picklist field was not accessible to the ipad app user. 2. The picklist field was not included in any SFM transaction page layout. Configuration sync used to get stuck at step 3 and initial sync used to get stuck at step 6. These sync issues used to occur randomly, when GPS Location Tracking was enabled in the device. Get Price was not populating Billable Qty and Line Price Per Unit correctly for Labor lines, if the device had 24-Hour Time format enabled, or had Region set to any value other than United States. ServiceMax Spring 15 for ipad Version SMX SMX Initial sync and configuration sync used to fail intermittently for some users, with the error message Apex heap size too large. This used to happen in orgs having a large number of objects and a large number of fields in objects, when many of these objects were accessible to the ipad app user and were downloaded to ipad app. When the volume of data related to Get Price such as products, pricebook entries, and so on was high, initial sync used to fail intermittently at step 5 of 6 with the error message System.JSONException. ServiceMax Spring 15 for ipad Version SMX If any installed product at a scheduled work order s location did not have associated Product, the app crashed during initial sync at step 5 of 6. On launching the app again, it used to crash immediately. Page 19 of 29

20 ServiceMax Spring 15 SP Release Notes ServiceMax Spring 15 for ipad Version SMX SMX SMX015871, SMX SMX017886, SMX SMX SMX SMX SMX Datetime field value entered when creating/editing a record used to have seconds value corresponding to the current time. This value used to be retained even when the existing datetime value was updated. The seconds value set as above was incorrect, could not be edited by the user, and must have been set to 0 for consistency with Salesforce and ServiceMax online application behavior. Labels such as Finalize, Customer Signature, and Signature in Smart Docs screen did not have translatable custom labels or out-of-the-box translations. Note: For this fix to work, do a configuration sync or a reset app after upgrading the app and server package to Spring 15 SP version. The app was timing out, requiring sign-in even after a short period of inactivity, though the session timeout for the org was set to a high value. When the users signed in after the session time-out, initial sync used to start automatically, resulting in loss of local data changes not synchronized before the time-out. This used to happen under the following conditions: GPS Location Tracking feature was enabled for the org and the device. App was put in background mode, was left idle, and then brought to foreground mode. During this idle time, location tracking became due (as per the interval configured in Mobile Configuration screen). The device was locked during idle time, and then unlocked by entering the passcode. When launching an Action to create new child records from existing source records, source records not matching the qualifying criteria were also being considered. This resulted in creation of more target records than intended. With ios 8.x, images added from Camera Roll > My Photo Stream option did not get uploaded properly. A black thumbnail was displayed for such images and tapping them displayed a white screen with a? icon at the top. In Work Order Troubleshooting screen s Chatter page, only a single line was being displayed for any post. When the user s language was French, the label of the button used to add new child records was displayed as + A TER instead of + AJOUTER. When using Advanced Get Price, billable hours were calculated incorrectly for dates on which DST change occurs. The hours were calculated as 22 instead of 23 and 26 instead of 25. Page 20 of 29

21 Release Notes ServiceMax Spring 15 SP SMX SMX SMX SMX SMX SMX SMX019025, SMX SMX When there were more than 8000 records downloaded to the mobile app through advanced download criteria, data purge did not get past advanced download criteria. Month and day were not displayed in the user s language in view and edit screens for date and datetime fields. The app crashed on clicking the +Add button to add a child record. This happened when Multi-Add Using was configured for the child section, and the lookup field configured had a basic filter defined using the SFM literal SVMX.CURRENTRECORDHEADER. When a child section had more than 50 records, +Add button was not displayed in the data entry screen and hence it was not possible to add any more records. In some orgs, logo was not being displayed in both standard and custom service reports, even with default configuration. Note: For this fix to work, do a configuration sync or a reset app after upgrading the app to Spring 15 SP version. When there was connectivity and successive updates were made to the same record by launching different Actions menu items, updates made during some of the actions were lost at times. Initial sync was stuck for a long time at step 5 of 6 and took considerably longer time to complete with ServiceMax Spring 15 for ipad app, when compared to the time taken by Winter 15 app. In an org with Login IP restrictions, when the users connected through external network such as 3G from the field, app failed with the error about expired or invalid session. This happened though the session initiated during initial sync when connecting from corporate network had a long validity period. For resolving this issue, after upgrading to Spring 15 SP app, the new device setting Session Auto Refresh must be turned OFF. It is ON by default. Page 21 of 29

22 ServiceMax Spring 15 SP Release Notes ServiceMax Mobile For Laptops Version SMX SMX SMX SMX SMX SMX Login to the application in Windows on virtual machine failed with the error 'An unexpected error has occurred while connecting to Salesforce. Re-login to proceed.', when there was no connectivity. Note: This fix involves a new option vmvendors added to the configuration file AppSettings.conf, for the app to identify the virtual machine manufacturer. By default, this setting value includes Parallels Software International Inc., Microsoft Corporation, and VMware, Inc. If the virtual machine manufacturer is not one of the above, execute the command gwmi Win32_ComputerSystem to identify the virtual machine manufacturer and add it to the configuration file. System admin privileges may be required to run this command. Filter criteria were not applied correctly and duplicate line records were displayed in some scenarios. This happened when the same child object was used in two or more lines sections, with qualifying criteria configured to identify the records that matched each section. For example, Record T&M transaction listed Estimate lines along with Usage/Consumption lines, though the filter was configured to list only Usage/Consumption lines. Some of the SFM wizard steps were not being enabled / disabled correctly, as per filter criteria defined for the individual wizard steps. SFM search results screen displayed incorrect date for date fields, for all the records. For instance, when the user's time zone had a negative offset from GMT, the dates displayed were one day earlier than the actual date. Record Type dependencies were being ignored in Extended Edit window. When adding a new line and editing it using Extended Edit window, all the picklist values were displayed when only the values related to the selected Record Type must have been displayed. If one of the invalid values was selected, the record was saved with null as the picklist value. Work Order Get Price did not fetch the correct price when any custom Price Book was configured for the associated group configuration setting under module Work Order, submodule Create Work Order Lines VF. Page 22 of 29

23 Release Notes ServiceMax Spring 15 SP ServiceMax Mobile For Laptops Version SMX SMX SMX Duplicate line records got created when the same child object was used in two or more lines sections, with qualifying criteria configured to identify the records that matched each section. For example, when a Labor line was added in a Record T&M transaction and saved, an Expense line also got added. Login to the application as Partner Portal User failed with the following error: An unexpected application error has occurred. Try this operation again. If the problem persists, please contact your ServiceMax administrator with the error details below. "The remote server returned an error: 404 Not Found." When a Smart Doc template included any picklist field which was not accessible to the mobile app user, report did not get generated and kept loading forever. ServiceMax Mobile For Laptops Version SMX SMX Some SFM wizard buttons were disabled even when the record met the criteria to enable the step. This happened in some scenarios when the criteria included 10 or more expressions, and advanced expression with a combination of OR and AND operators. Data Access API calls used to fail with the error Invalid User Name or API Access Key when there was no connectivity. This happened if the API Key used had been generated in the application when there was connectivity. The API Key generated was found to be changing with change in connectivity (offline, WiFi, 3G). Note: For this fix to work, please execute the following steps after upgrading the app: 1. Rebuild the 3rd party application with the libraries from the latest Mobile For Laptops app. 2. Launch the Mobile For Laptops app, generate the API Key, and use this new key from the 3rd party app. Page 23 of 29

24 ServiceMax Spring 15 SP Release Notes ServiceMax Mobile For Laptops Version SMX013620, SMX SMX SMX SMX SMX SMX In Search results screen, datetime field values were displayed in GMT instead of in the applicable time zone. Performing lookup search caused the application to become unresponsive. This happened after configuration sync, for some lookup fields. Note: For this fix to work, do a configuration sync or a reset app after upgrading the application to Spring 15 SP version. When user viewed a record in a View Process screen, master values were displayed for picklist fields, instead of translated values as per the logged in user's language. When an object had more than three record types, all the available values were displayed for picklist fields for some record types, instead of only the specific set of values selected for each record type. Note: For this fix to work, do a configuration sync or a reset app after upgrading the application to Spring 15 SP version. For work orders assigned to multiple technicians, events of the other technicians were displayed in the calendar along with the events of the logged in technician. This used to happen immediately after initial sync and Reset App, and got resolved automatically after data sync. Error message about poor/lost connectivity was shown frequently during initial sync, configuration sync, and data sync, even when the connectivity was good. This paused the sync, requiring the user to click Continue to resume the sync every time. ServiceMax Spring 15 for iphone Version SMX SMX In adherence to Salesforce s announcement of retiring all internal routing starting January 1, 2016, all references to API endpoint have been changed to For more details, refer to Salesforce Knowledge article - Note: Post January 1, 2016, using older versions of the app which use the old API endpoint will result in '404 (Page not found)' errors. App used to crash when any null values were being included in data sync. Page 24 of 29

25 Release Notes ServiceMax Spring 15 SP ServiceMax Spring 15 for iphone Version SMX SMX Initial sync used to fail with the error 'SVMXC:Too many query rows: 50001', when the Mobile Configuration option 'Capture synchronization time logs' was enabled. Initial sync used to fail with the error message Apex heap size too large at step 3. This used to happen in orgs having a large number of objects and a large number of fields in objects, when many of these objects were accessible to the iphone app user and were downloaded to iphone app. Page 25 of 29

26 ServiceMax Spring 15 SP Release Notes ServiceMax Spring 15 for iphone Version SMX Labels such as Finalize, Customer Signature, and Signature in Smart Docs screen did not have translatable custom labels or out-of-the-box translations. Note: For this fix to work, do a configuration sync or a reset app after upgrading the app and server package to Spring 15 SP version. ServiceMax Spring 15 for Android SMX SFM Searches did not return any results when a standard lookup field to a standard object was included in the list of display and/or search fields. Examples are: Owner field included for any object search and Account field included for Contact or Case object search. Page 26 of 29

27 Release Notes ServiceMax Spring 15 SP Known Issues/Limitations This section lists known issues/limitations in the enhancements released in the Spring 15 SP release of ServiceMax. ServiceMax Spring 15 for ipad Color-coding of events: For Case events, SET003 is applied instead of SET004 if case priority is anything other than High, Medium, and Low. Upgrade Instructions This section provides the details of upgrade instructions for different features. ServiceMax Search and Community Following steps are required to get ServiceMax Search and Community components displayed in the home page, after the Salesforce platform upgrade to Summer Navigate to the Salesforce Setup page Home Page Layouts under App Setup / Build > Customize > Home. 2. Identify the layouts which include the components ServiceMax Search and ServiceMax Community. 3. Make the following edits in each layout identified and save: Remove (uncheck) the above two components. Add (check) the components ServiceMax SFM Search and ServiceMax Customer Community. Linx for ServicePower On upgrading from Spring 15 release, ensure that the group configuration setting SET011 is set to Activity Type value from ServicePower, instead of Activity Type Id. This setting is to specify the Default ServicePower Standard Activity Type for non- Work Order events, and it is under module Dispatch Management and submodule Linx for ServicePower. If Type is not specified for a non-work Order event created in ServiceMax, default value is taken from the value of this group configuration setting. Page 27 of 29

28 ServiceMax Spring 15 SP Release Notes Appendix Configuration Settings introduced in this release Dispatch Management Event Management Setting Id & Name SET005 Show Type field in create/edit event window for non-work Order events Default Value: True Details: Setting Value and Details Setting this group setting to true displays the Salesforce/ServiceMax Event object's Type field in the create/edit event window for non-work Order events. Dispatch Management Linx for ServicePower Setting Id & Name SET012 Preferred scheduling horizon in days for job book requests Default Value: 7 Details: Setting Value and Details If contractlatest parameter in JobBookRequest API call to ServicePower evaluates to null, set it to the value of contractearliest parameter (datetime) + the value of this group setting (days). This is to indicate the preferred scheduling horizon (promised response window) to use when scheduling the work order. These parameters map to fields Preferred Start Datetime (contractearliest) and Preferred End Datetime (contractlatest) fields in the interface object Job Book Request in SFM Mappings configuration screen. ServiceMax ipad Client Synchronization Setting Id & Name SET019 Enable Aggressive Sync Default Value: True Details: Setting Value and Details This group setting, when set to true, will continue to trigger incremental data sync when a record is saved in ServiceMax Spring 15 for ipad app. When set to false, data saved in ipad app will be synchronized only during manual or scheduled incremental data sync. Page 28 of 29

29 Release Notes ServiceMax Spring 15 SP SFM Transaction Manager SFM Search Engine Setting Id & Name SET001 Display Search Delivery page with sidebar and header Default Value: True Details: Setting Value and Details Setting this global setting to True, displays the Search Delivery page with sidebar and header. When it is False, Search Delivery page is displayed without sidebar or header, in full screen mode. This setting applies to online app (browser) only. Device Settings introduced in this release ipad app Session Setting Name Session Auto Refresh Default Value: On Details: Setting Value and Details Turning this ipad app device setting ON validates the session whenever a call to the server is made and refreshes the session automatically to get a new token, if it was last obtained more than several minutes ago. Turning this OFF uses the session last obtained without any validation, and prompts the user for re-authentication on session timeout. Page 29 of 29