Sayali Sandip Kedar

I my name is. I have been working in Accenture for the past almost 3 years. I have been working as a Salesforce administrator and developer. My inclination was towards configuration because I started with that initially, and that is what I like to do. I've also been in a developer role, but not as much as administration. I hold a Salesforce admin certificate and a financial service cloud accredited professional and Salesforce associate. I would say Salesforce administration is something I excel at because there was, like, for example, I won't name names. I was a go-to person in my team if there was something needed in configuration that wasn't accessible to someone or that someone could not figure out in my team. In Accenture, I've worked with a banking client, and I have worked around 3 teams, starting with insurance, various lines of businesses, starting with the insurance team, then the mortgage team, and then the fraud management team, which was a part of the care center or care center team. It handled case management for our banking client. The client is one of the top 10 banks in the US. So, yes, my background is in computer engineering. I completed computer engineering in 2021. Since then, I have been working in Accenture as a Salesforce admin developer. I was recently promoted in December from associate to analyst role. And, yeah, that is it. I did check the requirements for this role. It was five plus years, but I assure you, configuration is something I excel at, and I would not have applied if I was not confident enough because I have higher standards for myself than the person sitting in front of me always. So, any problem regarding configuration, I'll be there to resolve it. I won't rest till I find a solution to that. Not sales related, but recently, an example I would like to give is: recently, there's a monitor in our bay where we used to work, and my senior manager has been using that monitor for I don't know how many years. There was a tiny floating reminder on that monitor that used to say, input signal should be like, this resolution for the screen. This should be the FPS. And he has been using that for I don't know how long. I asked him, did you try setting the resolution of your laptop to this? He said, yes, I've tried everything, but that monitor seems to be very old, so it doesn't fix. So, one day when my manager didn't come to the office, I just sat for five minutes. I spent five minutes looking at that problem, and I resolved it, which probably he would have done, given his experience, my senior manager has been in the company for 15 years and probably five plus years in the same project. So, yeah, I assure you, configuration is something I excel in Salesforce or otherwise. Thank you.

Plus I want to do a step approval process for discount requests in Salesforce. Okay. I know there are approval processes in Salesforce and Process Builder, multi-set approval process. I have not per se created a process builder or worked on it during my tenure. I worked on workflows and flow builders. So I wouldn't think for now, at least, before looking into it won't take much time, but I've not worked on Process Builders. I know there are approval processes which require you to send out a particular request to whoever is the approver. And based on the basis of what the approver selects, it executes some final steps, which includes rejection of the request or something like that. But yeah, I have not worked on Process Builder.

So, to correct permissions for a new hire in the sales department in Salesforce, depending on what permissions the hire needs, if there's a profile with minimal permissions, that can be assigned to that person until they become acquainted with the required permissions. Otherwise, there's a standard read-only profile available in Salesforce that we can assign. And for the time being, we can add the little permissions that they require from using permission sets. We can add it on top of profiles. And, yes, I mean, profile is the first point and permission sets after that.

Sharing issue, sir. Yeah. I know restricted data access for the team. Complex sharing rules issues that restricted data access for the team. Okay. Firstly, I would check OWDs, organization wide, OWDs, I'll check. After that, I'll check the profile access for the team, data access. Right? So, what depending on what access the team needs, I will go and check that access for them in their profile. If it is not present there, it can be added there. Or, if they, yeah, if sharing rules are causing the issue, I'll check what sharing rules are implemented on that particular object, if it is shared with a particular group of users. I'll see the data access to the team. Okay. I don't think sharing rules will restrict okay. Yeah. Maybe in sharing rules, only if read-only access is provided or something like that could be an issue. I will check that. Yeah. OWD's profile, permission sets, like, if any permission sets are assigned. But permission sets are not used to restrict access, so that will not be something to check. I'll go and check if a particular team is only assigned read-only access instead of edit access. That I will check. And one other thing would be maybe roles, if the team is assigned to a role where they're not allowed to access a particular data for users above them. So that will be something to check. Okay. Yep. I think that should be it. Fair enough. Yes.

Reporting is necessary. Reporting is needed. Reporting. I have created reports in the past. I'm not aware of any particularly complex reporting need. I'll be able to figure it out once I know the use case, but I don't recall a scenario where it was complex and I needed to manage it. Okay. Salesforce tool. Tools will include the reports object. Other tools include data if it's needed to be uploaded in the org, data loader or workbench can be used to insert or observe data. FLS, if it didn't meet requirements. I'll be able to figure it out more if I know what the use case was, but I'm not aware of a particular scenario as of now. Thank you.

Governance standards do you enforce? How do you maintain different users' data quality? What governance standards do you enforce on Salesforce? How do we maintain different users' data quality? To maintain users' data quality, restricting access to objects that are not required by the user can be done. Role management, assignment of roles in terms of what records the user should not be able to access, is done. There's a feature in Salesforce similar to list views, which is called scoping rules, which basically controls what records the user is able to see. For example, there are 3 teams in a particular org. The teams for the users are changed every day. For example, team A, team B, team C. And for example, today I'm assigned to team A. Tomorrow, I'll be assigned to team B. So based on what team I'm assigned to, I should be able to only see the records that belong to team B on that particular day. Scoping rules do not restrict access, but that can be controlled using scoping rules. Users will still be able to search their records from global search. But, yeah, data quality can be controlled using sharing rules. There are restriction rules as well, which I have not worked on. List views is something that can be used to control data quality. We can provide access to users based on the data they require, create list views, and assign the access only to the concerned users. Governance standards.

Troubleshoot and CSS integration issue where the account data is not syncing correctly, with an ERP system. Okay? Troubleshoot a Salesforce integration issue where account data is not syncing correctly with an ERP system. I have not directly worked with this scenario. I am not aware of this scenario. I will have to look into it. I have not worked in this particular scenario, the particular issue directly. So, thank you.

Salesforce is a third-party application that lacks support for Salesforce APIs. Under integration, there are six steps for third-party applications. I do not have much experience with integration, so I am not really aware of what needs to be done here. Thank you.

Implement to handle the cascading updates and deletions of the data integrity across a complex Salesforce relational data model. Strategies would you implement to handle cascading updates and deletions? Strategies would be implemented to handle cascading updates and deletions. Cascading delete is where delete works with a master detail relationship. If a master record is deleted, the lookup data is also deleted. To handle task reading updates, result rate is 80. This can be handled using correct permissions to the users, where they are not allowed to make updates to fields or objects they do not require or should not have access to. Checking relationships among objects, master detail, and lookup relationships where it is not required should be removed. It's getting updates. Going through flows, triggers, and workflows on a particular object, what it is doing, what it is not, that needs to be checked. If changing one object should not be affecting another object. This can be taken care of through controlling access to the users, mainly security and access measures. Record level and field level access should be controlled. Users who do not require delete access should not have them. In my org, end users never had delete access. Only system administrators and integration users had delete access. Not being able to delete a record was one of the things. I think that is all I have.

Salesforce formula fields for large volumes of records without impacting system performance. So, it shows the form of the fields. For a large volume of records without impacting the system performance. Optimize formula fields. I think optimizing formula fields is key. Salesforce formula fields, I know. Acting on system performance. Not adding the field wherever it's not required, on the layouts, for example. Not all layouts require it. Not all users will require the calculation of that formula field. Without impacting the system performance. I need to look into optimizing them; I'm not entirely sure what the question means to ask. I'll need to check.

So I have not directly worked on case management, but there was a POC that I worked on for my clients in insurance for initial insurance, but then mortgage users. For example, leads were to be assigned to mortgage users. There was an age-old round robin in place, the round robin code that was working to assign leads to loan or LOs, loan originators. And they wanted something that was configurable. So I did a POC on omnichannel, which I used. Omnichannel, I did a whole logic based on certain fields that were required on the basis of which it would assign it to the users. Omnichannel is basically used for routing. There are multiple options available in it. On the basis of certain criteria, the people that are added to a queue or a group are assigned the records, which based on availability or based on workload, is assigned to them. A particular record is assigned to them. So omnichannel, I think, is something mainly that is used for case management. And there's also a supervisor console. Also, one thing about omnichannel, it does not work outside console view. It does not work on standard app. It only works on console apps. That is why the idea was rejected, but the POC went well. So, there's also a supervisor view in omnichannel, where you can check, for example, I'm the manager, and there are a team of 5 working under me. I, and that queue I have access to the particular queue where they are added. I can check what records, what cases they are working on, what status it is in since when it is assigned to them. So that way, manually also, the manager can have a view of what the end users are on. What the users are working on, what the employees are working on. Omnichannel is one thing I can think of here. Features. Other features. Omnichannel can be combined with Apex and flows also, so complex logic can be handled that way. There's also assignment rules that are present in setup, in readily available in Salesforce, but that does not allow much flexibility to implement complex logic. So, after if it is not possible using case assignment, it can be done using Omnichannel. These are the two things I'm aware of. Case management. Other things that come along with case that, so that's support processes. Yeah.