Using the salesforce's standard connectAPI and the connectAPI helper class by Alouie helped me solve this. It helped me retain the @mentions and hashtags in the chatter posts that were being posted.
My feedItem Helper class through which I am calling the ConnectAPI and the helper class method to process the chatter posts look like below.
public class ...
This is because the files owned by internal users are being marked as private.
You can read more about this via below article link
Also note that Files is a different than Notes and Attachments. So the settings that you have got is not going to work.
To view a file on a ...
Automated Process such as Process Builder/ Workflow/ Flows won't get trigger if records are touched by Omni-Channel.
In my scenario, cases were getting routing via Omni-Channel to users and when they accepts the case, it doesn't trigger any processes I have built.
Workaround is to create a process on AgentWork object to trigger the Flow. When AgentWork ...
I have come across this answer on the other forums. In case it helps anyone else inf the future.
Unfortunately, it is not possible in Salesforce at this moment. There
is already an idea for this which you can upvote.
Yes, what you're experiencing is a result of standard built-in functionality, these "special" relationships. Note that you're allowed to delete an Account even if you have Cases and/or Opportunities attached to them, so long as there are no Cases or Opportunities with IsClosed equal to false. This is why Restricted Delete appears as "false,&...
If you only want to capture date/time when case owner is changed from Queue -> User, why not leverage the record identifier prefixes?
User records always start with 005
Queues (or Groups) always start with 00G
See reference here.
#1. START: evalute IsChanged for the OwnerId
#2. DECISION: evaluate if previous owner was Queue (Group) and new owner is ...
I believe you're running into this known issue if you're on an Enterprise Edition org - Aura context is not released after Aura Definition is saved
The issue seems to be specific to deploying Aura components and case layouts with the Solutions related list reference at the same time. The workaround is to
Deploy aura components and case layouts separately.
Sorry, I think it's still Out Of Box feature in Salesforce to add a Case.Subject or any caseinformation as prefix in chatter post. Currently In Salesforce, you can create a entire chatter post via Flow, Process Builder and Apex Trigger (You can get those ways via just googling) but we can't add any record information in chatter post as Prefix.
Normally, the ...
Email-to-case always runs Case Assignment rules so all you need is an assignment rule that inspects Subject using Contains operator for Electronic and assign to the new queue.
Note that a case can only have one owner at a time so it can’t be in two queues at once
If your requirement is to have a case assigned to two different queue at a same time then that is not possible.
If requirement is basis certain keywords and assigning it to some specific queue then it shall be pretty straight forward, you just need to set the owner of a case as a required queue basis the keyword availability.