Saravana Amuthu

Hi. Myself is Saravan Amudu. I have a total of 6 years of experience working in Salesforce ecosystem. In my previous experience, I have worked with companies like Accenture and Cognizant in multiple projects. I have worked on Salesforce configuration and went into customization as well. I have, uh, worked on building objects, uh, fields, other automation tools like workflow process builder and flows in 1. Also, I have, uh, worked on security settings like object level security, fail level security, and, like, all level security. In 1 of my client's project, I was involved in maintenance releases. I have successfully deployed 25 plus releases. These maintenance releases are nothing but small enhancements, which involves configuration as well as customization. So what I do in those maintenance releases is that I start with analyzing the requirement from the client. So we have a deck prepared by the business analyst. I go through the deck, and I understand the requirement. And I specify the, uh, uh, components which are needed to be built along with the efforts needed to build it. So after that, I build. I push it to QA and UAT using AutoRabbit. And after that, I work closely with the user for user action testing, which is UAT. Then I use auto rabbit for deployment. In my current role with the video, I'm mostly into support side of Salesforce. So we daily deal with requestings and queries or some issues from other teams which are using Salesforce within Folio, like sales team, finance team, etcetera. Uh, We handle the cases raised by them or the emails put to us. We reply the emails. We have a separate case management system within Salesforce. And apart from that, I'm involved in minor enhancements bill, which follows a joint methodology. So I am also involved in solving after CPQ related questions as well. I used to, uh, provision prospecting tools like Outreach, lead IQs, ZoomInfo, false sales team. So, currently, I'm based out of Bangalore. I work mostly in APJ timing, but I'm comfortable with any kind of job. Thank you.

Okay. So to handle customer queries including email, chat, and phone calls, uh, for emails, we can go with email to case, which is already in Salesforce. We can enable it, and we can, uh, put a deal for that. And whenever the customer sends an email to that particular deal which has been set up, It gets created as a Salesforce case. And for chat, we can, uh, use the chatter function, which is already available in Salesforce. We can assign the user with the charter license. And for phone calls, I'm sure that there is something available over service load, which request license, which I am not sure about, which I have not worked on. So I'll need to look more into the phone calls.

I have, uh, not really worked with Salesforce integration with 3rd party. I'll need to look into the Salesforce APIs.

Okay. So whenever there is this new sales process or release, we'll have the release notes, and we can circulate, uh, with the internal Salesforce team first and come up, uh, with any blockers, uh, with the existing implementation. If there is something going to block the business, we can send out the communication to the stakeholders asking saying that, uh, there is something new implemented from the Salesforce side, and we'll need, uh, certain x number of days to get it changed or get it upgraded. And after that, uh, we can break the entire requirement into user stories and assign it to the team and work on it, which goes for your agile process or whatever the existing process is. And it should go it should be done first in the dev sandbox and then goes to the UAT and gets deployed to the production.

Sure. So I used to work with finance team, and their major requirement is to track the approvals and the time needed, uh, for each and every approval. So what is the time lag between each and every approval? In my in my company, there is a department which handles credit related issues. So they are mostly looking forward for the approval process. But what they really look forward is the approval process and the time required for each and up, uh, each and every step. What's the time required to complete it, and where is the delay? They they are looking forward to cut off the delay. So, uh, in this case, approval process is related to, uh, certain object called credit check, but I can get the approval process step and the dates on the number of days elapsed between each and every step. But I can give you I can give the user only the credit check number or the record number, yes, specifically. But I cannot give the, uh, all information of the related record. Let's say credit check-in this case. So I had created a report with the steps and, uh, 1 of each and every step and the days which took for the user to complete the step with the corresponding, uh, credit check. So this report was a little bit helpful, though it did not match the exact requirement. So I had given the report saying that you can look forward for the days elapsed, which is the major priority for you than the information which is product present in credit check. The users were okay with that, and it was, uh, reducing their time, uh, at least by 60%. Previously, they were manually exporting all the records and comparing it with it with their own Excel sheet and everything. It had reduced their time by 60% using this report.

Okay. Process builder. Today, you stopped in the context of Apple process. I I would suggest, um, going with flows would be a better option, or using a approval process separately would be a better option because, uh, process builder is, uh, kind of, like, getting the commission. So flows would be a better option when we are going for multistep approval, or we can use a standard approval process for discount request. In my company, we use Aptis approval request, which is more helpful for multistep, uh, discounts in coming to billing or sending out, uh, order form to the customer. But coming to some things related to, uh, credit check or so when the, uh, customer's looking to buy some product on credit, we use standard approval process.

Okay. So we can either do via profile or permission check. So for new hire into sales department, uh, we usually have a process where when they are onboarded, by default, they get Salesforce. And after that, to set up, uh, correct permissions within Salesforce, We compare their portion, uh, over Workday and take the permissions of their existing coworker and copy the same permissions for them. So this would involve copy copying the same profile for the new hire who is getting onboarded to the same team and also other permissions, it's which are already existing. So we take a different user who is already existing in the team and copy the same permissions for the new user who is getting onboard.

Okay. Sure. Profiles and roles are completely different. Profiles are mostly into object and field level security, and roles are into record level security. So, uh, to give a visibility of a field or control over an object, we use profile. For example, there is object on account, and there are, uh, let's say, 10 fields. Uh, a user, uh, needs control over 5 fields, but should be able to edit only those 5 fields and read the have the read access over other fields. Then we'll assign read access to all the fields over profile and give edit access to those 5 fields. For example, uh, let's say there is a manager and there are 5 subordinates, and the manager should have access to edit all the fields which are entered in the particular record. And he should also be able to see their subordinates record. So in this case, so manager will have a manager profile, and the subordinates will have, let's say, uh, team member's profile. So team member's profile will have read access and edit access to certain fields, which they are supposed to input their, uh, inputs from their side. And the manager can also edit and also see. We go for 2 different profiles. For roles, manager will have a manager role, and the team's subordinates will have team member's role. So team member's role for that particular object, it will be set to, uh, private for, uh, team member's role, and the manager will have access via hierarchy. So he can see every team member's record, but the team member is subjected to see only his or her records because it is set private. So by this way, uh, role and profile are helpful.

Okay. Just getting updates and deletion while preserving the tag. Okay. So come come coming to updates, uh, basically, we use tools like data loader or data inspector. So we would always have multiple demo operations going on in objects. So whenever something is changing a record, depending on the condition, it could be from flow or process builder or it could be from triggers. So it's always, uh, wise to reduce the batch size so that we don't, uh, try to update the record again and again and get into multiple DML error issue and complete con and coming to deletion. It really depends upon, uh, what all data I would like to delete. Maybe the incomplete data can be deleted. So this is my understanding. I'm not, uh, really sure about this.

Okay. Uh, mitigate government limits. Okay. Um, while doing data migration, the government limit, which we mostly get is that, uh, too more too many SQL queries that that would be the most, uh, issue which we would come across. So in that case, it's very good to optimize the DML operations which are already set up in the system. This could include effects and, um, flows and whichever automation tool which requires to collect in collect the data. So the gate operation, which is in Apex and flows also, we have a get records operation. And, also, we have update operations and create data, create a record, uh, function. So first is to optimize those. And recently, we have been going through optimization of flow project. So where we identified, uh, several flows which are trying to update the update a particular record based on certain condition, which are clapped over there. And whichever DML operations are happening separately, we had put it into a, uh, same flow so that it doesn't fall 2 flows. So in that case, the DML operations can be reduced.

Okay. Okay. So formula fields are something which, uh, comes in comes early in the order of execution. So formula fields are to be optimized in such a way that it could handle raw volume of record without, uh, impacting the system. For that, uh, I really need to think about that. Maybe we can, uh, put more filters on based on what criteria this formula should be calculated. Or, uh, it's better not to have much form of things.