Custom Mobile Advance Search no longer available for users after quarterly patch received over the weekend of 18th.

(Doc ID 2236420.1)

Last updated on APRIL 11, 2017

Applies to:

Oracle Fusion Mobile Sales Cloud Service - Version 11.1.11.1.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.11.1.0 version, Mobile Sales App

ACTUAL BEHAVIOR
---------------
Custom Mobile Advance Search no longer available for all users after quarterly update.

The custom advance search that all of our users need to search for the "Dealer ID" field no longer works in the SalesCloud Mobile app. They received the quarterly patch over the weekend of Feb 16th, and there was also an actual Apple app store update around Feb 16th for the mobile app as well.

All of our user are on iOS devices.
Oracle SalesCloud app version: 11.1.11.0.12.1
iOS version: 10.2.1 (14D27)

EXPECTED BEHAVIOR
-----------------------
Customer should be able to access the custom advance search created when clicking on "Reset" bottom.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

Previous Behavior:
1. Go to Accounts
2. Select Advance Search
3. Select the "Reset" Button to expose the custom advance search our users need to perform necessary day to day operations. This custom search includes a custom field called "Dealer ID" that our users need to quickly search for certain Accounts.

New Behavior after Mobile App update OR Quarterly Patch Bundle Update:
1. Go to Accounts
2. Select Advance Search
3. Select "Reset". The screen flashes and the custom advance search never appears. (Please See Attached Video showing issue)

BUSINESS IMPACT
-----------------------
The issue has the following business impact: Users cannot access the custom advance search created before quarterly update when clicking on "Reset" bottom.

Changes

After some additional testing in the customers environment they were able to recreate this issue on the current version of the SalesCloud mobile app and previous versions, so its safe to say the Apple App Store update around Feb 16th has nothing to do with it.

It almost certainly was caused by the quarterly patch they received over the weekend of the Feb 18th:

Product: 3.07.01.00
Binary: 3.07.01.143
Package: 3.07.01.00 (Build 143)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms