Sayali Sandip Kedar

Thanks. Sorry. Uh, yes. So, uh, I my name is. I have been working in Accenture for the past, uh, almost 3 years. Uh, I have been working as Salesforce administrator and developer. Uh, my more, uh, more of my inclination was towards, uh, configuration because I started with that initially, uh, and that is what I like to do. Uh, I've also been in developer role, uh, but not much much as administration. Uh, I hold Salesforce admin certificate and, uh, financial service cloud accredited professional and Salesforce associate. Uh, I would say Salesforce administration is something I excel at, uh, because there was, like for ex I won't, uh, now name names. Okay. Whatever. Uh, I was a go to person, uh, in my team, uh, if there was something needed in configuration that, uh, that was, uh, that wasn't accessible to someone or that, uh, someone could not figure out in my team. I have, uh, in Accenture, I've worked with a banking client, uh, and I have worked around 3 teams, uh, starting with insurance, uh, various, uh, line of businesses, starting with the insurance, then mortgage, and then fraud management, uh, which was a part of, uh, care center or care center team. It handled the case management for, uh, for our banking client. It was, uh, the client is 1 of the top 10 banks of US. So, yes, uh, my background, uh, is in computer engineering. Uh, I, uh, yeah, I completed computer engineering in 2021. Since then, I have been working in Accenture as a Salesforce, uh, admin developer. I was recently promoted in December, uh, from associate to analyst role. And, yeah, that is it. I did, uh, check the requirements for this role. It was 5 plus years, but I assure you, uh, configuration is something I excel at, and I would not see it if I was not confident enough because I have more higher standards for myself, uh, than the person sitting in front of me always. So any, uh, any problem regarding configuration, I'll be there to resolve it. I'll I cannot rest till I find a solution to that. Not sales related, but recently, uh, so 1 of the examples I would like to give, uh, is recently, uh, I there's a monitor, uh, in our bay where we used to work, and my senior manager, uh, has been using that monitor for I don't know how many years. Uh, there was a tiny floating remind tiny floating warning, uh, continuously floating warning on those, uh, monitor that used to say, uh, input signal should be like, these this should be the resolution for the screen. This should be the, uh, FPS. And he has been using that for, uh, I don't know how much how long. I asked him, did you, uh, 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 does not, uh, it does not fix. So 1 day when, uh, my manager did not come to the office, I just sat 5 minutes. I spent 5 minutes looking to that problem, and I resolved it, which, uh, probably he would have been he's, uh, also my senior manager has been in the company for 15 years and probably 5 plus years in the same project. So, yeah, I, uh, I assure you configuration is something I excel in in Salesforce or otherwise. Thank you.

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

Uh, so correct permissions for a new hire in the sales department in Salesforce. Depending on what permissions the hire needs, uh, if there's a profile, uh, if there's this particular profile with minimal, uh, permissions that can be assigned, uh, to that person till, uh, he becomes acquainted to, uh, what permission is required. Uh, otherwise, there's a standard read only, uh, profile available in Salesforce. We can assign that. And, uh, for time being, we can add, uh, the little permissions that he requires, he or she requires from, uh, using permission sets. We can, uh, add it on the top of profiles. And, yeah, I mean, profile is the first, uh, point and permission sets after that. Yep.

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

Uh, reporting. Need. Okay. Reporting need. Okay. Reporting. Uh, okay. Uh, I have created reports in the past. Uh, I can't think of any particular complex reporting need. I'll be able to figure it out once I, uh, know the use case, but, yeah, I don't I can't think of any scenario where it was complex, and I needed to manage it. Okay. Salesforce tool. Uh, tools will include reports object. What other tools? Data if, uh, if data is needed to be uploaded in that, uh, in org data loader or workbench can be used to insert or observe data. FLS, uh, if it didn't meeting it. Yeah. I'll be able to figure it out more if, uh, I know what the use case was, but I can't think of a particular scenario as of now. Okay. Thank you.

Governance standards do you enforce? How do you maintain different users' data quality? Okay. What governance standards do you enforce on Salesforce? How do we maintain different users' data quality? Okay. So to maintain users' data quality, restricting access to the objects that that are not required by the user can be done. Um, role management, uh, assignment of roles, uh, in terms of what records, uh, the user should not be able to access, uh, is done. Uh, there's a feature in Salesforce uh, similar to list views, uh, which which is called scoping rules, which basically, uh, uh, which basically controls what, uh, records the user is able to see. So for example, there are 3 teams in a particular, uh, org. So and the teams for the users are, uh, changed every day. For example, team a, team b, team c. Uh, 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, uh, records that belong to team b on that particular day. Does not restrict access, but, uh, that can be controlled using scoping rules. Uh, and users will still be able to, uh, search their records from global search. But, uh, yeah, data quality can be controlled using sharing rules. There are restriction rules as well. I have not worked on that. Uh, and list views is something that can be used to control data quality. Uh, we can provide access to the users, uh, based on the data they require, create list views, and, uh, assign the access only to the concerned, uh, users. Yeah. Governance standards. Okay. I

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

Salesforce is a third party application that lacks need of support for Salesforce APIs. Under integration, 6 for the 3rd party applications. I do not have much experience with integration, so I am not really aware about 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. Okay. Strategies would you implement to handle cascading updates and deletions? Okay. So cascading delete is, uh, delete works where there is a master detail relationship. If a master, uh, record is deleted, uh, the lookup data along with is also deleted. Implement to handle task reading updates. Result rate and 80. Okay. Uh, I think this can be handled using, uh, assigning correct permissions to the users, uh, where they are not allowed to make updates to the fields or objects they are, uh, they don't require or they should not have access to. Checking, uh, relationships, uh, among objects, master detail, and lookup relationships, uh, uh, where it is not required should be removed. Yeah. It's getting updates. Going through flows, uh, triggers flows, uh, and trigger flows, workflows, uh, on a particular object, what it is doing, what it is not, that needs to be, uh, checked that, uh, if changing 1, uh, for example, update on 1 object should not be affecting, uh, update on another object. So that's needs to be taken care of. Should be, uh, that should be able, uh, that should be possible through controlling access to the users, mainly. Security, uh, access measures. Yeah. Record level, um, and fee level. Aug level. Yeah. Cascading updates and deletions. Yeah. Uh, users who do not require delete access should not have them. In my, uh, org, the end users never had delete access. Only system administrators, uh, had delete access and integration users. So not being able to delete a record, uh, was, uh, is 1 of the things. Okay. I think that is all I have.

Salesforce formula fields for large volume of or a large volume of record without impacting the system performance. Okay. Salesforce formula fields. Okay. For a large volume of records without impacting system performance. So it shows form of the fields. Okay. My volume of records without impacting the system performance. Fields. Okay. Optimize formula fields. I think optimize formula fields. Okay. Salesforce formula fields, I know. Um, acting system performance. Not adding the field wherever it is not required for, uh, on the layouts, uh, for example. Not all layouts require it. Not all users will require, uh, the calculation of that formula field. Without impacting the system performance. Can't think of anything else. I need to look into optimize I am not entirely sure what the question means to ask. Optimize sales. Uh, Yeah. I'll need to check.

Uh, so I have not directly, uh, worked on case management, but, uh, there was a POC that I worked on, uh, for my for the, uh, clients in insurance for, uh, initial insurance, but then mortgage users. So for example, leads to be assigned to mortgage users. Uh, there was a age old, uh, round robin put in place, the round robin code that was working to assign leads to loan or LOs, loan originators. And, uh, they wanted something that was configurable. So I did a POC on omnichannel, uh, which I used, uh, Yeah. Uh, omnichannel, I, uh, I did a entire logic based on, uh, certain fields, uh, that were required, uh, on the basis of which, uh, it'll assign uh, it to the users. Uh, so Omnisannel is basically used for routing. There are multiple, uh, uh, options available in it. Uh, on the basis of certain criteria, uh, the people that are added to a queue or a group uh, are assigned the records, uh, which based on availability or based on workload, uh, is assigned to them. Uh, a particular record is assigned to them. Yeah. So omnichannel, I think, uh, is something mainly that is used for case management. Uh, and there's also supervisor, uh, a console. Also, 1 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, uh, yeah, there's also a supervisor view in omnichannel, uh, where you can check the for example, I'm the manager, and there are, uh, there is a team of 5 working under me. I, uh, and that that queue I have access to the particular queue where they they they are added. Uh, I can check what, uh, records, what cases they are working on, what status it is in since when it is, uh, it has been assigned to them. So that way, manually also, the manager can, uh, have a view of what, uh, the end users on, uh, end users are on the sorry. What the users are working on, what the employees are working on. Omnisannel is 1 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. Um, there's, uh, there's also, uh, assignment rules, uh, that are present in setup, uh, in readily available in Salesforce, but, uh, that does not allow much flexibility to implement complex logic. Uh, so, uh, after if it is not uh, if it does not work using using case assignment, it can be done using Omnichannel. These are the 2 things I'm aware of. Yeah. Case management. Other things that come along with case that so that's, uh, support processes. Uh, yeah.