Now you will create properties of mode Page List. Individual properties that belong to a Page type of property (one of mode Page,Page List1, or Page Group) are called embedded properties. The Page mode property is called an embedded page2.
Here, the embedded properties are created automatically when you associate the Page mode property with a data class. The properties already defined in the class become the individual properties for that page.
1. In the Application Explorer, underGLBX-FW-OnboardingFW-Work, expand the Data Model category if it is not already expanded. Right-click Property and selectNewfrom the context menu.
The New Rule dialog opens.
2. In the New Rule dialog, enterHardware Itemsin theProperty Namefield.
1A Page List mode property is a data structure consisting of an ordered list of zero or more pages, each identified by an integer index (starting with 1). Page List is one of the eleven modes a property rule may have. Pages must be created with sequential subscripts: 1 before 2, 2 before 3 and so on.
2An embedded page is a clipboard page that has the value of a property of mode Page. Any page on the clipboard that is not a top-level page is an embedded page. Process Commander uses a recursive page structure. Pages con-tain properties that can have single or multiple pages as their values. For example, the Obj-Browse method creates an array of embedded pages (all of the same class) that contain its results.
3. Confirm theApplies To,RuleSet,Version, andTypefields are set toGLBX-FW-OnboardingFW-Work, OnboardingFW,01-01-01, andText.
4. Click Create. The Property form for this new property rule displays.
5. In theProperty Modefield, selectPage Listfrom the drop-down list.
6. In thePage Classfield, type GLBX, and then use the SmartPrompt to see the classes beginning withGLBX-.
Select theGLBX-Data-Hardwareclass. This associates this Page List with the data table that is based on classGLBX-Data-Hardwareand the values in that data table.
7. Confirm that theGeneraltab matches the following image.
8. Click theAdvancedtab.
9. Check theAuto-populate Propertycheckbox. This enables the property values to be automatically populated at run-time with the values from the associated data table.
10. Do not make changes to the other fields, and click Save ( ) to save the property.
11. Use the Application Explorer to verify the newly created HardwareItems property appears. Click the icon to close the rule form's tab.
12. Repeat steps 1 to 11 above to create the SoftwareItems property.
Property Name Software Items
Property Mode Page List
Page Class GLBX-Data-Software
At this point, confirm that the HardwareItems and SoftwareItems properties are listed in the Application Explorer, and each has an embedded property named Price.
The two Price properties came from the zip file you imported before beginning this tutorial. You did not create them.
The zip file provided the data classes specified for the HardwareItems and SoftwareItems properties, and the sys-tem automatically creates the Price property when you associate the embedded page with the data class.
Continue to the next tutorial topic.
Review
In this step you created a data model for your application by:
n Creating a single-value property
n Creating multiple properties using the Property Wizard
n Creating embedded properties
To read more about the skills you used in this step, see
n Introduction to Properties [KB 26322]( )
n Property Mode definition [Developer Help]( )
n Page definition [Developer Help]( )
In this step, you created the process-specific properties that display and capture information for the equipment request process. Now a user interface is needed to use that information. The user interface should be designed to meet the stakeholders' use cases and requirements. In the next tutorial step, you develop an initial user interface that the business analyst can bring to the stakeholders to get their input.
Move to the next step in the tutorial.
Step 6: Extend the default user interface
Typically performed by In the previous step, you
The work item begins to look more like what is desired by the stake-holders, and you can run the process and display the work item for them to get their feedback
The project has a series of requirements for the application user interface. They include:
n The HR Staff Member has to be able to enter basic new-hire information, including first and last name, depart-ment, and manager
n The HR Staff Member needs a method to specify the hardware and software package for the new hire
n The Hiring Manager needs to be able to see what the budget limit is for equipping this position, and the cost of the selections made so far, so that the Hiring Manager knows whether to approve the work item
In addition, the user interface should comply with standard usability guidelines, including these:
n It should be clear at all times what the current operator can do
n The user interface should require a minimum of scrolling to see all elements of the current form To learn more about interface design, seeTop Ten Usability Guardrails [KB 26006].
The application already includes some user interface resources, created in Step 2. These include:
Item Name
Four harness rules Confirm
New Perform Review
Four section rules CoreSummary Header NewHeader WorkObjectInfo
You can see these in the Application Explorer by expanding the User Interface category under GLBX-FW-Onboard-ingFW-Work, and expanding the Harness and Section categories.
Before beginning this tutorial, you imported a zip file of resources. This collection included the following items:
l Two activities:getHardwareandgetSoftware
l Two data tables and their associated classes:GLBX-Data-HardwareandGLBX-Data-Software
These items are provided because creating activities and data tables falls outside the scope of this tutorial. These data tables provide values that are used in some of the user interface controls you create in this tutorial step.
In Step 4, you created two flow action rules, but did not associate them with user interface resources. You make those associations in this step.
The data model, which you built in Step 5, provides all the properties you need for this step.
To promote modularity and reuse, a best practice is to create sections to hold needed user interface elements, and then combine those sections in a meaningful way within the harnesses associated with the various steps of the proc-ess. This tutorial step describes how to:
1. Update an existing section 2. Create new sections
3. Add properties and controls to the sections 4. Add the sections to harnesses and flow actions Continue to the next topic to begin this step of the tutorial.