Friday, June 30, 2006

Top tips when reviewing and repairing an AppExchange package

Once you have built an AppExchange package you then move on to the "fun" bit of the process.

In the past year Salesforce.com has massively improved the process for registering, reviewing and publishing apps on the AppExchange. I remember the days when this was a completely manual process and believe me, that was hard work.

Even now, I think this stage is the most painful. I think it's partly to do with the fact that, as a supplier, you have now built your perfect package and can't see why it should take any time at all to review and approve packages... the reality is that it's bound to take time and Salesforce.com has to ensure that packages reach a certain quality to be published.

To make this process run as smoothly as possible, here are my top tips:

1. Build your package properly
This may sound rather stupid but the more time you spend building your package, the less time you will spend reviewing and repairing your package to meet Salesforce.com requirements. And believe me, you want to spend less time doing this. Put in the test data, make sure the test drive organisation works properly - you will only have to go back and redo it all if it doesn't work.

2. Use the processes and checklists
One of the areas that has massively improved is the amount of information provided to help you with the publishing process and the automation of the process. I know that many I.T. types never read manuals (that's obviously more true if you are male) but everyone should really read the process guides and marketing guides. They do tell you everything you need to know.

3. Don't be afraid to iterate
No matter how much effort you put in, don't expect to get your package approved first time. Make sure you put some time in to your plan for re-working and iterating through the publishing process a couple of times. Also, take time to get internal reviews because it is much better to make corrections and improvements at this stage of the process rather than after the package is published.

4. Don't be afraid to ask
Finally, if you do get stuck, don't be afraid to ask. Also, if you don't quite agree with some of the recommendations - ask. The AppExchange is new so everyone (even the Salesforce.com staff) is going through a learning process and I have found both the technical and partner teams very open to discuss alternative approaches.

No comments: