Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

likeMessage(param)

Updated on July 20, 2021

Likes or unlikes a message.

Returns

Not applicable.

Parameters

Usage example

NameTypeDescriptionRequired
paramobjectThe object that contains all the required data to like or unlike a specific message.

The following table contains the properties of the param object:

NameTypeDescriptionRequired
pulseContextstringThe name of the application context or case context for which the feed must be fetched.
likedBybooleanThe value that determines whether to like or unlike the message.
Note:
  • Set likedBy to false if you want to like a message.
  • Set likedBy to true if you want to unlike a message.
messageIDstringThe ID of the message that needs to be liked or unliked.
isReplybooleanThe flag that determines whether the number of likes must be obtained for a message or a reply to a message.
Note:
  • The default value is false.
  • Set isReply to true if you want to obtain the number of likes for a reply to a message.
  • Set isReply to false if you want to obtain the number of likes for a message.
c11nEnvobjectThe name of the context where the API is being called.

Usage example

In this example, the API likes the message whose ID is W-103.

PCore.getFeedUtils().likeMessage({pulseContext:'DATA-PORTAL', likedBy: 'likeFeedMessages', messageID:'W-103', isReply:'false', c11nEnv:'app/primary_1'})
.then(() => {
   // success
}).catch(err => {
  // errors
});
  • Previous topic getTagSuggestions(tagProps, c11nEnv)
  • Next topic postMessage(pulseContext, message, attachmentIDs, isReply, c11nEnv)

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us