You need to set the page to Available For Salesforce Mobile Apps. This is found in Setup > Develop > Pages > Edit (Page Name). First, you need to specify a page version of at least 27.0 (on the Version Settings tab), then you can check the box to make the page available. You can now also add pages to the navigation menu, under Setup > Administration > Mobile ...
You can't edit the Activity Publisher component, but you can change the set of tabs that appear therein. They're Quick Actions.
You can control which Quick Actions appear in the Activity Publisher by editing the "Salesforce Mobile and Lightning Experience Actions" section of the page layout assigned for the relevant record type/profile combination. ...
In Summer '15 you'll be able to hide the header in Visualforce custom actions using the showQuickActionVfHeader attribute. As per the Summer '15 Release Notes:
To hide the header, add showQuickActionVfHeader=“false” to the
<apex:page> tag of the custom action’s
Visualforce page. When the Visualforce custom action renders in
Salesforce1, the ...
The Lightning component you wanted to show in quick action should implement force:lightningQuickAction or force:lightningQuickActionWithoutHeader interface.
Add the force:lightningQuickAction or
force:lightningQuickActionWithoutHeader interface to a Lightning
component to enable it to be used as a custom action in Lightning
Experience or Salesforce1....
So @Monith's answer is correct in that you should use an outputLink tag, but I disagree with the link construction methodology enough to post a separate answer.
When you are constructing links for standard actions, you should use the $Action global variable:
If you look through the Valid Values for the $...
As of the latest version of Chatter Mobile(v4.2), you can now include VF tabs in the app. Mark the VF page as Available to Mobile apps and create a tab that uses that page. Then go to Administer>Mobile Administration; you’ll find a new option called Mobile Navigation. This lets us rearrange “stage left” in the Chatter Mobile app. We can add and remove ...
You can query the rather misleadingly named WebLink SObject to find all of the information you need about a custom button:
Select Width, Url, SystemModstamp, ShowsStatus, ShowsLocation, ScontrolId,
RequireRowSelection, Position, PageOrSobjectType, OpenType, NamespacePrefix, Name,
MasterLabel, LinkType, LastModifiedDate, LastModifiedById, IsResizable,
Two things going on here:
To predefine a lookup field in a Publisher Action, you need to pass in an ID Field. So, if this were going to work, you would put Account.Id. As @LaceySnr posts, there doesn't seem to be a way to pass an actual record ID into the field. (However, note that there is an acknowledged (in Twitter by the PMs, not on Known Issues) bug ...
There were two things related to the problem, try Solution-1 and if you still don't see the actions then Solution-2 should do it (as was the case with me).
1 - Add "New Task/Event/Email" buttons to the object Page layouts
View the page layout for the object you want to update. Make sure
buttons for New Task, New Event, Log a Call, and Send an ...
We got an answer from Salesforce on this issue.
Turns out this is a known issue at the time and they are working on it to get these removed soon.
No way at this time that you can remove them yourself.
You might want to contact Salesforce support if it is a real show stopper issue at this time.
The code I used was fine. I found following Known Issue existing for this same issue and it has been Fixed already in the platform now, and the Close behavior is not consistent with this Event firing from any context.
The onFocusedPrimaryTab function is available as one of the "Methods for Application-Level Custom Console Components".
I had tried to add a Visualforce page to the console via the Custom Console Component link for layouts e.g:
I actually needed to add a Custom Console Component via the App | Edit screen
The answer to my question is that yes ...
Indeed, it is true that most custom buttons will not be visible in the Salesforce1 context.
Custom buttons that DO work are those linked to a visualforce page where the standardController is set to the object on which your button is made.
Visualforce pages that don't use this standardcontroller won't work either.
Also keep in mind that your visualforce ...
For a long time, TEXT() didn't support picklist values in certain formula types, including default values, approval processes and workflow rules. The team fixed this around Winter '14, but apparently missed it in predefined fields. I'll file a bug.
In the meantime, if you have Enterprise Edition or above, you can work around it by using a workflow field ...
I have not personally tried this, but I know the User object isn't "normal". For instance, it doesn't support workflows, or inline editing on the page layout, and has locked areas on the page that can't be moved around. My suspicion is that this truly is not implemented yet, but have nothing to confirm that.
That is by design.
According to Salesforce Docs Quick Action Considerations
Actions to create records for an object that is the detail object in a master-detail relationship must be object-specific, not global.
When you create an object-specific action, you can choose as a target object only an event, task, or any object that ...
Leave the JS button as is, and it'll only show on the Classic layout. Create a Lightning Component Quick Action which will read the value from the record and either display the appropriate message or redirect.
As of Summer '15 you can hide the header in Visualforce custom actions by setting the showQuickActionVfHeader attribute to false (see the Summer '15 Release Notes).
So you could hide the buttons and then add a "back" button in your VF page that basically does the same thing as cancelling. Not perfect, but at least less confusing for the end user.
This is most likely due to record types on the Contact object.
Mobile Smart Actions display the standard page layout assigned for an object, taking into account record types and user profiles.
Publisher actions are specific to the record type. If you have record types on a standard object, the out-of-box action will be using the Master record type. Unless ...
As far as I can tell / ascertain - there currently is no supported way to do make the Action / + button appear on a VF page, be it app, global action or record action in S1 Mobile. The screenshot was probably taken back while Salesforce1 was still in beta and overlaying that might have been default then. There are lots of reasons not to do that, mostly the ...
Unfortunately there isn't currently a way to assign an action to a button. sforce.one.createRecord() uses the standard page layout for the profile/record type, not an action layout.
You could fake it out by creating a Visualforce page that dynamically generates the form based on the action layout, something like this (this is a lead because it's code I had ...
Thank you bigassforce for the suggestion. I was having the same problem (my global actions were not appearing, even with refreshing). Solving the problem was as simple as logging out of my salesforce1 app. Once I logged back into the app the custom global action and updated layout was visible and correct.
I came across this problem while running through ...
Global Actions now have their own menu section under Setup | Create | Global Actions. Custom Actions however are still added to Salesforce 1's menu by going to the page layout for the object they're applied to. List views don't have the option to add custom actions as they don't apply to List Views, only to Object Records.
Once you're on the page layout the ...
According to the Trailhead unit Understanding How Actions Work in Lightning Experience:
The Global Actions menu displays a subset of global actions from the
Salesforce1 and Lightning Experience Actions section of the global
publisher layout. Specifically, these types of global actions are
supported in the menu: Log a Call and Create a Record quick actions
If you use CTI, you get this functionality "for free." It works both in Classic and Lightning. And if it isn't good enough, you can write your own Open CTI connector to work in Classic and Lightning. The framework is already there, and there's vendors that already support this, so it's really just a matter of doing research.