In the SAP Cloud Applications Studio for Cloud for Customer two different UI “paradigms” are supported:
They are used for:
In this document, I will outline the features of the thing-based UIs as supported in the SAP Cloud Applications Studio for Cloud for Customer. This document is relevant for you if are developing (or planning) a custom solution for SAP Cloud for Customer with SAP Cloud Applications Studio and you want to learn about the thing-based UI.
I assume that you are familiar with UI development in SAP Business ByDesign (if not, read the introducing documentation on the UI designer in the help documents or Chapter 4 “User Interface” of my book “SAP Business ByDesign Studio -Application Development” ( http://www.sap-press.com/products/SAP-Business-ByDesign-Studio-%E2%80%94-Application-Development.htm... ).
This document does not replace the documentation and the how-to guides on UI development, but is meant as an overview on the features.
The following figures provide an overview on the UI paradigms in ByDesign and in Sales OD:
Figure 1: OBN-based screens: (1) Work center; (2) Work center view; (3) Object work list (OWL); (4) Quick activity; (5) Object instance; (6) Object-based navigation. (Figure taken from my book “SAP Business ByDesign Studio -Application Development”)
Figure 2: Thing based screens: (1) Work center; (2) Work center view; (3) Object work list (OWL); (4) Quick Create; (5) Quick View; (6) Thing Inspector; (7) Thing Type; ES: Enterprise Search; FD: Feeder
The follwoing terms and abbreviations are used in this document:
Here we go. The complete prototype takes about 1 hour.
First, I will define the business object Project in the SDK, save and activate it:
import AP.Common.GDT as apCommonGDT;
import AP.CRM.Global;
import AP.FO.BusinessPartner.Global;
import AP.PC.IdentityManagement.Global;
businessobject Project raises NoValidPeriod, NoValidAccount {
message NoValidPeriod text "Enter a valid period";
message NoValidAccount text "Enter a valid account";
[AlternativeKey] element ID : ID;
element Name :LANGUAGEINDEPENDENT_EXTENDED_Name; // 255 char
[Label("Account")] element AccountID : BusinessPartnerInternalID;
association ToAccount to Customer;
[Label("Opportunity")] element PrecedingOpportunityID : BusinessTransactionDocumentID;
association ToOpportunity to Opportunity;
[Label("Owner")] element ResponsibleEmployeeID : EmployeeID;
association ToResponsibleEmployee to Employee;
[Label("Start At")] element StartDate : Date;
[Label("End At")] element EndDate : Date;
element SalesVolume : Amount = {currencyCode = "USD"};
element ComplementaryMaintenance : Indicator;
element EndOfComplementaryMaintenance : Date;
[Label("Status")] element ProcessingStatusCode: ProcessingStatusCode = "1";
[Label("Changed At")] element ChangedDateTime : GLOBAL_DateTime;
association ToChangedIdentity to Identity;
}
If you are an experienced SDK user, you will have noticed that I have used features in the BO definition language to set the Label and default values (for example for the currencyCode element).
On top of the Project custom business object, I will create a UI for creation, viewing and editing. So, I just have to select the business object, select Create screens from the context menu and select “Screen Scenario with Thing-based Navigation in the dialog box. The system creates
After generation, I can immediately assign the work center and work center view to my test user and start creating projects in the UIs. Of course, I can also start the screens directyl from the SDK with my development user.
The generated screens need some “fine tuning”. These manual activities include:
For the fine-tuning of the UIs, you can use the same procedures as for ByDesign (see the documentation on the UI designer in the help documents or Chapter 4 “User Interface” of my book “SAP Business ByDesign Studio -Application Development” ( http://www.sap-press.com/products/SAP-Business-ByDesign-Studio-%E2%80%94-Application-Development.htm... ).
Even “mixed UI scenarios” are possible. For example, you can configure an OBN from a screen that belongs to a thing-based UI scenario to a screen that belongs to OBN scenario.
Figure 3: Thing based screens: Work Center/View; Object Work List (OWL) with Card View, and Quick View
The default query QueryByElements that is generated for each BO node does not support full index support. It has in general a linear dependency on the number of instances in the business object node. Therefore it should be used only if:
In all other cases, an application-defined query (defined by Query Wizard)) has to be used. An application-defined query supports full index support on all query elements.
As a new feature in the SDK for Sales OnDemand, you can alternatively define an application-defined query directly in the UI designer. In the UI designer, this is called a "SADL query".
The generated OWL uses the generated QueryByElements query of the BO root node. To convert the OWL, perform the following configuration steps in the generated OWL:
(For details on application-specific queries and for find forms, see the help documents or Sections 3.6 and 4.3 of my book “SAP Business ByDesign Studio -Application Development” ( http://www.sap-press.com/products/SAP-Business-ByDesign-Studio-%E2%80%94-Application-Development.htm... )).
Tags, Flags, Favorites, and Sticky notes on custom UIs are supported. Prerequisites is that BO is enabled for Enterprise Search (see the respective section, below). Another prerequistie is a meaningful configuation of the primary and secondary text in the QV and the TI.
Enterprise search and feed enabling for a custom BO can be configured in the “Create Query” wizard of the SDK (context menu on the business object definition project item). In the “Create Query” wizard, new flags “Enable for Enterprise Search” and “Enable for Feed” have been introduced.
As a manual activity, you have to configure the BO as “Enterprise Search Object” in the work center view.
You can use thing-based screens (OWL, QV,QC, TI) directly on tablet PCs (currently supported: iPad player). The following properties have to be configured on the floor plans: Tags: Device = “Tablet” & Device = “Desktop”.
Figure 4: Thing based screens on a tablet computer
For smartphone UI, you have to configure additional screens tailored for usability on smartphones. Here, the same rules and guidelines as for ByDesign apply.
You can use REST/OData-based web services of the ByD/SoD tenant for user-to-system communication. SAP supports the OData-Protocol. OData follows the principles of REST. OData provides a uniform interface. This means that when you address items in an OData communication, you interact with a service (using HTTP verbs) in the same way across any OData Service (i.e. how to construct URIs), regardless of the data it exposes. For details on the OData protocol, see http://www.odata.org.
REST/OData-based web services are
Scope
Usage: User to system communication (for example for native mobile devices)
Development process overview (1): thing type-based REST services
Development process overview (2): report based REST services: To be done
The REST service URL to query all instances of a custom BO is composed as:
<https://<hostname>/sap/byd/rest/<workcenter.svc>/<thing type short ID>+”s”>
Thing-based SAP screens of Sales OnDemand are extensible. Stable anchors on the UI floor plans define the positions and the outports that can be used for extensibility. The following main extension scenarios are supported:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
26 | |
18 | |
15 | |
13 | |
11 | |
9 | |
8 | |
8 | |
8 | |
7 |