Skip to main content

Hello everyone,

 

This is my first post to anything Salesforce-related even though I've been an "Admin," for about 2 years now. I still consider myself very green. I will be on the Admin presentation later today, but here's the burning question I have at this point.

 

We use Salesforce in conjunction with a third-party vendor (Enrollment RX) to provide our application for admission. EVERY. TIME. Salesforce puts in new anything (generally security updates), the user profile permissions gets screwed up in a way that disallows our applicants from being able to do anything after they register for our portal. Whenever this happens, I have to contact the vendor who magically fixes the permissions, but my question is WHY does this need to change every time something new comes down the pike? It happens in our staging environment first, as well. It's so frustrating because it makes us dead in the water until the vendor can investigate and resolve the new security changes.

 

And yes, the vendor does have documentation on what to do to prepare for these changes, but we have such a unique instance of Salesforce, coupled with my inexperience of the "into-the-weeds," details about Salesforce in general, that the instructions largely make little sense to me. 

 

But the question remains: WHY do these changes happen EVERY release?! It's rather frustrating to keep up.

 

I know I'm asking a rather loaded question, and the answer probably is, "Depends," or something similar, but if there's a boiled-down answer, I would take that.

 

Thanks for "hearing" me out; I appreciate all you guys do and I'm trying to learn more so I don't need to ask questions like this in the future.

 

Christi Noyes

Pima Community College

Tucson, AZ

1 条评论
  1. 2021年1月29日 15:35

    Not a loaded question. It's because Salesforce is really locking down and double downing on Security, specifically when it comes to Guest Profiles, that's all.

    Salesforce does give a lot of warning when changes like this occur. First in the release notes, and preview sandboxes, before changes are made. These are also usually classified as Critical Updates as well, so you can turn them on in a sandbox before they auto activate to test for any adverse reactions.

    If you keep up with critical updates, and test them in a Sandbox environment before they are auto activated, it should minimize any downtimes.

0/9000