Getting Started with Process Builder – Part 5 (Launch a Flow)

Posted on Updated on

Fire

Till now we had discussed about Create a Record, Time-dependent action and Update records using the Process Builder. In this article I am going to discuss another action available in the Process builder i.e. Flows. Process builder allows us to auto launch a Flow. Let’s start with a business use case

Business Use case:- Steve Cartwright is working as System administrator in Universal Container. He receives a requirement to auto update the case owner with Assets owner, if a case is raised for an Asset.

Solution of above business requirement

You can solve the above business requirement through multiple ways. We will use Flow and Process Builder to solve the above business requirement. We have to use Flow, because Process Builder currently doesn’t allows us to update the Owner field. Meanwhile, you can vote for the similar idea Process Builder – Access to Owner Fields. I want to say thanks to Kausar Shaikh for asking such a great question. This article will help you to understand, how to launch a Flow from Process builder. Follow the below instructions to create a Flow and Process for the above business requirement

1. Click on Name | Setup | App Setup | Create | Workflows & Approvals | Flows
2. Click on New Flow, it will open flow canvas for you, now create one Text variable VarT_AssetOwnerId to pass an Asset’s Owner ID, we will use into the flow, as shown in the following screenshot

Text Variable
Text Variable (To store Asset’s Owner ID)

3. Create one more Text variable VarT_CaseId to pass the Case Id, as shown in the following screenshot

Text Variable
Text Variable (To store Case Owner ID)

4. The next step is to update the case owner ID with Asset’s Owner Id, for this we will use Record Update element. Drag-and-drop Record Update Element on the window and fill the details as shown in the following screenshot

Record Update
Record Update (Update Case Owner)

5. Finally your Flow will look like the following screenshot

Launch a Flow

6. Click on the Save button, save the Flow with the name Update Case Owner as shown in the following screenshot

Save the Flow

7. Don’t forget to activate the Flow.

Launch a Flow from the Process Builder

Our next task is to create a Process on Case object to call a Flow. To create a Process on the Case object follow the below instructions

1. Click on Name | Setup | App Setup | Create | Workflows & Approvals | Process Builder  and click on the New button, Enter Name, API Name and click on the Save button

Process Definitions
Process Definitions

2. Next step is to select the Object and Evaluation Criteria, for more detail please take a look from the following screenshot

Evaluation Criteria
Evaluation Criteria

3. Now we have to add Process Criteria into this Process, so that Process will only execute whenever Case.AssetId is null, please take a look of the following screenshot

Process Criteria
Process Criteria

4. Now we have to add an Immediate action into the Process to Launch a Flow. For this use Flows action. Use Field Picker to select the field Description and Text Entry field to enter a comment or sentence. Click on the User object as shown in the following screenshot to select the object

Add action - Flows
Add action – Flows

5. Once you are done activate the Process.
6. Add Asset field on the Case page layout and Grant field access to the users.

It’s time to test this Process

Now onwards if business users create a new case, Process builder will automatically update the case owner based on Asset’s owner if Asset is selected for that particular case.

1. Asset “Demo Record” record is owned by Demo User as shown in the following screenshot

Asset Record
Asset’s Record

2. Now I am going to create a new case for above mentioned Asset from Rakesh Gupta user account, as shown in the following screenshot

Create a Case
Create a Case

3. Once you are doing with data entering, click on the Save button and check the Case owner, as shown in the following screenshot

Case Owner
Case Owner

Likewise, you can update the owner for any records dynamically.

AppExchange app review – One Click Update

Posted on Updated on

Once click update

This is the first time I am writing a blog post on the AppExchange app to share my experience. Last week I got a chance to test few applications, One Click Update is one of them. It allows you to update the records (Only drop-down fields) in one click. The One Click Update application has been developed by Satrang Technologies. The provider is offering the One Click Update app free, to install this application click here. Let’s start with a business use case

Business Use case :- Tamara McCleary is working as Inside Sales Representative in Universal Container on a daily basis, she has to update at least 100+ leads (Random leads) Status. Currently, she is using Inline editing for the same, but she is looking for a way to make this process faster.

Solution of above business requirement

There are few ways to make this process faster. One is to use Data loader, but for this she has to create a .csv file with all the details i.e. time taking process. Another way is to use One Click Update. Let’s see how this application helps Tamara McCleary to save her time. Once System administrator have installed One Click Update application and configured it for lead object. Then it allows business users to update the Picklist (Drop-down) from one click. The design of Once Click Update is simple and elegant, which is nice to have for an app such as this one. It also allow you to select which drop-down field you want to enable for One Click update. It might be possible on a lead object there are 10 drop-down fields are available, but you want to allow your business users to update Drop-down1, Drop-down2 as One Click update fields, this app allows you to do that. In the following screenshot, lead Status is Working – Contacted

Lead Status
Lead Status

If you want to change the status to Closed – Not Converted, then click on the button marked in rectangle.

Nice to have features:-

  • Support dependent picklist.

Note:- Try this app today and don’t forget to share your experience with app provider.

Getting Started with Process Builder – Part 4 (Auto update Chatter email settings)

Posted on Updated on

In Salesforce Chatter is a great way to boost collaboration in your organization. User can Post Status, links, Files and comments on others post. We can also add any number of users in Chatter group. Chatter can email you every time someone follows you, posts to your profile or groups, etc. You can also receive daily or weekly Chatter group email digests for the group you are a member of as well as Personal digest (It contains posts from your feed and up to 3 comments per post) . To receive Chatter email notification and digests System administrator have to enable email notifications for your organization. By default Personal digest is set to Daily and New Chatter groups I join Digest is set to None for new users.

Business Use case :- Tamara McCleary is working as System administrator in Universal Container. She receives a requirement to auto update new use Chatter email settings as mentioned below

a) Frequency for personal digest :- Weekly
b) Default frequency for groups I join :- Email on each post

Solution of above business requirement

There are multiple solutions possible for the above business scenario. You can either use Apex trigger, combination of Flow and Process Builder, and few more. We will use Process Builder to solve the above business requirement. Before proceeding you have to understand User objects in Salesforce.
A) DefaultGroupNotificationFrequency :- This field represents the default frequency for sending the user’s Chatter group email notifications when the user joins groups.
B) DigestFrequency :- This field represents the frequency at which the system sends the user’s Chatter personal email digest.

Possible options for Notification Frequency are
–> Daily Digests
–> Weekly Digests
–> Email On each post
–> Never

Follow the below instructions to create a Process for the above business requirement

1.  Click on Name | Setup | App Setup | Create | Workflows & Approvals | Process Builder
2. To create a new process from scratch, click on the New Button available on Process management page, A popup will open where you have to enter Name (Enter Update Chatter Email Notification as name), API Name and Description as shown in the below screenshot

Define Process Properties
Define Process Properties

3. Once you click on the Save button, it will redirect you to Process canvas. Click on Object node to add object, select User object, in this case and set the evaluation criteria, Please refer to the following screenshot for more details

Evaluation Criteria
Evaluation Criteria

4. The next step is to define Process criteria. For this click on Add Criteria node, enter Criteria Name, Set filter conditions (Similar to Rule Criteria in WFR), as shown in the following screenshot

Process Criteria
Process Criteria

5. Now we have to add an Immediate action into the Process to update the user record. For this use Update Records action, Use Field Picker to select the field Description and Text Entry field to enter a comment or sentence. Click on the User object as shown in the following screenshot to select the object

Select Object
Select Object

Then select the fields Default Notification Frequency when Joining Groups and Chatter Email Highlights Frequency fields, Choose the frequency as shown in the following screenshot

Add action - Update Records
Add action – Update Records

6. Finally the Process will look like the following screenshot, clicking on the Activate button.

Auto update Chatter email settings

It’s time to test this Process

Now onwards if the system administrator creates a new user, Process builder will automatically update their Chatter email notification frequency, as shown in the following screenshot

New Users Chatter email settings
New Users Chatter email settings

Likewise, you can update other preferences for Chatter email notification for new or existing users.

Getting Started with Process Builder – Part 3 (Clone a record)

Posted on Updated on

Clone

Till now we had discussed about Create a Record, Time-dependent action and Update records using the Process Builder. In this article I am going to discuss another business scenario where you can use Process builder i.e. Clone a record. Process builder runs in the system mode and Flow runs in user mode. Let’s start with a business use case

Business Use case:- Steve Cartwright is working as System administrator in Universal Container. He receives a requirement to auto create a new Opportunity (Similar to an old record) whenever an Opportunity is successfully closed and set the Close date for new Opportunity to 120 days from old opportunity’s close date.

Solution of above business requirement

There are multiple solutions possible for the above business scenario. You can either use Apex trigger, combination of Flow and Process Builder, and few more. We will use Process Builder to solve the above business requirement. This is just one level cloning, if you want to implement deep clone (Multilevel cloning) then you have to use Flow or Apex code. This article will help you to understand the way to clone a record using Process builder and concept to use dynamic date in the Process builder. Follow the below instructions to create a Process for the above business requirement

1. Unlike Workflow rule, Process builder doesn’t allow you to use dynamic date on a field update (i.e. Update Records action). For this we have to create a custom formula field 120 After RCD on Opportunity object as shown in the following screenshot

Close Date for new Opportunity
Close Date for new Opportunity

2. Also creates a check-box field One time activity (Default value :- Unchecked), so that Process will fire only once, after successful closure of an Opportunity.
3. To create a Process click on Name | Setup | App Setup | Create | Workflows & Approvals | Process Builder. Click on the New Button available on Process management page, A popup will open where you have to enter a Name (Enter Clone an opportunity as name), API Name and Description as shown in the below screenshot

Define Process Properties
Define Process Properties

5. Once you click on the Save button, it will redirect you to Process canvas. Click on Object node to add object, Select Opportunity object, in this case and set the evaluation criteria, Please refer to the following screenshot for more details

Evaluation criteria
Evaluation criteria

6. The next step is to define Process criteria. For this click on Add Criteria node, enter Criteria Name, Set filter conditions (Similar to Rule Criteria in WFR), as shown in the following screenshot

Process Criteria
Process Criteria

7. Now we have to add an immediate action into the Process to create a case record. For this use Create a Record action, Please refer to the following screenshot for more details

Add action - Create a Record
Add action – Create a Record

Make sure that you have assigned data in the correct format, because Process builder obey Validation rule. If some fields are required by using Validation rule, then make sure that you have added those fields. Same time if some fields are required using Page layout, you can ignore those fields.

8. Next step is to update the One time activity field to True, so Process will not fire if a user is trying to update the Closed Opportunity. For this use Update Records action, Please refer to the following screenshot for more details

Add  action - Update Records
Add action – Update Records

9. Final task is to activate your Process by clicking on the Activate button.

Now onwards if the user will update the Opportunity stage to Closed won, Process builder will automatically create a new Opportunity.

Getting Started with Process Builder – Part 2 (Time-dependent actions)

Posted on Updated on

Time based action

In the last article Getting Started with Process Builder – Part 1 I had discussed the way to auto create a child record. In this article I am going to discuss another concept, i.e. Auto update records and the concept of time-dependent actions in Process Builder. Let’s start with a business use case

Business Use case:- Steve Cartwright is working as System administrator in Universal Container. He receives a requirement to auto update Asset Description (with the sentence “Update the Serial Number “) field after 1 day of its creation, if Asset’s Serial Number is blank.

Solution of above business requirement

To solve the above business requirement, we will use Process Builder. Process builder allowed us to update the record from same object or records from child object or records from parent object (In both the cases master-detail or look-up relationship). Whereas Workflow rule allow us to only update the record from the same object or parent object (In case of master-detail relationship only). At the end of this article I will show you how to track time-dependent actions and the hidden concept behind it. Follow the below instructions to create a Process for the above business requirement

1. Click on Name | Setup | App Setup | Create | Workflows & Approvals | Process Builder
2. To create a new process from scratch, click on the New Button available on Process management page, A popup will open where you have to enter Name (Enter Update Asset description as name), API Name and Description as shown in the below screenshot

Define Process Properties
Define Process Properties

3. Once you click on the Save button, it will redirect you to Process canvas. Click on Object node to add object and set the evaluation criteria, Please refer to the following screenshot for more details

Evaluation Criteria
Evaluation Criteria

4. The next step is to define Process criteria. For this click on Add Criteria node, enter Criteria Name, Set filter conditions (Similar to Rule Criteria in WFR), as shown in the following screenshot

Process Criteria
Process Criteria

5. The next task is to set the time for schedule action. For this click on Set Schedule available under Scheduled actions. Set time for scheduled actions as shown in the following screenshot

Time for Scheduled actions
Time for Scheduled actions

6. Now we have to add a Time-based action into the Process to update the Asset record. For this use Update Records action, Use Field Picker to select the field Description and Text Entry field to enter a comment or sentence. Click on the Asset object as shown in the following screenshot to select the object

Select Object
Select Object

Then select the Description field and enter the comment, Please refer to the following screenshot for more details

Add action - Update Records
Add action – Update Records

7. Finally the Process will look like the following screenshot, clicking on the Activate button.

Update Records

Now onwards if you create an Asset record without Serial Number, It will schedule a time based action to update the records as per your Process design.

It’s time to test this Process

To test this flow, create an Asset record as shown in the following screenshot

Create a new Asset record
Create a new Asset record

Flow created by Process builder and Time-dependent Queue for Process Builder

In the last article Getting Started with Process Builder – Part 1 I had discussed the way to see the Flow created by  Process Builder for any particular Process. Follow the below instruction to open the Flow created by Process Builder and understand the concept of time-dependent action in Process Builder

1) Below is the Flow created by Process Builder see the Type i.e. Workflow different from normal (Flow or Autolaunched Flow). Now click on the Open link as shown in the following screenshot

Flow Created by Process builder
Flow Created by Process builder

2) It will open the Flow, which is generated by Process Builder for the Process we have created. There are two SObject Variables created by Process to pass old and New Id of record to Flow. If you check the flow very carefully, you can find there is a Wait Element used in the Flow as shown in the following screenshot

Flow detail view
Flow detail view

3) If you are working on a Flow and wants to wait for a few hours or days to complete a specific process then you have to use Wait element. Wait Element is basically used to create time-dependent actions in the Flow, and this is used in Process builder for the same. It means Process Builder use Wait Element to create time-dependent actions, i.e. updates Asset record after 1 day of its creation in our case, please refer to the following screenshot for more details

Wait Element - To Create Time-based action
Wait Element – To Create Time-based action

4) As soon as you create a new Asset record and if it’s meet the Process entry criteria, it will schedule an action for the next day.
5) To check the Paused and Waiting Interviews in the Flow, click on Setup | App Setup | Create | Workflows & Approvals | Flows navigate to a section Paused and Waiting Interviews as shown in the following screenshot

Paused and Waiting Interviews
Paused and Waiting Interviews

The same concepts apply to Process Builder time-dependent actions because it’s nothing but wait element. Use Paused and Waiting Interviews to monitor Scheduled actions from Process Builder.

6) If you click on Name, it will open the detail page for you, as shown in the following screenshot

Waiting Element detail page
Waiting Element detail page

It also allows you to edit the page layout by clicking on Edit Layout link, available on top right corner of the page.

7) To remove a record from scheduled action, click on the delete link, as shown in the following screenshot

Remove a record from scheduled action
Remove a record from scheduled action

Note : – This is my finding and only for learning purpose. Don’t delete any actions or Flows.

Getting Started with Process Builder – Part 1 (Auto Create a record)

Posted on Updated on

Idea

The purpose of this article is to discuss about Process builder. Process builder is generally available for use, after Spring’15 release. From today onwards I am going to start a series of blog post on Process builder, I will try to post at-least one article per week related to it.

What is Process Builder ?

Process builder is a combination of Flow and Workflow rule. In other word we can say that it’s a next level of Workflow rule, that allows us to automate your business process by creating Processes with point-and-click.

How to enable Process builder ?

Process builder is only available in Enterprise, Unlimited, Performance and Developer editions. After Spring’15 release it will generally available for above mentioned editions.

Why Process builder?

Workflow rule has a few limitations like using WFR you can’t create child record, Post to Chatter or Auto submit record in Approval process. Let’s start with a business use case

Business Use case :-  Corey Eridon is working as System administrator in Universal Container. She receives a requirement to auto create a child case whenever a new case is created with Case Reason Breakdown.

Solution of above business requirement

To solve this requirement, we will use Process Builder. Whenever we create a Process using Process builder Salesforce auto create a Flow and Workflow rule (With an action) to fire it. At the end of this article I will show you how to view Flow and Workflow action created by System for Process. Follow the below instructions to create a Process for the above business requirement

1. Click on Name | Setup | App Setup | Create | Workflows & Approvals | Process Builder
2. To create a new process from scratch, click on the New Button available on Process management page, A popup will open where you have to enter Name (Enter Create_Child_case_for_Breakdown as name), API Name and Description as shown in the below screenshot

Define Process Properties
Define Process Properties

3. Once you are click on the Save button, it will redirect you to Process canvas. Click on Object node to add object and set the evaluation criteria, Please refer to the following screenshot for more details

Evaluation criteria
Evaluation criteria

4. The next step is to define Process criteria. For this click on Add Criteria node, enter Criteria Name, Set filter conditions (Similar to Rule Criteria in WFR), as shown in the following screenshot

Process Criteria
Process Criteria

5. Now we have to add an Immediate action into the Process to create a case record. For this use Create a Record action, Please refer to the following screenshot for more details

Add action - Create a Record
Add action – Create a Record

Make sure that you have assigned data in the correct format, because Process builder obey Validation rule. If some fields are required by using Validation rule, then make sure than you have added those fields. Same time if some fields are required using Page layout, you can ignore those fields.

6. Final task is to activate your Process by clicking on the Activate button.

Now onwards if you create a case with Case Reason Breakdown, Process will auto create a child case for it.

Flow and Workflow action created by Process builder

1. There are two ways that I am aware of, to see the Flow generated by Process Builder for current Process, those are Package or Change Sets. Now I am going to create a package, don’t worry it is very easy. Follow the path to create a Package
2. Click on Setup | Build | Create | Packages and click on the New button, enter the Package Name, as shown in the following screenshot

Create a new Package
Create a new Package

3. Click on the Add button available under Component, as shown in the following screenshot

Add Components to Package
Add Components to Package

4. From Component Type drop-down select Flow, and click on the Flow we have created, i.e. Create_Child_case_for_Breakdown as shown in the following

List of active Flows and Processes
List of active Flows and Processes

5. It will redirect you to the Flow detail page, see the Type i.e. Workflow different from normal (Flow or Autolaunched Flow). Now click on the Open link as shown in the following screenshot

Flow Created by Process builder
Flow Created by Process builder

6. It will open the Flow, which is generated by Process Builder for the Process we have created. There are two SObject Variables created by Process to pass old and New Id of record to Flow

Create_Child_case_for_Breakdown Flow
Create_Child_case_for_Breakdown Flow

7. To check Workflow action, use this URL https://gs0.salesforce.com/09M, change the Salesforce instance, as per your current organization instance. I have created a custom view to see additional details

Workflow action to call a Flow
Workflow action to call a Flow

8. If you click on the Edit link, it will look like the following screenshot

Edit action Flow param
Edit action Flow Param

Note : – This is my finding and only for learning purpose. Don’t delete any actions or Flows.

Out of Office notification for Chatter post

Posted on Updated on

OOOAn Out of Office notification, allows you to set an automatic reply message when you are away. You can do these settings in your email account, but there is no such settings available in Salesforce. There are a few app available on AppExchange for this purpose. After Spring’15 release you can create workflow Rule or Process (PB) on FeedItem object.

Business Use case :-  Corey Eridon is working as System administrator in Universal Container. She got an email from higher management, they wants to implement Out of Office notification for Chatter post. It means if a user is out of office and every time someone mention him on a Chatter post (Chatter wall, TextPost or LinkPost etc.) auto post an automatic Out-of-Office comment. Similar to the below screenshot

Out of Office Notification for Chatter Post
Out of Office Notification for Chatter Post

Solution of above business requirement

To solve this requirement, we will use Visual Workflow, Process builder to call a Flow. Before proceeding you have to understand FeedItem objects in Salesforce.

1. First of all create a custom object (Out_Of_Office__c) set the Name as Text, and few fields to save the Out of Office message, Start Date, End Date, as shown in the following screenshot

Custom Object (To save OOO details)
Custom Object (To save OOO details)

Note :- Set OWD to Private for Out of office object. Ask your business users to create only one record and edit the record when they want to set the Out of Office message.
2 Next step is to create a flow to post Out of Office message in Chatter post. Click on Name | Setup | App Setup | Create | Workflows & Approvals | Flows
3. Click on New Flow, it will open flow canvas for you
4 Now create two Text variable with name FeedBody and FeedItem__ID we will use into the flow, as shown in the following screenshot

Flow Variables
Flow Variables

5. Drag-and-drop a Record Lookup (Give the name Get Feedbody) on the window, to get the body from Chatter post. Map the fields according to the following screenshot

  • Select Object FeedItem
  • Enter criteria Id{!FeedItem_ID}
  • Save Body into a variable {!FeedBody}, Please refer to the following screenshot for more details
Record Lookup - To get FeedBody
Record Lookup – To get FeedBody

6. The next task is to get all Out of Office messages, created in the custom object Out of office. To do that Drag-and-drop a Fast Lookup ( Give the name OOO_Messages) on the window and map the fields according to the following screenshot

  • Select Object Out_Of_Office__c
  • Enter criteria Start_Date__c <= {!$Flow.CurrentDate}, End_Date__c >= {!$Flow.CurrentDate}, and Name != {!$GlobalConstant.EmptyString}
  • Save the details in a SObject Collection Variable {!OOO_Details}, also select fields Start_ date__c, End_Date__c, Name, CreatedById, OOO_Message__C. Please refer to the following screenshot for more details
Fast Lookup -To get OOO messages
Fast Lookup -To get OOO messages

7. Now drag-and-drop Decision Element (Give the name Check SObject Collection Variable) to check the SObject Collection Variable {!OOO_Details} is Null or not, if it’s not null then go to the next step. Please refer to the following screenshot for more details

Decision Element - To Check SObject Collection Variable
Decision Element – To Check SObject Collection Variable

8. Drag-and-drop a Loop Element (Give the name Extract ID one by one) on the window and extract IDs from SObject Collection Variable and pass it to SObject Variable variable, as shown in the following screenshot

Loop Element
Loop Element

9. Now drag-and-drop Decision Element (Give the name To Check FeedBody with OOO Usres Deatils) to check the Variable {!FeedBody} contains names that mentioned in Out of office object records (i.e. On the field Name) Please refer to the following screenshot for more details

Decision Element
Decision Element

10. If a User Name mentioned in Chatter post and there is an Out of Office message is found in the Out of office object for the same user, then add the user details into a  SObject Variable {!SingleUserDetails}. To do that Drag-and-drop Assignment Element ( Give the name One by one assignment) onto the window and map the field according to the following screenshot

Assign Detail in one SObject Collection
Assign Detail in one SObject Collection

11. Drag-and-drop Assignment Logic (Give the name All in one) on the window and assign value from SObject Variable {!SingleUserDetails} to Sobject Collection Variable {!All_Record_In_One} (FeedItem Object Type) so at the end of the flow will use it inside the Fast Create to post OOO messages altogether. Please refer to the following screenshot for more details

Add SObject Variables into a SObject Collection
Add SObject Variables into a SObject Collection

12. Finally drag-and-drop Fast Create (Give the name Post Out of Office notification for Chatter post ) on the window and map the field according to the below screenshot

Out of Office notification for Chatter post
Out of Office notification for Chatter post

13. Finally the Flow will look like the following screenshot

Out of Office notification for Chatter post

14. Save the flow with name Out of Office notification for Chatter post and close the canvas.

Call a Flow from Process Builder

Our next task is to create a Process on FeedItem object to call a Flow. To create a Process on the FeedItem object follow the below instructions

1. Click on Name | Setup | App Setup | Create | Workflows & Approvals | Process Builder  and click on the New button, Enter Name, API Name and click on the Save button
2. Click on Add Object, select FeedItem object and for the entry criteria, Select when a record is created or edited, as shown in the below screenshot and also click on the Save button

Record Evaluation Criteria
Record Evaluation Criteria

3. The next task is to add process criteria, To do this click on Add Criteria, enter Name, Type of action and set filter conditions  (In this case set [FeedItem].Type Equal to TextPost and [FeedItem].Type Equal to LinkPost with OR conditions) and click on the Save button, as shown in the following screenshot

Process Criteria
Process Criteria

4. Our final task is to add Immediate action to Process. Click on Add Action (Under Immediate actions), Select the type of action to create (In our case Flows) , and then fill out the fields to define the action, as shown in the following screenshot

Process Actions
Process Actions

5. Click on the Save  button and then activate it.

It’s time to test this flow

To test this flow, follow the below instructions

1. Create OOO messages for few users in Out of office object, as shown in the following screenshot

Out of Office Messages
Out of Office Messages

2. Create a TextPost or LinkPost any where on Chatter (Either on User Profile, Group or Records) and mention the few users for whom you have created Out of Office messages

Final Output
Final Output

Note :-I will suggest you to Implement this first on your developer org test it and then move it to Production.