Isvforce Workbook: Winter '12
Isvforce Workbook: Winter '12
Isvforce Workbook: Winter '12
ISVforce Workbook
names and marks. Other marks appearing herein may be trademarks of their respective owners.
Table of Contents
Table of Contents
ISVforce Workbook.............................................................................................................................2 Tutorial #1: Develop an App.................................................................................................................3
Step 1: Sign up for Developer Edition......................................................................................................................................3 Step 2: Create an App...............................................................................................................................................................4 Development Summary.............................................................................................................................................................5
ISVforce Workbook
ISVforce Workbook
The ISVforce workbook is a quick introduction to developing and distributing apps on the Force.com platform. The workbook takes you through the process of signing up for orgs, developing a simple application, and packaging it for distribution. You'll then install and test a beta version of the app, and finally you'll create a released version of your app, so that anyone can install it in their Salesforce organization. Note: This workbook streamlines the ISVforce lifecycle so that you can complete it in an hour or two. Therefore, some real-life steps are missing, such as signing up for the Salesforce Partner Program, licensing your app, and additional options such as creating a free trial. However, the basic application lifecycle remains the same. When you've completed this workbook and ready to create your killer app, see the Quick Start in the ISVforce Guide, which takes you through the full process.
Supported Browsers
Browser Windows Internet Explorer versions 6, 7, 8, and 9 Comments Salesforce.com strongly recommends using Internet Explorer version 9 over versions 6, 7, and 8. Apply all Microsoft hotfixes. Internet Explorer 6 is not supported for certain features. Internet Explorer 7 is not supported for Siteforce. For configuration recommendations, see Configuring Internet Explorer in the Salesforce online help. Salesforce.com recommends using Firefox for best performance. For configuration recommendations, see Configuring Firefox in the Salesforce online help. Google Chrome applies updates automatically. Salesforce.com makes every effort to test and support the current version of Google Chrome. There are no configuration recommendations for Chrome. Chrome is not supported for the Console tab or the Service Cloud console. Supported plug-in for Internet Explorer 6 only. For configuration recommendations, see Installing Google Chrome Frame for Internet Explorer in the Salesforce online help. Chrome Frame plug-in is not supported for the Service Cloud console or Forecasts. Supported on Windows XP and Mac OS X version 10.4 and later. There are no configuration recommendations for Safari. Safari is not supported for the Salesforce CRM Call Center CTI Toolkit or the Service Cloud console.
Tell Me More....
At the end of each step, there is an optional Tell Me More section. If you like to do things quickly, move on to the next step. However, if you're a smell-the-roses type, there's a lot of useful information here. For an introduction to developing on Force.com, see http://developer.force.com/workbook. To learn more about Force.com and to access a rich set of resources, visit Developer Force at http://developer.force.com.
Tell Me More....
When you sign up for a DE org, you also become part of the Force.com community, which includes forums, webinars, and other exclusive content. http://developer.force.com
5. Click Save to finish creating your new object. To display information about the Merchandise object, you associate the object with a tab. 1. 2. 3. 4. 5. 6. In the sidebar Setup area, click Create > Tabs. Select Custom app and click Next. In the Custom Objects Tabs related list, click New to launch the New Custom Tab wizard. From the Object drop-down list, select Merchandise. For the Tab Style, click the lookup icon and choose an icon. Accept the remaining defaults, and click Next, Next, and then Save.
As soon as you create the tab, you can see it at the top of the screen.
Next create an app that contains the tab. 1. Within the Setup area, click Create > Apps.
2. 3. 4. 5.
Click New to launch the New Custom App wizard. For the App Label and App Name enter Warehouse. Click Next and Next again. In the Available Tabs list, locate the Merchandise tab and click Add to add it to the list of selected tabs.
6. 7. 8. 9.
Leave the Default Landing Tab set to the Home tab, and click Next. Select the Visible checkbox to make the application available to all user profiles. Click Save to create the Warehouse application. The app now appears in the Force.com app menu in the upper right corner of the page. Click it.
Tell Me More....
If it seems like you just created an object within a container, within another container... you did. And you're about to put all of that into another container! What's with all these containers and what do they do? A tab is a container for things you want to display on the same page, such as a chart, a table, or the Merchandise object you created. An app is a container for tabs that appear next to each other. Currently your app has only two tabs, Home and Merchandise, but it could have many more. A package is a container for components. Usually a package contains an app that can be installed in an org. You haven't created a package yet, you'll do that in the next tutorial.
Development Summary
In this tutorial you signed up for two Developer Edition (DE) organizations, a dev org and a test org. You used your dev org to create a simple Warehouse app that contains a Merchandise tab. The Merchandise tab displays information about the Merchandise custom object.
Tell Me More....
The Components tab displays the components in your package. When you clicked Add to Package for your app, did you notice that your Merchandise object and tab were automatically added? Other dependent files, such as the page layout are also added. The framework automatically detects dependent components and adds then to the package.
2. In the Developer Settings list, click Edit and on the following page click Continue. 3. In the Namespace Prefix field, enter a 1-15 character alphanumeric ID and then click Check Availability. Repeat this step until you have a unique namespace. Note: You might be wondering if the characters that make up your namespace are important. Not really. Try a shorthand for your company name or something easy to remember. The only people that see the namespace are developers. 4. In the Package to be managed field choose your Warehouse Components package and then click Review Your Selections. 5. Review the information on the page and then click Save.
Tell Me More....
Within the underlying code, your namespace is prepended to all components that are packaged from your dev org. This allows your package and its contents to be distinguished from those of other developers, and ensures your exclusive control of all packaged components.
Congratulations, you've uploaded an app! Your app isn't available to the general public, but it can be accessed through an install link. You'll install the app in the next step.
Tell Me More....
The purpose of a beta is for testing, and so it can only be installed in a test org, Developer Edition, or sandbox. A sandbox is a replica of your customer's org that allows them to test things before they commit to using them. DE orgs don't have a sandbox, but if you have a sandbox in another org and want to install your app in it, you must replace the initial portion of the Installation URL with http://test.salesforce.com.
Note: If you get a warning that you can't install this package because it was created in this org, you accidentally developed in your test org. It's OK, just remember from now on that your test org is really your dev org and vice versa. 5. 6. 7. 8. 9. Click Next. On the Security Level page, Grant access to all users and click Next. Click Install. Click Deploy Now and then Deploy. Once the installation completes, you can select your app from the app picker in the upper right corner.
Figure 2: Warehouse App 10. Let's test the app and see if it works. Click the Merchandise tab and add then click New to create a new record. 11. In the Merchandise Name field enter Wee Jet and then click Save. Your app installs easily and you can add the name for Merchandise records, your beta test has passed! Next you'll upload a released version of this package.
Tell Me More....
Your app doesn't do much, in fact it only has a single field. The name field is called a standard field because it is included automatically with every custom object you create. You can also create custom fields to further define your object.
Figure 3: Developing Warehouse Components, version 1.0 3. 4. 5. 6. On the Package Detail page, click Upload. Enter a version name. For the Release Type, choose Managed Released. Scroll to the bottom and click Upload and OK on the popup.
Tell Me More....
Just as before, you'll receive an email with a login link when the package is ready.
Tell Me More....
If you created some Merchandise items, the data is preserved in a Zip file so you can import it later. Importing that data is beyond the scope of this workbook, but your customers will be happy to know their data is saved.
What Next?
If you'd like more of an introduction to development on Force.com, try the Force.com Workbook. The Merchandise object in this tutorial is a stripped down version of the Merchandise object in the Force.com Workbook, so you already have a head start. As you complete the tutorials in the Force.com Workbook, periodically package and upload components to create new versions of the app. If you're ready to create your killer app, see the Quick Start in the ISVforce Guide, which takes you through the process of signing up for the Salesforce Partner Program, setting up licensing for your app, and registering for the AppExchange.
10