3

Currently the user profile carousel navigation has three different items..

On a desktop running one/one.app viewing a user profile:
  carousel1:  chatter / follow user
  carousel2:  about user / edit / reset password/ freeze actions
  carousel3:  related lists / mobile cards

On a mobile device viewing a user profile:
  carousel1:  chatter / follow user
  carousel2:  followers / following / direct reports / files / groups
  carousel3:  about user

If one adds a visualforce page to a mobile card on the user profile it will display fine in the browser using one/one.app.. Yet when we view the user profile in the mobile salesforce1 application we do not see the visualforce page / mobile cards. More over the componets displayed are different as shown above..

Why does the one/one.app differ from the mobile client?

How do we get a visualforce page embedded on a mobile card to display on a mobile client?

Why are we getting different behaviour on one/one.app vs. mobile client?

Thanks!!

enter image description here

1

2 Answers 2

1

Why does the one/one.app differ from the mobile client?

Why are we getting different behaviour on one/one.app vs. mobile client?

The one/one.app doesn't really simulate a mobile device. If you want to do that you have to use the one/one.app and additionally use the Mobile Emulation of Chrome. But there still will be some differences between one/one.app and the Salesforce1 App.

How do we get a visualforce page embedded on a mobile card to display on a mobile client?

Do you ckeck the Available for Salesforce mobile apps Checkbox for the Visualforce pages you want to use for your mobile cards ?

1
  • Thank David. Everything you say is true.. But sorry this still doesn't answer how we get visualforce pages in a mobile card on a native app in the user profile. Yes the vfpage is available for salesforce mobile apps and does show up in one/one.app but not on mobile client. Commented Jul 30, 2014 at 19:52
0

Salesforce confirmed that this is the current behavior on ipad/iphone clients. Was told this should be fixed with next release..

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .