Extend an MDK App with Customer Orders

This page will display customer orders list, you will add an Object Table control that is used to display information (like Sales order ID, order creation date, gross amount and life cycle status name) about an object.

You can find more details about available controls in section page.

In SAP Web IDE project, right-click the Pages folder | New MDK Page | Section Page | Next.

You can find more details about section pages.

Enter the Page Name Customers_Orders and click Next and then Finish on the confirmation step.

In the Properties pane, set the caption to Customer Orders.

Next, add an Object Table compound to display information like sales order ID, order creation date, gross amount and life cycle status name.

In the Layout Editor, expand the Controls | Compound section, drag and drop the Object Table control onto the page area.

A Compound control contains a group of other controls. Unlike in a container control where you can add your own child controls (container items), the child controls in a compound control are fixed. You can populate each of its child control by defining its data binding, depending on which the child controls are created.

In the Properties pane, select the previously added service from the Service drop down and then select SalesOrderHeaders entity set from the dropdown. This way, the Object Table has been bound to SalesOrderHeaders entity.

Provide below Properties:

For a given customer id, query expression will filter top 5 order entries returned in descending when sorted by the order creation date property.

Now start binding Object Table properties with SalesOrderHeaders entity set properties.

Provide the below information:

$(D,{CreatedAt}) is an expression of how to format a date, end result would be like 8. Jun 2018. By default it will be formatted to the device’s locale setting.

$(C,{GrossAmount},{CurrencyCode},'',{maximumFractionDigits:2,useGrouping:true}) is an expression of how to format currency value, end result would be like 200.44 €. By default it will be formatted to the device’s locale setting.

In the Search section of the Properties pane, change both the Search Enabled property and Barcode Scanner property to true.

In the Behavior section of the Properties pane, select DisclosureIndicator to AccessoryType property.

In the Empty section of the Properties pane, provide No Orders Found for the caption property.

Save your changes to the CustomerOrders.page.

This page will show related details for an order. In this page, you will add an Object Header control that is used to display information (like first name, last name, date of birth, email address & phone number) about the header of an object and Static Key Value control to display key value pair items like address, city, postal code & country.

In SAP Web IDE project, right-click the Pages folder | New MDK Page | Section Page | Next.

Enter the Page Name SalesOrders_Detail and click Next and the Finish on the confirmation step.

In the Properties pane set the Caption to Order Details.

Next, you will add a Static Key Value container and its container item Key Value Item to display information like sales order id, life cycle status & date of order creation name.

Static Key Value is a container that can display one or more key value pair items on a section page. In this container, you can include a Key Value Item, a simple key value cell that displays a label and a text pair. You can find more details here about this container.

In the Layout Editor, expand the Controls | Container section, drag and drop the Static Key Value control onto the page area.

Now, add key value item to this container. In the Layout Editor, expand the Controls | Container Item section, drag and drop the Key Value Item control onto the page area.

Provide the below information:

Make sure to select values for the mentioned properties only from SalesOrderHeader entity. You may find similar values from other entities.

Repeat the above step by adding 5 more Key Value Item on the page.

Provide the below information:

You should have final binding for all key value items as below:

Save your changes to the OrderDetails.page.

Now, you will create two Navigation actions that opens the Order List and Order Details page when called.

Right-click on the Actions folder | New MDK Action | choose MDK UI Actions in Category | click Navigation Action | Next.

Provide the below information:

Click Next and then Finish on the confirmation step.

Repeat the above step and create a new navigation action.

Provide the below information:

Click Next and then Finish on the confirmation step.

Go back to the Customers_Orders.page and set the OnPress event of the Object Table. You will link the Object Table to the NavToSalesOrders_Details.action so that when an end-user selects a order, the SalesOrders_Detail.page will open. MDK automatically passes the selected order to the details page.

In Customers_Orders.page, select the Object Table, click the link icon under the Events tab for the OnPress property to open the Object Browser.

Double-click the NavToSalesOrders_Details.action and click OK to set it as the OnPress Action.

Save the changes to the Customers_Orders.page.

Next, you will add an Object Table compound to display top 5 orders information in the Customers_Detail.page.

In the Layout Editor, expand the Controls | Compound section, drag and drop the Object Table control onto the page area.

In the Properties pane, select the previously added service from the Service drop down.

Provide below Properties:

The odata.readLink annotation contains the read URL of the entity or collection.

SalesOrders is a navigation property in Customer entity to SalesOrderHeader entity. You can find this information in OData service metadata document.

Query expression will filter order entries returned in descending when sorted by the order creation date property.

Now start binding Object Table properties with SalesOrderHeaders entity set properties.

In the Appearance section of the Properties pane, provide the below information:

$(D,{CreatedAt}) is an expression of how to format a date, end result would be like 8. Jun 2018. By default it will be formatted to the device’s locale setting.

$(C,{GrossAmount},{CurrencyCode},'',{maximumFractionDigits:2,useGrouping:true}) is an expression of how to format currency value, end result would be like 200.44 €. By default it will be formatted to the device’s locale setting.

In the Behavior section of the Properties pane, select DisclosureIndicator to AccessoryType property.

In the Empty section of the Properties pane, provide No Customer Orders Found to Caption property.

You may also want to open SalesOrders_Detail.page when clicking on any order in Customers_Detail.page. For this, you will set OnPress event of the Object Collection and link it to NavToSalesOrders_Details.action so that when an end-user selects a order, the Order Details page will open. MDK automatically passes the selected order to the details page.

In Customers_Detail.page, select the Object Collection, click the link icon under the Events tab for the OnPress property to open the Object Browser.

Double-click the NavToSalesOrders_Details.action and click OK to set it as the OnPress action.

Save the changes to the Customers_Detail.page.

For orders grid area, you will add a header to display some text label.

In the Layout Editor, expand the Controls | Section Bar section, drag and drop the Header control above the order grid area.

Provide the below information:

Save the changes to the Customers_Detail.page.

You can find more details about Header controls.

For orders grid area, you will also add a footer to display total count of orders for a customer.

In the Layout Editor, expand the Controls | Section Bar section, drag and drop the Footer control above the order grid area.

Provide the below information:

You can find more details about Footer controls.

You may also want to open Customer Orders page when clicking on See All. For this, you will set OnPress event of the Footer control and link it to NavToCustomers_Orders.action so that when an end-user clicks on See All, the Customer Orders page will open.

In Customers_Detail.page, select the Footer control, click the link icon under the Events tab for the OnPress property to open the Object Browser.

Double-click the NavToCustomers_Orders.action and click OK to set it as the OnPress Action.

Save the changes to the Customers_Detail.page.

Deploy the updated application to your MDK client.

Right-click on the DemoSampleApp MDK Application in the project explorer pane and select MDK Deploy and Activate.

Since we have deployed already both the destination and app id should be pre-selected based on the last time you deployed our application.  Confirm the Destination Name is mobileservices_cf and the Application Id is com.sap.mdk.demo and click Next.

Re-launch the app on your device, you may asked to authenticate with passcode or fingerprint. When you see a confirmation pop-up, tap OK. Tap CUSTOMER LIST.

You will see the CUSTOMER ORDERS area in customer detail page and also total count of orders.

In sample service backend, Not every customer has related Sales Orders in case if you see No Customer Orders Found message. Try with other customer record.

Tapping on any order navigates to its details page.

Navigate back to Customer Detail page, tap See All, which navigates to the Customer Orders page.

Re-launch the app on your device, you may asked to authenticate with passcode or Touch ID. When you see a confirmation pop-up, tap OK.

You will see the Customer Orders area in customer detail page and also total count of orders.

In sample service backend, Not every customer has related Sales Orders in case if you see No Customer Orders Found message. Try with other customer record.

Tapping on any order navigates to its details page.

Navigate back to Customer Detail page, tap See All, which navigates to the Customer Orders page.

Are you wondering how exactly MDK knew that clicking on a record in list page would display respective record in detail page?

The MDK sets the current object to the selected record when running the on press action on the list. The detail page then just needs to reference the correct properties assuming they are part of the object from the list page.