Transcripts
1. Introduction: congratulations on completing Part one off sales Force Change Management Co. Siri's. It truly takes time and commitment and I'm so proud of you. So in part one, we understood about the overall change management and salesforce, how it works, what all the key benefits off a change management and water, all the stages involved and about the various development methodology options as a continuation off that in Part two, we are going to deep dive into salesforce, change management on understand about sandboxes. We will start understanding about that. What's a sandbox? I want all the different types of sandboxes that we have in salesforce on the difference between the sandbox types how to create a sandbox, how to delete the sandbox on basically how to do a sandbox refresh So in this part will understand entirely into end about sandboxes. So at the end of the calls, you can confidently work on sandboxes with no hesitation. And of course, that this is a very essential skill set for a sales force release manager and also for arguments or developers who deployments and salesforce. So that would be about part two. And once you complete this course, please do check out the other parts s will. That is part three and part for about metadata export and meditator deployments. Happy learning.
2. Sandboxes and Sandbox Environment Types: The next topic that we're going to discuss about is the sandboxes and the various type off sandbox environments. So insensible is that there are were widely to type of environments that is a production environment, and the other result test environments are you can call it the developer environments. Or you can also say the sandbox environments. They mean the same production environment has got active users accessing the business critical information. And how would you access to production environment you can use? Log in to access full circle and use Ukraine and choosing that and nexus a sandbox in warm sandbox environment we used strictly for a development and testing. And it just contains only the test data to help you heal her development and testing. And you can use a test dark salesforce dot com and use your sandbox credentials sometimes if you don't have a devil tradition, but that is more off on your personal use and for developing some people sees. But majority the only use sandboxes for our development and testing on the particular organization can have only one production environment. No doubt about that that can we will leave one real time environment with users access with the real time data and there can be multiple sandbox environments depending on their requirements. One sandbox to sandbox 5 10 15 to any. The number of sandboxes actually depends on the business. And these sandboxes fall into one off these categories. When we say there are some 10 sandboxes say, for example, these 10 sandboxes can be one. Among these category can be full sandbox. It can be partial copy sandbox. It can be developer pro sandbox. It can be devil a percent box. It can fall into anyone off this type. And first comes to develop a sandbox. This is space. And this copies of customization. That is a merry data on the difference between the devil percent box in the develop of pro sandboxes there produces saying other than the day of stories limits it is only 200 MB data Maxim and this is one GB data maximum on the partial copy sandbox. It copies a meta data. Yes, Along with that. It also has a sample off your production organizations data and the data storage capacity is five g B on the full sandbox. That is the exact replica off. What you have in your production, be the metadata, be the data. It is a kind of exact copy of words there in the production. And that's why it's called us full sandbox and definitely is datable by the prices. The developer sandboxes the lowest and the full sandboxes the highest. So all the sandboxes in your Argh will fall into one off these four environment types. And it is totally up to the business up to their requirements upto their development and testing to determine how many sandboxes they need for what purpose and who basically uses those sandboxes. Onda, how did we basically lock into these sandboxes in production? We know this is just an example. John Smith at whichever company that you belongs to our domain. You can say dot com on in the staging, it would be like the user name dot staging and Cuba. It would be appended with dark you way and in depth sandbox. It would be appended with dog dead engine. The user name would be the same as it isn't truck, except that it would be appended with a sandbox name and as an admin, even developer, if there is no defined admin in your project. This is definitely one off the initial task that you got to do when you join a new project . You got to have an understanding off the various sandboxes in your ark and why it is being used for But in the developing tradition, we do not have any concept of sandboxes. So pretty much we'll all be able to see anything over here. Like sandboxes. It returns nothing but an ideally in a real time environment means in a real time production environment. If you go and search for sandboxes, you'll be able to see that option under data management. So instead, wanted me, Louis Litt official. Your screen shirt off that so that you can visualize it better. Real a screenshot from one off the production environments just to help you understand the concept later, as it is live data and the information is very critical. I have overdone all the information with just some test sample later. So in your life production environment, when you go search for data management are sandboxes, you will be able to see an option under data management called sandboxes go forward, and that will list on all the sandboxes that are associated in your ark. And as you can see here, this gives the order information out off the four environment type sandbox environment types that we have. You know, there are 16 that belongs to developer sandbox, and there are zero for developer pro and zero for partial copy. And there is one full sandbox that is available and pretty much everything is the news, and they do not have any extra moments. And under that, you can see three taps when the sandboxes, the other is a sandbox. Templates on the other is a sandbox History. When you go to the sandbox of step, it gives you information off the various sandboxes. Then they were basically last refreshed. Say, for example, this death sandbox on it is off the type developer and the state is computer and the location. I've just given some random numbers like CS 10 2030. And what is the are Guidi and even like I've put up some information for this I'm completed on. So the last to refresh that happened in death is this particular date and what is the description? And this is pretty much given at the time of creation. When you create a sandbox, you know, you just give a description saying like What's the purpose off that sandbars? And who will be primarily accessing that sandbox so as an admin, if a question comes to you asking like when the previous refreshment, the last refreshed for a particular environment, was done, you can pretty much go to this information. Gore sandboxes go sandboxes are even the sandbox history and check like when the last of fresh happen for that particular sandbox. I have just given some sample later. There are only like a fire records out here, but then, as it's a 16 ideally like introduced list of all the 16 sandboxes that have there in your arm and the next step a sandbox templates. Sandbox templates are basically used for partial copy sandboxes on full copy sandboxes then and then you do a refresh. You can use these templates to design on which object data you will a copy on which portion off data that you basically were. Copy. However, it is not mandatory. It was optional that you can have sandbox templates. The third tab out here is a sandbox history. So in sandbox history. Once you click on that, you can access the whole history off the refresh father various and boxes in your arm, which sandboxes requested. And it was requested by which person and no, it was activated by which person. And then the refresh basically happened on vented, finished. And then it was activated. The entire history of information you can access in the tap sandbox history. So pretty much of this information is sufficient for you to understand the various sandboxes off what sandbox environment types they belong toe and in which frequency the refresh happens in those sandboxes. So this is all about sandboxes and the various sandbox environment types on in the next section will be understanding, like how we do a sandbox and a fresh and at what intervals can be repeated at refresh for a particular sandbox and all those information
3. Create a Sandbox: you never previous radio, we understood about what the sandbox and what role the different sandbox environment types in Salesforce. Perfect. So now let's understand, How do we create a sandbox and says Force? Basically, in real time organizations, they have a production environment which they roll it out to users Roundup offered. They also purchase sandboxes for all their development and testing Onda based on the company based on their requirements, the number of sandboxes and their type of sandboxes have differ from company to company. And in this video what We're going to learn this whenever a company for chases a sandbox license, how do we consume that license? And how do we create a sandbox in Salesforce? So that is what we're going to learn. And, as you know, that the addition that we're using for all of our learning purposes a developer edition. So this is the addition that we're using on in developer tradition, we do not have access to any off the sandboxes. So in set up, if you say sandbox, you obviously get no vessels because in developed tradition, we do not have access to sandboxes. We can't configure any, However, in real time in a real time production environment. Yes, When you go to your production environment, when you say when you search for sandboxes, then yes, you would get results on the nuclear concerned boxes. Basically give you an idea about water, all the sandboxes that is available. But as I can show you here for the purpose off are learning what have done as I have taken some screen shorts from a real time production environment. And I'm showing you the screen shorts for us to get a better understanding off the concepts . So, in the real time environment, when you search for sandboxes, you will get 2000. When you hit sandboxes, basically are you'll get a screen similar to this. It will list down. All the sandboxes that are available with your production are basically all the sandbox is that you're always using this arc I have chosen. It is a pretty fresh production, or it has basically no sandboxes. Conficker Onda. Here you can see the available sandboxes licenses that is purchased for this. Argh! They have a developer sandbox. There is only one license available on develop a pro. Partial copy. Full copy. They have no licenses purchased. So basically they have only one license for a devil percent box. And now that they have purchased this license, we have to create a sandbox and configure that in our production environment. So this would be the basically the page that you pop whenever you hit sandboxes in your set up in your production arc in your riel time production are so you can see they have a developer sandbox license available. But you know otherwise. Like you, you you may see like a to e news zero available, meaning they purchased to develop a pro and they consume the border sandboxes. And here it may say, like one A news and one available each means they have one partial copy sandbox, which is already in use. And if it says one available, it means they have a license for a partial copy sandbox and it is it to be consumed. So basically, this gives an idea about the total number off licences on how many licenses are already consumed by the Ark. And here you can see they have absolutely no licenses for all these. The only one license that is available is for their developer sandbox. We know what the devil. A percent box. We already discussed that in detail before. Now let's understand. How do we consume this devil? A percent box license. So here you can see two tabs, sandboxes and sandbox history. Sandboxes means it'll list don't work for all the different type of sandboxes they have a particular art has. And what's the type off sandbox and what's the state is basically like, if it is active or if it is being refreshed and everything and what's the are gaity and all the details off? All the sandboxes appeared out here and we also have another tab which say's sandbox history. So Sandbrook history. Basically, this is the tab that gives you the history off information off sandboxes. So what? All the sandboxes that were available? Who activated that, then? It was a refreshed when it got completed on all the details. Basically what all the actions that were happened in the sandbox. All those will appear in sandbox history, so you can see two tabs out here. Sandboxes gives all the details. History gives off the history details. So now let's go to the sandbox. A stab and we have a button. New sandbox, Martin. And once you click on new sandbox button, this green pops up. So what does this page all about? It ask you for a name, basically the sandbox name under description. So it is always a good practice to give up meaningful description so that others will also know what is the purpose off the sandbox. Say, for example, a people in organizations. We may create a separate sandboxes for separate projects. It might be an upcoming major project, and they might use a sandbox completely for one project, so they might name it accordingly. Or it might be a regular Cuba environment or a regular you 80 environment. So it depends on the organization for what purpose? They are creating that sandbox. So give a name for the sandbox under description. And here it also gives some additional information to us like words. The devil percent box to develop a pro partial copy. Full copy. On Dhere, you can see that we have only one license available, and that is only further developer sandbox. So that doesn't They were able to see this create button only here on we are not able to see that create Burton out here. But if your organization has got licences for more than one sandbox, you'll you'll be able to see the create burdens all along. And you have to choose basically which sandbox license you're going to consume. And here we have only this and this is only option that is left to us. So we have to hit the create button. So when you hit the create button automatically a sandbox off the type developer, basically a developer sandbox gets created. And here I have filled in the details. Once you fill in the details, should the create barker and then this is what you would be seeing. So basically you have no created up sandbox using their developer license that we have on, we can see that it is off the name death. It is a devil, a percent box on the state as a spending. Basically, whenever you create a sandbox, the system takes time to create a sandbox, and it is in Cuba. Onda as a sandbox is still not creator. The are gaiety is still not assigned, so that is also showing us pending. So basically the whole process is in progress. it is still not completed. Their developer sandbox that we created is still under progress. And then depending upon the configuration and everything, it takes some time for creating the sandbox. Once a sandbox is successfully completed, you can see the devil a percent box. The status gets changed to complete it. And you also get this are guiding. I have actually like giving a false on daily here. We also get the already and we also get the completed data in time on other description whatever we gave while creating the sandbox. So this shows that we have successfully creator a sandbox. We have completed the process. And as we mentioned before, we also have a tap called a sandbox history. Right. So now, after creating a sandbox, if you go to the sandbox history, you should be able to see this information. So it is a death sandbox, and it was requested by the salon. So person on it was created basically, by that is what it's saying refreshed. And then it was finished at this time and it was activated, probably like, you know, activation and the refreshing. It all shows the same time because the sandbox just got created. So this is about the sandbox history tab. So let's go back to the sandbox of stab on here. If you click on death basically the death sandbox, it would list down all the details out here. So what's the sandbox name, The description, the license and what's the status? The location, The are gaiety and by whom it was created so it would display all the leaders out here. And we know that a developer sandbox, it can be refreshed every single day it's and we just created that. So it says one day, reminding off one day. So basically, after 24 hours will be ableto refresh this sandbox and you can click on log in button too long into the sandbox. You also get an email notification when the sandbox gets created. So basically, the logging user name and the password would be the production user name appended by dot the e V, or whatever the sandbox name is on that the password will be the same as in the production credit shifts. And this is how we create a sand box and salesforce
4. Establishing a Deployment Connection: So now that we have created a sandbox successfully, the next step is to establish a sandbox connection, basically a deployment connection. So the sand looks that we created. It is very much a news. Users are able to log into the sandbox successfully, and they are able to do their development and testing, and they completely they can use this hand box. But at one point when we need to migrate the competence when we need to deploy the competence from that sandbox to a different environment, beat another son, books or be the production environment the feature. But environmental this the number that is need for this deployment off meta data. Then we need to have a deployment connection in place only when Tuaregs have a deployment connection in between them. Only then we can use chain sets our I D or C L A or whatever competence so deploying. Also, establishing a deployment connection is essential for deploying metadata competence between two are so now. Let's understand, how do we create a deployment connection between two are on the hero Throughout the learning purpose. We are using developer tradition, and we do not have access to sandboxes so a similar to the previous assignment. Even here I have some screen shorts which we can use it for our learning purpose. So bomb log into the sandbox, for which we need to establish a deployment connection, log into the particular sandbox on in set up. If you search for deployment settings, you will be able to find deployment settings on the page would appear similar to this. So here we have deployment settings here and here we have listed of the production. Argh! Because there was only one are other are that is available. But in real time, if there are more dogs, the production all will be there and on top off it. If the company has got more than one sandboxes, all the sandbox is will be listed here on that Here it will show us what is that Basically connection between that particular environment on the other environment. Here we can see that there is a nor deployment connection between the death sandbox that were logged into on the production sandbox. So right now, that is a nor deployment connection between these two arcs already between the death sandbox under production arc. So now what we're going to do is we are going to establish a connection. So here we have the production are click on the production OG. This will give us other details. However it does define and then we have allow in bone changes on except our bone changes. So what does this inbound and outbound as the name say's inbound means incoming and outbound means outgoing. So only then this boxes check that is in bone changes. It means that it can accept changes from production. Og look, it cannot give out its changes to production arc. Basically, it can only accept the changes, but there is no outgoing and depending upon the requirement for depending upon how the um Ahmad has to be configured, it completely depends whether you have to select both or either one off them in the scenario have selected board, and once you do that, you can see it is to wait. Changes from death can be deployed to production on changes from production can be deployed toe death because we have selected both inbound hand along on now, we have successfully established a deployment connection between Denver and production. Similarly, you can see all the other sandboxes listed out here, And you can also see how was the deployment connection established between their death sandbox and the other sandbox. Say, for example, we have a sandbox que way so here you don't say death to weigh and what is their relation? If there is no relation to Children, read. If it is one way, you don't show one way, and if it both ways, it shows like this. So this is how we establish a deployment connection between two environments, insists Force on. After those deployment connection is established, we can use chains. It's a post or comedy toe deploy over meta data.
5. Delete a Sandbox: Now that we know how to create a sandbox aunt, how to establish a deployment connection between two arms and salesforce? We should also get to know how toe Adelita, sandbox as well and salesforce, right, Because there may be requirements wherein we may want to a delete a sandbox which we used for a particular project and we no longer need that. So we may want to delete the sandbox. So how do we do that in Salesforce again for deleting sandboxes we do not have access to sandbox is because we have only developer tradition. So I have some screen prints with me which will help us learn the concept in a real time production environment. Go for sandboxes that will list on all the sandboxes that are available on being confidential information. I have just basically blowed out most of the information out here and you can see the devil percent boxes How many are available and how many were news? We can see there is a full sandbox. Basically they have only one license which is already consumed on. They have no more licenses available and the most they have is developer sent boxes. They have a developer sent boxes on. Among that, all the eight are available, and here we see all the eight developer sandboxes are consumed. And if we decide to delete a sandbox, then what should we do here we see all the sandbox environments it's listed out, and you also have options to log in the refresh or delete. So go to that particular sandbox. In other case, let's say that sandbox go to the particular sandbox on hit delete as simple as that on. Then we get a warning message saying that we're about to delete a sandbox, and then the operation cannot be on then. So if we are very sure about deleting the sandbox, check the check box on hit, delete and that's it. The sandbox gets deleted once the process is completed. On Daz. The warning Miss. It says this process cannot be undone. So be sure about deleting a sandbox before we actually go ahead and delete one. So this is the process off. Deleting a sand box and salesforce
6. Sandbox Refresh: now that we have invested about a sandbox is the veda sandbox environment types. The next topic that we're going to discuss about his sandbox refresh, Say, for example, there are these many sandboxes in your arm and you want to refresh one off the sandbox. So what is all that we got to consider to make it happen? Let's say we go to war with Russia. Cuba Sandbox that. How do we take it forward before we go ahead and perform the refresh? There is one important thing that we gotta have in mind and that is a refresh interval. If the sandboxes off type developer, then you can't refresh it every day because the interval is one day, you can refresh the developer sandbox every day and saying that the developer pro sandbox as well you can't refresh it every day. But in case of a partial copy sandbox, you can refresh it only once in five days on. In case off a full sandbox, you can refresh it only once in 29 days. So be mindful about the intervals so that you can plan your refresh schedule accordingly on the capacity information. We are privileged aware off for the developer. It's 200 MB. The capacity for definable pros. One GB for passion Copy. It's five GB on for a full sandbox. It is a very same as your production instance, and in the refresh be to developer, sandbox of a fresh or a developer, pro sandbox of a fresh it influence the configuration, Apex and marina and all user information just that the capacity to force in the data storage capacity in the force between developer and develop a crew. But in case you are refreshing a partial copy sandbox, then like it includes the apex. It picks and metadata all user information configuration on some sample records. And you can also use sandbox templates for this partial copy sandbox. And finally, the full sandbox for the soulful sandbox. Again, the configuration epics and Maria and all use and information are there along with that, the interstate off records, whatever is there in the production, so you can sell it all of the objects. Andi, if really required, you can select some off the objects and you can definitely have the support off sandbox templates. You can you sandbox templates where anyone to select, which all are back. More objects you want basically refresh on Bill. You can also have the history and the Charlie information. If you want the field tracking history on the charter information to be refreshed asked me then you can very much do it on a full sandbox. So these are some off the important information and differences that you gotta have in mind before you start any refresh. And just for instance, let's consider we are going to refresh the Cuba sandbox and as a chills here, it's a devil. A percent box. So what are all the ladies activities that we're going to do for the Cuba sandbox? Refresh. First, we got exactly understand what this Cuba sandbox refresh mean, what it does overall. So when you refresh the Q a sandbox, the interior Cuba sandbox metadata will be completely refreshed with a production margarita . So whatever you haven't prod will completely come and sit down. Cuba. Sandbox means you're objects. Feel stabs, applications, visual force pages, apex clauses, everything. Absolutely everything from production will be copied into Cuba sandbox, meaning you use whatever you have in Cuba prior to the refresh and after the refresh, it will be only the production Maria that you can see in Cuba and this Q way being a devil percent books, no data will be copied from production. So all your best days lie in Cuba will be removed on the user. Information in Cuba will be overturned by as it isn't right. So all the users who are there in production will be there Cuba as well. But there's no doubt regarding the user. Information is actually a little different from business to business. In some business, it is like the same set off users. They exist across all the environments. But in some projects it is like some people have access only to the lower environments, and they do not have access to production because they were calling the development and the migration is completely taken over by someone else. So they have access only to say Devinsky way, and they do not have access to staging and prod pretty much even that it's possible. So you gotta handle the scenario accordingly. So, in short, Cuba sandbox with a fresh will completely razeq you Maria on will replace it with a production copy off that and no test data will be present. Okay, Perfect. So as an admin before starting the refresh, there are some activities that you go to do task one. Send out a communication to the development team with the date and time off the refresh so that basically they can back up all the dead work. Say, for example, in a team there is only one single team that is working on an application pretty much the deaf team. All of them will be on the same page there in the best date will forever doing the refresh will be the day after the deployment. So after the deployment, pretty much you can do a refresh so that you can copy the production instance to the lawyer environments. But in scenarios were in, multiple teams work on the same application. Well, say, for example, they work on different applications, which connects to salesforce. So in that scenario, the death teams might have different time slots for the express. So it is very much possible that when one team goes life, the other team they are doing with their development where the other team goes life pretty much the third team is actually working on the deployment. So in those scenarios you have toe will coordinate among the teams, find the best a suitable date for performing the refresh and send out a communication to the entire team so that if anyone has got some work done in that environment, they can pretty much back up their work so that they do not include any work loss. Also, this Cuba, a sandbox being a devil percent box, remind the team that their test day I will be lost. So in case they are very specific about their test data for any off their developments are testing. Then they go back the past well. So after that refreshes done, they can reload their test data. And you can very much send a reminder emails, maybe the previous day just to ensure that no one's workers lost. So once is communication and everything is jump done just prior to the refresh. You go to take a complete meditator export, and we discussed How do we basically take a meditator export in the previous session's so use force dot com cli? And that is the fastest way off exporting metadata on half that for reference because many times where people come to you asking for the back of files, They say, Ah, they missed out. Oh, basically, take a backup off class that they were working on a trigger that they were working on. They lost some information. So having this mirror export taking a back up off that is definitely recommended. And also do take a list off users who were using Cuba into in the scenario for any reference later. So these are all the activities that you got to do prior to the refresh once done long into the Salesforce application and started a fresh even for this lecture as I won't be able to use the developer edition on basically using some screenshots to explain the concept. So in the production instance, go data management sandboxes that will list of all the sandboxes that is there in your arc , you can see three options Delete, refresh, log in hit refresh so that you can have refresh the corresponding sandbox. Once you hit Refresh, You got to give in the name on the description off the new copy of the sandbox. And as you can see here, it will list on all the different type of sandbox environments on, then was it a fresh interval? And the other information on that this Cuba sandbox is basically a developer sandbox, so you can see the next option only out here, So go next. So once you click on next, now you can see that I am no templates for this organization because it is basically a developer sandbox, and then it is asking an option for auto activate. So here we go. To understand, what does this option off or deactivate? Actually, sandbox refresh happens in two steps. First step copying the Medicare from production and step to us activating the Cuba sandbox with them. Production metadata. If you do not check auto activate. Once the production metadata is copied, it waits for your confirmation on activating it to the Q A sandbox. And if auto activators check it copies the production moderator and automatically activates Thank you a sandbox. It doesn't wait for your confirmation. So in this instance, let's assume what do you do not auto Activate. So do not check the check box and hit create. Once you do that automatically, the sandbox stated that it will be bending in Cuba and as you can see here at this point of time, and the state is burning in. Q. You do not have neither off the options. Delete a refresher log in and when the processing starts, when the refresh processing starts, it stays. Processing on the time it takes for processing depends on the type of sandbox and also the type of meta data. So you didn't basically stay on the space. You can continue with your other activities on. Once a processing is complete, Salesforce would send an email saying that the processing it's complete on as we have not order activator it will let you know that the activation is spending from your side on the email would look something like this. Then it stays. The refresh is complete on it just actually completed. It is ready for activation. So what to activate their a fresh copy. Basically, it gives you the link off the production account. Then we'll have the activate link. So once you click on to activate link, it will get activated on in cases that are any discrepancy in the user information, and if it is not able to update the user information, it will this down all that user information as well. And now if you check the sandbox status, it will show pending activation, meaning that refreshes done. But then it is still not activated. So in this time, the Cuba will be ordinarily how the Cuba is before the refresh. There is no change. Only after you activate the production meditate. I would be copied into Cuba. But at this point of time, you have two options. Activate out of this card you've activated than the human sandbox would be activated with waters there in production on discard, all the changes will be discarded. And once you activate, it will ask for a confirmation that in just check and hit, activate again. The sandbox stages would no be activating. And now, like again like you will be getting an email from Salesforce saying that the Q A refresh is ready for use, meaning it is completely activated and it is ready for use meaning now that the Cuba sandbox is refreshed with waters there in production and again, some information on how it has to be accessed off as it is Cuba. And as it is a sandbox, you can access using the yuan test dark cell phones dot com. It just gives you an instance. Say, for example, your production accomplice. This then you can access your Cuban with this user means it is pretty much appended with the sandbox name on. If, in case like there are some users which is not able to sync by the system, then it lists all the users, and that's an AGM. Unlike you, gotta cross verify if they are really invalid users. And now, if you again long into the application and see the refresh is complete. So that's the reason it is showing the state of this completed on The refresh is complete. And here, if you see the options, you do not have the lead on refresh. Why? Because this is a developer type sandbox and it can be refreshed only once a day. So it means the refresh option will again appear after 24 hours, and in case of it being a full sandbox, the refresh option. You'll get it only again after 29 days. So once the Cuba sandbox and fresh is done is completed. There are some activities that you got to do a full set of fresh So what is all that you got to do? So this is all that you go through? Posted a fresh first is reactivating the users in Cuba if need reactivate users in Cuba if needed. Meaning If the users in Cuba are not in sync prior to the refresh and posted a fresh, then you got to reactivate those air. Those users and some scenarios might be it might not be across all business, but in some business there are pretty much chances that users will not be there and fraud. But they will be there and eventuate in those scenarios, very likely that you might use those users. So what you can do is you can take a list of all the user list prior to the refresh and then basically do a comparison and then recreate them after the refresh and reinstalling absent packages. Even this again, that is, are dependent again that it's project different. You're in some projects. Um, what they do is all these up exchange APS that you installed pretty much they do not install everything in production. Some off the apse might before some trial and error office, um, testing the instant only in the lower environments. So in those scenarios, you know, as it is not then in Prada, it is very much likely that you lose. Those absent Cuba are dead or in the lower environments. So you gotta have a check off all those apse which is there in Prague. So I'm just not there and for and which is there in similar environments. And if yes, then you got to reinstall those APS on once we're done with these two activities, then send out a communication to the entire team, letting them know that the refreshes complete on when you sent out that email do remain the team on the following that in which you are all they need to use for accessing the Q A r. Which of our sandbox? I also do remain them on the user name and the password. The user name will be the same as it was for product, except they got upended with a sandbox name. And Cuba in this instance on the password is the same as for protection. So what other password? They have a production that will work for Cuba going forward after the refresh ondas for the secondary tokens. They have to regenerate the security tokens on, in case they are using the secretary tokens basically hardcore in the secondary tokens in anyone off their schedule, the jobs. Then they have to update those jobs accordingly and also some support to any users in case they have any issues and logging. And so these are all the activities that you go to the post refresh. And in case you are refreshing, a full copy sandbar. This is one additional step in the process, you know, Then you hit Refresh. It will take you to a page wherein it will ask you for the name and the description off the sandbox on when you hit next, it will basically show up the screen. So what does this? It will ask you whether to include all the object data. Or maybe you can use some templates where you can create some sandbox templates which tells you, like which all objects and which all data that you basically want toe but a fresh. And it also gives you options there. And you want to include the field tracking history data from production toe which of a lower environment and include the Channel data and also this option or activate. So this is kind of an additional step Venuto a full copy sandbox of a fresh
Archana Rajendran, Salesforce Consultant
