4

You should be able to use the "Create Record" publisher action to define all the fields you want. You won't need to to use sforce.one.navigateToURL() to do this (and it wouldn't work as it doesn't allow you to specify a full url). Note, you also shouldn't need to use a custom Visualforce page as you can define all the fields you need on the publisher action ...


3

What you are trying to do is referred to as URL hacking, which is not supported by Salesforce. You are correct that your solution could break should Salesforce make any backend changes. I would propose that rather than trying to use URLFOR() to account for this, you look into using Publisher Actions. Publisher actions all but make URL hacking a thing of ...


3

As per the documentation here and here (more useful methods) It dictates that you use the method: sforce.one.navigateToSObject([RECORD_ID_HERE]); To navigate to the SObject. For your case, use: sforce.one.navigateToSObject(result[0].id); I've also used: Sfdc.canvas.publisher.publish({name: "publisher.close", payload:{ refresh:"true"}}); to refresh an ...


3

Finally i found the Answer - We need to change "Email Deliverability" Settings to "All Emails" instead of System Emails or No Access.


3

You must set the NetworkID on your ChatterPost for it to show up in the community. Posts are scoped according to this. Try querying the CommunityID.


3

The reason it's because a Quote Object is always related to an Opportunity via a master relationship. It's a bit like Opportunity Product, you can't create a publisher action for that object too. I'm not sure what's your business logic, but you might create your publisher action on your opportunity instead, and with some logic redirect you to the right ...


2

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 ...


2

Your problem is solved as of Summer15. The page layout editor now has two places for actions--one for the feed, and another for the action bar. http://docs.releasenotes.salesforce.com/en-us/summer15/release-notes/rn_mobile_salesforce1_newfeat_actionbar_customization.htm


2

Just discovered this is indeed a known issue with Salesforce, https://success.salesforce.com/issues_view?id=a1p30000000T3uIAAS


2

Email button is not showing since you are using global email action in the Quick Action. If you can closely look into the properties, you will see like this. Remove that action from page layout Go to Support Settings and choose Enable Case Feed Actions and Feed Items : When you select this option, you will go the feed based page layout and will see a new ...


1

Make sure in the top left panel, you have selected the Mobile & Lightning Action item. Otherwise it will not allow you to add. Please refer below -


1

In its current beta implementation there is no way to hook Lightning Components into the publisher actions feature. This will no doubt be part of some release in the near future as it is a key part of the Salesforce1 mobile UI. But currently the only way to surface a Lightning Component in the S1 mobile UI is as a tab surfaced as an item in the left hand ...


1

adi, PageReference redirect is meant only for full site navigation. Salesforce1 mobile navigation is handled thru sforce.one javascript library methods Since in your case you are directing to the records detail page, you can use the navigateToSObject method and pass in the record id. If you are using this page between both S1 and full site, there are ...


1

You have to enable Email-to-Case in order to have this functionality. Please go to Setup-->Case--> Email-to-Case Enable Email-To-Case checkbox. Then go to the Case Page layout, you will find the option to add email quick action.


1

On your custom publisher action Setup > App Setup > Customize > Cases > Buttons, Links, Actions and select the publisher action, add a property in Predefined Field Values. Here you will select the field you want to pre-define (Subject in your case), and define the value ("" in your case which tells system that the value should be blank). If you ...


1

Create a new VF page that simply renders the standard layout using <apex:detail>, but has some additional logic that inspects the URL parameters to determine if the publisher should be expanded (and if so, runs the additional JS code you spotted) Now from the original VF page you can redirect to the standard VIEW page reference, but adding a new param ...


1

This is a known issue with Salesforce: https://success.salesforce.com/issues_view?id=a1p30000000jgjpAAA EmailMessages show HTML mark-up in the feed view Summary Case Console Feed View email tracking is showing HTML mark-up with emails sent from/received to the case related lists, as of Spring '16. Repro 1) Enable Email-To-Case 2) Enable HTML emails 3) ...


1

Easiest way to do this is via Process Builder. There is a Post to Chatter action! So simple and easy to use... just set your criteria (when a case is changed to escalated) and then set the action after that happens. Other options are to trigger a Flow from Process Builder to do the post (that doesn't really make too much sense unless you're doing queries ...


1

The first things I check when I don't see the quick-actions I expect to see are do I have the permissions to make the change? for create-record actions, is the record type specified on the quick-action one that is assigned to my profile? It doesn't seem as if the second applies here. But if you are working in a sandbox and you have Email Deliverability set ...


1

In the end this was not possible without totally rebuilding the text input with our own chatter action. What we did was added a trigger on the chatter objects so that if someone posted a message without including a hashtag #Public it would throw and error saying that "This post is potentially visible by anyone in the org. Please add #Public to your post to ...


1

Figured it out, here's my code: VF Page: <apex:page standardcontroller="Account" extensions="Acct_Action_Extension" sidebar="false" showHeader="false"> <apex:form > <apex:sectionHeader title="Create Drop-In Meeting"> <apex:pageBlock title="New Event"> <apex:commandButton value="Create Drop-In Event" action="{!...


1

You won't be able to do this declaratively with the standard Create quick action -- those can only create a single record (the Event record), not add the attendees. You should be able to do this programmatically with a custom Visualforce quick action. Because you're writing the action UI from scratch (and a controller), you could create a form allowing the ...


1

Just tried below thing instead of eventListner and it worked fine for my use case. See if it would help you. This code snippet passes the Hello world event to the action my_custom_action. Sfdc.canvas.publisher.publish({name:"publisher.customActionMessage", payload:{actionName:"my_custom_action", message:"Hello world"}}); This code snippet is what ...


1

Did you enable Case Feeds under Cases, support settings? Enable Case Feed Actions and Feed Items If you didn't do this - you have to go thru this process - and I would read up on it before you do. If you have done this, and you are trying to use basic email in case feed(s) then I wish you luck. Because so far the implementation of email based ...


1

How to Create Object and Global Actions is well documented in numerous tutorials provided by Salesforce including the Salesforce 1 App Developer Guide and the Force.com Platform Fundamentals. Between those two documents, I'd expect you to find the guidance you seek. If you have a more specific question, then please come back and post for help with it. As ...


1

Not at this time, sorry. Jody


1

Welcome to SF.SE user12128. There are two types of Publisher Actions of the type you speak of, Global Actions and Object Specific Actions. The latter can only appear on Detail Pages. Global Actions can appear anywhere, including on Detail Pages. They're both discussed in depth, including how to enable them in Chapter 8 of the Force.com Platform Fundamentals ...


Only top voted, non community-wiki answers of a minimum length are eligible