[SalesForce] Create Chatter post with mix of HyperLinks and text in the Body (in Apex code)

How to create a chatter post in the body I want to add Links in between. (in Apex code)

its not complete link or complete plain text. I am looking at mix of both

Example Chatter post –

just has call with John[link to contact here] and closed opportunity name[link to opportunity ]

Update – its not simple chatter post with LinkUrl (the one suggested in reply is very easy)

I need final chatter post to look like as follows – (basically with hyperlinks)

just has call with John and closed opportunity name

Best Answer

So, I haven't actually tried this, but here's what I would try first:

FeedItem myPost = new FeedItem();
myPost.Parentid = object.Id; //user's Id I'm assuming
myPost.body = 'Text here http://www.internets.com more text http://www.theinternets.com';
insert myPost;

Obviously, you'd have to get the Id of the object you're posting to and the links to the contact and opportunity.

Related Solutions

[SalesForce] Losing @ mentions in apex trigger on FeedItem

Hashtags are parsed out of plain text, but you need to use the Connect (Chatter API) or REST API to post mentions.

I've answered a similar question here, which might help.

Copy the FeedBodyParser Utility Class from http://developer.force.com/cookbook/recipe/connect-in-apex-pilot

Then to post a mention simply use

ConnectApi.FeedItemInput feedItemInput = FeedBodyParser.convertToFeedItemInput('Hello @[Ritesh Aswaney](user:005i0000000nEVV)');      
ConnectApi.ChatterFeeds.postFeedItem(null, ConnectApi.FeedType.News, 'me', feedItemInput, null);

[SalesForce] Custom VF Page for Publisher Action to Create Post on Chatter Group linked to Opportunity

Yes. You can do all of that. Take a look at the help page on creating VF pages for custom actions for some good examples.

You would need to make a Controller Extension to be able to access the Opportunity in context. The controller you posted is a Custom Controller. Once you have the Controller Extension and page written you can then add it as a Object-Specific Action. See the docs on Customer Controllers and Controller Extensions for more information.

You may want to associate the post with your Opportunity rather than the Group. I've included Visualforce pages for both scenarios. If you do want to do the group you can avoid asking for the ID by storing the Group Id in a Custom Setting. Technically, you could just hardcode it in your source, but that's not as maintainable.

Controller Code

public with sharing class OpportunityChatterPostController {
    public String detail { get; set;}
    public Opportunity opp { get; set; }
    public String groupId { get; set; }
    public String message { get; set; }

    public OpportunityChatterPostController(ApexPages.StandardController controller) {
        opp = (Opportunity) controller.getRecord();

        // get this value from a Custom Setting
        groupId = Your_Custom_Setting__c.getInstance().Group_Id__c;
    }

    public PageReference doPost() {
        FeedItem fItem = new FeedItem();

        // alternatively, if you want this to show up in the
        // Opportunity's feed then change to set parent to OppId
        // fItem.parentId = opp.Id;

        fItem.parentId = groupId;

        fItem.body = detail + ' Opportunity: ' + System.URL.getSalesforceBaseUrl().toExternalForm() + '/' + opp.Id;

        insert fItem;

        return null;
    }
}

Visualforce Code to use if posting to Group Feed (no refresh needed)

<apex:page standardController="Opportunity" extensions="OpportunityChatterPostController" showHeader="false">

  <apex:form >
    <apex:pageBlock >
      <apex:pageBlockButtons >
        <apex:commandButton value="Post" action="{!doPost}" />
      </apex:pageBlockButtons>

      <apex:pageBlockSection columns="1">
         <apex:outputLabel value="Path to Win"/>
         <apex:inputText value="{!detail}" style="width: 255px !important;" />
      </apex:pageBlockSection>
   </apex:pageBlock>
 </apex:form>

</apex:page>

Visualforce Code to use if posting to Opportunity Feed (refresh needed)

<apex:page standardController="Opportunity" extensions="OpportunityChatterPostController" showHeader="false">

  <script type='text/javascript' src='/canvas/sdk/js/publisher.js'/> 
  <script> 
        function refreshFeed() { 
            Sfdc.canvas.publisher.publish({name : 'publisher.refresh', payload : {feed:true}}); 
        }
  </script>   

  <apex:form >
    <apex:pageBlock >
      <apex:pageBlockButtons >
        <apex:commandButton value="Post" action="{!doPost}" oncomplete="refreshFeed();"/>
      </apex:pageBlockButtons>

      <apex:pageBlockSection columns="1">
         <apex:outputLabel value="Path to Win"/>
         <apex:inputText value="{!detail}" style="width: 255px !important;" />
      </apex:pageBlockSection>
   </apex:pageBlock>
 </apex:form>

</apex:page>

The second Visualforce page refreshes the feed on the Opportunity in the onComplete function of the apex:commandButton, after the FeedItem is inserted. If that is left out the feed doesn't get updated and the user won't see the FeedItem just created. In the first page you'd be posting to the Group's feed so there's no need to update the Opportunity's feed. That's the only difference between the two Visualforce pages.

Also, make sure that all profiles that need to use the action have access to the Visualforce Page.