Part 1: Data

1. Launch K2 Designer (Start > All Programs > K2 blackpearl > K2 Designer)
   (If you do not have the K2 Designer link in your start menu, check with your K2 administrator to determine what the URL is for your K2 Designer environment.)
2. Right-click All Items and select New Category. Name the new category
   K2 Learning
   (If you have worked through previous tutorials, this category may already exist. If so, skip to the next step.)
3. Right-click K2 Learning and create a new category. Name it
   Sales Orders
4. Create three new categories under Sales Orders. Name them
   Forms
   SmartObjects
   Views

Your categories should look like the image below:

1. Launch the K2 Management site. (Start > All Programs > K2 blackpearl > K2 Management)



2. In the Management menu, expand the Integration category, then click Service Types.



3. The available service types are displayed in the Service Types central pane. You will be adding a service instance of the SQL Server Service type for this step. To help you locate the correct service type, enter
   sql
   into the search text box, then click the green refresh icon.
The Service Types node contains the available service types (or connectors). Instances of service types are individual connections containing specific configurations. For example, you will add an instance of the SQL Server Service type and configure it to connect to an external SQL database. By creating the service instance, K2 will discover the properties and methods that define the SQL data source.



4. At least two service types for SQL are returned: SQL Reporting Service and SQL Server Service. (There may be additional service types depending on your environment.) Click to highlight SQL Server Service, then click the New Instance button.



5. Use the table below as a guide for configuring the service instance. For additional reference, see the image below the table. Click OK after you have set the fields.
Notice the option to generate SmartObjects for the service instance (at the bottom of the page). Checking this option will result in K2 creating SmartObjects from all of the objects it discovers in the service instance. You will be creating your own SmartObjects in the next step using K2 Designer, so you don't want K2 to automatically generate them for you.

	Field Name	Setting
A	Display Name	Sales Orders
B	Description	This service instance connects to an external SQL data source and provides values for drop-down lists.
C	Service Type	SQL Server Service (default)
D	Authentication Mode	Static
E	User Name	K2LearningUser
F	Password	K2LearningPass
G	On Different SQL Server	true
H	Command Timeout	90
I	Database	K2Learning
J	Server	uh8ydarb4m.database.windows.net
K	Use Native SQL Execution	false
	Generate SmartObjects for this Service Instance	NOT CHECKED



6. You should see a confirmation dialog box. Click OK to close the dialog box.

Take a moment to locate the new service instance you just created using the following steps.

7. Still in the Integration node, click Service Instances. Scroll down and locate the Sales Orders service instance. (You may need to navigate to page 2, depending on the number of service instances already created.) Notice the name, description and service type correspond to your configuration settings.
You can also search for "sales" instead of scrolling through the pages.

STEP 2 REVIEW

In Step 2 you began working with the first of the four main components for K2: Data. In the K2 Management site, you explored the available service types, then added a new service instance from the SQL Server Service type. In the next step, you will create corresponding SmartObjects which will allow you to leverage the properties and methods of the external SQL data source.

1. In K2 Designer, right-click the Sales Orders SmartObjects category and select New SmartObject.



2. Click Next on the home screen. Name the SmartObject
   Regions
   and select the Advanced SmartObject option. CHECK the box to Allow this SmartObject to be used in Workflows. Click Next when ready.
When you select Allow this SmartObject to be used in Workflows, you are configuring K2 to expose the SmartObject properties and methods available as wizard options when building workflows using K2 Designer. Since you will be building your workflow using K2 Studio in this tutorial, this setting is not actually required. However, if you decide to build workflows using K2 Designer at some point, you should be aware of this setting.



In the next step you are going to select the method type you need for your application. Thinking back to your application design, this SmartObject will be used to populate the region drop-down list on your form. To accomplish this, you only need one method (list) which lists out rows of data source content. If you were going to add a provision that allows users to create new items in this data source, you would simply repeat the steps and add another method to create a new record.

3. On the SmartObject Designer screen, click the Methods tab. Click Add. Locate the Sales Orders service instance you created in the previous step and expand the tree until you can select the [Denallix].[Region] List method. Click Next to continue.



4. The Method Details are fine as is, so click Next. On the Default ServiceObject method bindings screen, click Create All.
Behind the scenes, K2 is creating all of the Regions SmartObject properties (think columns in a table) based on all of the [Denallix].[Region] properties it finds. The Regions SmartObject properties will have the same name as the [Denallix].[Region] properties. If you wanted different names for your SmartObject properties, you could create the SmartObject properties first, then manually map them to the corresponding [Denallix].[Region] property. (Recall that Sales Orders is the name of the service instance you created in the Management site.)

Click Next.



Your screen should look like the image below. You can see that the service instance for this SmartObject is the Sales Orders service instance and the method you have selected is list, based off of the Denallix.Region table. Click Finish to complete and close this SmartObject.

When working with SmartObject using a designer, the finish command saves the SmartObject and publishes it to the K2 server.



You have now created your Regions SmartObject which will be used to populate the region drop-down list on your form. Using the same steps as above, you will create two more SmartObjects from the Sales Orders service instance. Customers will populate your customer drop-down list based on which region is selected. Products will populate the products drop-down list.

5. Right-click the SmartObjects Category and select New SmartObject. Click Next if you are first on the home screen. Name the SmartObject
   Customers
   and select the Advanced SmartObject option. CHECK the box to Allow this SmartObject to be used in Workflows. Click Next.
6. On the SmartObject Designer screen, click the Methods tab, then Add. Navigate to the Sales Orders Service Instance, [Sales].[Customer] table and select the List method. Click Next.
7. The Method Details are fine as is, so click Next. On the Default ServiceObject method bindings screen, click Create All. Click Next. Click Finish, then Finish once again to complete the Customers SmartObject.
8. Create a new Advanced SmartObject named
   Products
   and Allow this SmartObject to be used in Workflows. Click Next.
9. Click the Methods tabs and click Add. Navigate to the Sales Orders Service Instance and expand the tree until you can select the [Sales].[Product] List method. Click Next to continue.
10. The Method Details are fine as is, so click Next. On the Default ServiceObject method bindings screen, click Create All. Click Next. Click Finish and then Finish once again to complete the Products SmartObject.

Your SmartObjects category should look like the image below.

STEP 3 REVIEW

In Step 3 you created the Regions, Customers and Products SmartObjects using the Sales Orders service instance. SmartObjects allow you to leverage the properties and methods for a specific data source. In a later step, you will associate the Regions SmartObject and the Products SmartObject with form controls, which will result in the drop-down lists being automatically populated with the appropriate data when the form loads.

1. In K2 Designer, right-click the Sales Orders SmartObjects category and select New SmartObject. Click Next on the SmartObjects home screen. Name the SmartObject
   AD Sales People
   and select the Advanced SmartObject option. CHECK the box to Allow this SmartObject to be used in Workflows. Click Next to continue.



2. Click the Methods tab, then Add. Expand the Active Directory Service2 ServiceObject trees until you reach the AD User service instance. Select the GetUsers method and click Next.



3. The Method Details are fine as is, so click Next. On the Default ServiceObject method bindings screen, click Create All. Click Next to continue.



Your screen should look like the image below. Click Finish, then Finish again to complete the AD Sales People SmartObject.

STEP 4 REVIEW

In Step 4 you created a SmartObject connection to Active Directory. In later steps, you will use this SmartObject for a picker control to select the sales person assigned to the sales order. By creating all of the input and return methods, you gain access to the sales person’s Active Directory properties. One property (Manager) is populated with the employee's immediate manager name. In your workflow, you will assign a user task to the manager to approve or not approve the order.

1. In K2 Designer, right-click the Sales Orders SmartObjects category and select New SmartObject. Click Next on the SmartObjects home screen. Name the new SmartObject
   Sales Orders Header
   and select the SmartBox SmartObject option (it should be the default). CHECK the box to Allow this SmartObject to be used in Workflows. Click Next to continue.



Notice that K2 has automatically generated the key identifier: ID, property. This property creates a unique identifier for each record that is added to the SmartObject. In a later step, you will associate this ID with the HeaderID that you will create in the Sales Orders Items SmartObject. This will bind the two SmartObjects together, creating a parent-child relationship.



2. Click Add. Enter the following properties: (See the image below the table for reference.) Click OK, then Next when you have finished adding the properties.

Name	Type	Notes
Region	Text	The region drop-down list will be populated with data from the Regions SmartObject.
Customer	Text	The customer drop-down list options will cascade from the Region selected.
Sales Person	Text	The sales person will be a picker control that allows the user to enter just a few keystrokes before it auto-fills based on the characters entered.
Order Date	Date
Ship Date	Date	You will configure an expression for the ship date so that it is seven days after the order date.
Purchase Order Number	Text
5% Tax	Decimal	You will configure an expression so that the tax amount is 5% of the sub total.
Sub Total	Decimal	The sub total field will get its value from the order items total for all of the orders.
Total Due	Decimal	You will configure an expression so that the total due is the sub total plus the tax amount.
Comments	Memo
Status	Text	The status field will initially be set to pending, then update to processed as the workflow is completed.



In the next few steps, you are going to associate the Sales Orders Header SmartObject with the Regions and AD Sales People SmartObjects. Associating SmartObjects creates a join statement of sorts, so that your form fields can be automatically populated with data from their corresponding SmartObject. You will first associate the AD Sales People > DisplayName property to the Sales Orders Header > Sales Person property. In a later step, you will change the Sales Person field (on your view) to a picker control so that users can actually search for the sales person they wish to add.

3. On the Configure Associations screen, click Add. Navigate to the AD Sales People SmartObject and click Next.



4. The Define association settings are fine as is, so click Next.



5. On the Association mappings screen, highlight Sales Person and click Assign. Assign the DisplayName property to the Sales Person property. Click OK then Finish.



Next you are going to associate the Region SmartObject > RegionID property with the Sales Orders Header > Region property. By associating the Region property with the Regions SmartObject, the text box (data type) will automatically become a drop-down list that will be populated with content from the Regions SmartObject. (This is because you are using the list method, which returns a list of records.) In a later step, you will bind the regions field (on the Sales Orders Header view) with the customer field (on the same view) and add a filter so that when a region is selected, the customer values will be filtered based on their associated region. This is referred to as cascading drop-down lists.

6. On the Configure Associations screen, click Add. Navigate to the Regions SmartObject and click Next.



7. The Define association settings are fine as is, so click Next.



8. Highlight the Region property and click Assign. Assign the RegionID property to the Region property. Click OK, then Finish.



Your screen should look like the image below. Notice on the right side of the screen are the properties you created for the Sales Orders Header SmartObject. In the central pane, you see the two associated SmartObjects (AD Sales People and Regions) with corresponding lines to the Sales Orders Header properties they are associated with.



Click Finish once again to close the Sales Orders Header SmartObject designer.

STEP 5 REVIEW

In Step 5 you created the first of two SmartBox SmartObjects. SmartBox SmartObjects are K2-provided storage using a SQL server table that is automatically generated as part of the SmartBox component. K2 then provides a series of default methods (create and save, for example) that can be used in forms, views and workflows. The Sales Orders Header SmartObject will store the item view content containing your customer and invoice information.

1. Create a new SmartObject from the SmartObjects category and name it
   Sales Orders Items
   then select the SmartBox option. CHECK the box to Allow this SmartObject to be used in Workflows. Click Next to continue.



2. Click Add and enter the following properties: (See the image below the table for reference.) Click OK, then Next when you have finished adding the properties.

Name	Type	Notes
HeaderID	Number	This property will be the property you associate with the Sales Orders Header SmartObject > ID, property so that each Sales Orders Items record is bound to a Sales Orders Header record. You will create this association through a rule that you will add in a later step.
Product	Text	The product drop-down list will be populated with data from the Products SmartObject.
Quantity	Number
Unit Price	Decimal	You will create a rule that loads the unit price when a product is selected.
Row Total	Decimal	You will create an expression that multiplies the unit price by the quantity for a row total.



Recall in the previous step you associated the AD Sales People SmartObject > DisplayName property with the Sales Orders Header > Sales Person property. You will now perform the same step and associate the Sales Orders Items > Product property with the Products SmartObject > ProductName property.

3. On the Configure Associations screen, click Add. Navigate to and select the Products SmartObject. Click Next.



4. The Define associates settings are fine as is, so click Next.



5. On the Association mappings screen, highlight the Product property and click Assign. Select ProductName from the drop-down list and click OK, then Finish to complete the Sales Orders Items SmartObject. Click Finish to exit the designer.



Your screen should look like the image below. Notice once again the Sales Orders Items SmartObject properties are shown on the right side of the screen with the Products association in the central pane.

STEP 6 REVIEW

In Step 6 you created the last data source required for your application, the Sales Orders Items SmartObject. You associated the Product property with the ProductName property from the Products SmartObject. You also created the HeaderID property, which will be used to bind the Sales Orders Items SmartObject with the Sales Orders Header SmartObject in later steps.

When you are ready to start building the views and forms for this application, continue on to Part 2: Views to get started.