Offline Mobile - No Sections Loading

User Experience
, , , , ,
1

When attempting to configure the Pega Sales Automation application for offline use, section rules in the harnesses defined by the mobile navigation rule are not loading. The spinning loading icon appears indefinitely. I have attempted to follow the offline configuration documentation, but cannot seem to get any UI elements to load in a harness. The log off function works properly, and the sync seems to succeed, however.

Loading icon displays when attempting to load any harness.jpg
Loading icon displays when attempting to load any harness.jpg2732×2048 86.3 KB

I have attempted the following to troubleshoot and simplify the configuration:

  • Removed section customization to reflect OOTB functionality only
  • Reduced the number of OOTB case types enabled for offline use to one
  • Use the “My Work” harness recommended in the documentation
  • Configure harness rules to use client side template UI, and tried displaying online version of the page (and non-online version)
  • Display a harness with only a single button with no actions in an attempt to get any section to load
  • Attempted to create a simple case type solely to test offline functionality

This is a simplified version of events, and more detailed steps can be found in the attached document.

Is there some configuration step that I’ve missed here? I would have expected the simple harness/section to load without issue.

07_06 Offline UI Issue.docx (71.1 KB)

2

@MatthewD2007 please can you confirm that you logged this question as a support ticket under INC-227752?

I believe our support team helped resolve this issue, and the final outcome on July 13th was as follows:

Solution description:

Solution description:

Made following changes/checks to resolve screen to display fine

a. Configured a new channel altogether on application for which mobile end user access group is pointing to. (Earlier they were modifying the default shipped channel “Pega Sales Automation”. This was done since default channel was built on ui-kit and now the client application is on cosmos. And also do away with any other concerns, we started scratch new channel)

b. Made sure leads mobile list pages are selected

c. Made sure the role selected in mobile channel is matching with the access group of actual mobile end user.

d. Made sure the access group of actual mobile end user had a portal with same name as mobile channel

e. The default offline configuration was used (could have used PegaSalesAutomation offline configuration as well )

f. Search configurations are removed

I will mark this as the solution in the next couple of weeks if there is no further update on this post.