0

We have developed a solution that we want to distribute as ISV on AppExchange.

What happens if we have people install those packages while they are in review? Do customers need to reinstall our package? can they upgrade from non-reviewed to reviewed version?

What happens if we make changes and publish new versions while the initial submission is in review? Do we need to resubmit again (i know ONCE reviewed you do not have to, but we're a bit unclear on this 'updates while in review' case)

I asked the same on the Security Review community, but wanted to hear some real-life experiences from people who've gone through this mess before.

2

What happens if we have people install those packages while they are in review? =Do customers need to reinstall our package?

No, the package will work without being reviewed, although the package will count towards org setup limits (e.g. number of custom fields per object, etc) until the review completes. There is no need to reinstall the package after review.

can they upgrade from non-reviewed to reviewed version?

Yes. A managed package is a managed package, regardless of it is reviewed or not. There is no functional difference between these two, except as before, "Aloha Apps" do not count towards org setup limits.

What happens if we make changes and publish new versions while the initial submission is in review? Do we need to resubmit again (i know ONCE reviewed you do not have to, but we're a bit unclear on this 'updates while in review' case)

You'll need to ask about current policy. Last I checked (~2014), uploading a new version resulted in an automatic failure of the review and you had to start over (not including any fees already paid). In other words, you should probably wait until your review is complete.

Unless you have a critical must-fix problem, you can probably afford to wait until your review is complete. We had a mishap where we did upload a new version, and we had to do our review twice. Salesforce will only review the latest version, so you can't provide a "moving target" for them to review. It would be better to wait until the review concludes (even if it is a fail or conditional-pass) than to have to start over from the beginning.

| improve this answer | |
  • The only thing i found that is, indeed, different, is that when it is a managed package from a non-partner org you can't publish Apex to Professional or Group; but you can if it is reviewed? salesforcenapex.wordpress.com/2013/03/24/… – zaitsman Sep 6 '19 at 4:24
  • @zaitsman DE (Developer Edition) vs PDE (Partner DE) is number of licenses and storage space, but are otherwise identical. Apex only runs in lower Editions after a successful review, and requires additional testing in both a Professional Edition (PE) PDE and Enterprise Edition (EE) PDE to make sure it runs in both environments. The Reviewed flag is what allows org limits bypass and Apex code execution. – sfdcfox Sep 6 '19 at 4:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.