I'm creating an app that requires Users to validate a few things in their Org so that the app functions correctly.

Is there a way to include this on the "Success" page after they install the app? It's a very short 3 step list.

  • 1
    "Configure Custom Link" on your package is another worth checking out. In the package description, you could direct the user to the Configure button which links to your README. – bigassforce Apr 24 '13 at 23:22

A couple of communication routes to consider...

  • Default Landing Tab. I've seen a few apps include a Welcome tab and ensure its the default tab on the Application. This ensures the user sees it first when selecting your app from the application drop down. You can read more here about setting one of these up.

  • Welcome Email. You may also want to consider a post install script that sends an email with your read me text in it (and perhaps a link to the welcome page). You can read more about this here.

Configuration Checking: You certainly should make sure your app fails gracefully if this config is needed for it to function. Make sure you choose carefully the location to make this check, since Force.com native apps can be interacted with in various ways, least of which your VF pages. If its really vital you may want to put prechecks into your triggers.

| improve this answer | |
  • Thanks Andrew, I hadn't even thought of the welcome email - that works perfectly for what I need. – McD Apr 25 '13 at 13:51
  • Excellent, happy to have helped! – Andrew Fawcett Apr 25 '13 at 15:10

There isn't a "baked in" way to do this from the install success page, no. That said, there are a few ways you could implement something like this. You could make sure you app doesn't work until some initial config/questions were submitted. Then you would explicitly state in your install instruction that admins must complete the Setup/Settings/whatever VF page that you surface in your custom app on a custom tab. It's hard to say what would be the most accessible not really know what your app is or does. Either way, once you have your tab and VF page, you tie it into a Custom Settings object that is set to visibility of Protected. This doesn't let users muck about in the custom setting directly, protected settings are not visible to end users except through your VF page.

You can then drive all of the functioning of your app off that protected settings record, that would be the way to make sure that the app doesn't function otherwise, if those settings either don't exist, or aren't what you want them to be. Absence of this settings record could also redirect people to your setup page as well. This is one way to do it, and I've made a big assumption that your app is mostly native to SFDC. Hope that helps.

| improve this answer | |
  • Appreciate the info greenstork! I'm trying to keep this app very simple, so I don't know if a VF page is the way to go, but very much appreciate the info! – McD Apr 25 '13 at 13:51

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.