Notes: This project assumes that basic knowledge of SUP, primarily in the area of workflows.

Prior to starting to use this guide, you should have started the SUP services, and have knowledge of the workspace, and associated SUP services. This guide also assumes that you have either an iPhone or blackberry device registered with SCC. This guide is designed for users who have had some experience with making workflows, but want to use customization to further enhance the look and feel. Setting up the sample projects: 1. Download the sample projects and place them on your desktop (or another desired location) 2. Launch the SUP Workspace 3. Connect to the sample database, and connect to your SUP server. 4. Click on File->Import , select Existing Projects into Workspace under the General Tab

a.

5. Select the root directory to be the folder where you downloaded and unzipped the sample projects

6. Each project contains a data.sql file. Youll need to run that to generate the back end data. Right click on the sql file and click Execute SQL files.

a.

7. Next, right click on the Mobile Business Object folder, and click Deploy Project. This deploys the SUP data model to the server, so your apps can interact with it.

a.

8. Follow through the wizard to complete deployment.

9. Next, right click on the SampleInventory.xbw, and select Generate Mobile Workflow Package

a.

10. Make sure you assign the workflow to the user registered in SCC. To do this, press Get Users button.

Finally, check your app inbox for the deployed workflow.

Sample Approval Info You can use the app to add requests. The name that is used for the owner column is the

device id (the activation name you put into SCC). This app is designed to be an example and show you the possibilities of SUP. Thus the app does not too closely reflect a real world application. In Sample Approval, you actually have the power to approve your own requests. There are two ways to get items to show up in My Approval. For a production application, there will a piece in the backend of your choice that handles the business logic of determining of how to fill in the approver field (say sql triggers). Use the App Any request you add will be added in the backend db with approver = admin. This way you can actually approve our own requests. The value admin is a static value defined in the create operation of the LeaveRequestItem MBO.

Manual SQL (Extracted from data.sql): INSERT INTO LeaveApprovalItem(owner, approver, itemStatus, itemType, startDate, endDate, extraNotes) VALUES ('John Doe', 'admin', 'Pending', 'Vacation', '2011-01-01', '2011-0201', 'Honeymoon request.' ); Adds an entry into the My Approvals section when you make the query. Notice that the approver field has the value admin. To add values, simply add the sql to the bottom of the data.sql, or you can manually do so through any sql tool of your liking. However, mind you that if you do so through the included data.sql, it will drop the table first, erasing your current LeaveApprovalItems. You can always hardcode a set of Requests using the same format as above. Simply leave the approver field empty, and replace the owner field, with your device id. (Can be found in settings,

username settings)