Simplifier Academy

Courses & Documentation

PDF generated April 30, 2019

New Features Release 3.5

The Documentation refers to the latest version of the Simplifier. If you have an On-Premise installation and need help with an older version, please contact us via support@itizzimo.com, we are glad to support you.

New Features

Client-side Business Objects

Business objects can now also be executed directly on the browser or on the respective mobile device. They are created centrally and can therefore be reused several times. Read more »

Tags of connectors and business objects for easier search / categorization

Each connector/business object, widget and data type can now be tagged. For example, project-related configuration objects can be given a project name, which makes them easier to find again.

Automatic reloading of the preview when saving in the UI Designer

Every click on the “Deploy” button automatically updates the preview in the browser.

New Business Object API incl. autocompletion

Within a business object, the most common functions can be accessed using a uniform API and auto-completion. Read more »

Logging & Monitoring for Connectors and Business Objects

Via the Logs & Monitoring you can now see who did the last changes in a connector or business object.

Mobile Log

Errors in the Simplifier Mobile Client can now be evaluated centrally.

Application configuration level

You can now check how much programming effort is avoid through the low-code approach, the degree of configuration is now displayed in percent in the application overview. Read more »

Interactive API documentation

Simplifier Universal Client for Android

We have reworked our Simplifier Universal Client for Android to include the same features as in the iOS Universal Client. In addition to the function that you can work offline with the Simplifier client or the autostart function for already installed business applications, we now also support the fingerprint sensor for login with Android. Furthermore, the Android client now appears in a new layout in the native Android material design.

Moreover, we offer an optimized menu navigation on data glasses, depending on the hardware complete with voice control. Support information is also automatically transmitted to the server on request.
And for the developers, we now offer a developer mode that displays errors from the console directly on the device.

_______________________________________________

Getting Started

Using state-of-the-art technologies, we accelerate your application creation. We have designed and built our platform in terms of logic and usability to accommodate the modern, agile development processes within companies. Due to the low-code approach, applications no longer need to be elaborately programmed but can be easily configured and integrated into any system. Thus, applications can be mapped process-oriented.

Basically, creating an application with our Simplifier can be divided into the following 5 steps:

_______________________________________________

What is the Simplifier?

The Simplifier is a low code platform for mapping business processes in integrated business and IoT applications and to interconnect internal and external IT infrastructures. Applications only need to be configured once to be available on any mobile device and operating system.

Main Features:

• Web-based Development Environment to configure integrated
  Mobile, Wearable and Browser applications
• Customization of Applications with UI Designer, Visual Scripting for SAPUI5 and AngularJS based Applications
• Customization of Backend Interfaces through standardized Connectors (SOAP, REST, XML, IDoc, MQTT, OPC UA, API, CSV)
• Rapid Deployment and OTA-Updates
• Contextual Technologies (Augmented Reality / Realtime Communication, Scanning, Sensors)
• Multi-Device (Browser, Phones, Tablets, Glasses, Watches)
• Multi Platform Universal Client (Android, iOS, Windows)

_______________________________________________

The Dashboard

The Dashboard is the place for you to start. It gives you a clear overview about your Simplifier instance. Here you find information about:

• Marketplace
• Users and their roles
• Applications
• Connectors
• Plugins
• Transports
• Business Objects
• Logs and Monitoring
• Data Types
• Jobs

_______________________________________________

Start Simplifier for free

The Simplifier Freemium (free + premium) account contains a test environment where you can see and test selected features. The Freemium account comes with predefined application templates and example applications for different use cases.

Apply for an account by filling out the registration form on simplifier.io

You can test the Simplifier extensively and completely free of charge for 90 days. After 90 days the Simplifier is of course still for free use, only the server hosting has to be paid for.

You have the possibilities to create as many applications as you like and create and configure connectors to integrate all your systems.

Besides that, you have full administration access including user administration and monitoring and you have unlimited permissions to Simplifier items like widgets, libraries, data types, plugins, jobs and business objects.

_______________________________________________

Prerequisites

[vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]

1. The Admin Interface supports only Google Chrome Browser latest Version -1  & Firefox latest Version -1 for Simplifier Configuration & App Development, please download from https://www.google.de/chrome/browser/desktop/
2. Use Google Developer Tools for Mobile Preview, Console, Debugging and DOM Inspection
3. Install  and use UI5 Inspector to inspect and debug your UI5 Application
4. For testing on mobile devices use Android (>4.4) , iOS (>9) and Windows 10 devices with Simplifier Mobile Client available for iOS and Android
5. Aps created with Simplifier support the second to last Version (n – 1) of the following Browser:
   – Chrome
   – Firefox
   – Safari
   And the Browser:
   – Internet Explorer (Version 10-11)
   – Microsoft Edge

[/vc_column_text][/vc_column][/vc_row]

_______________________________________________

Features and supported operating systems

• Remote Debugging for Mobile Devices
• Debug View within Simplifier Mobile Client (Debug Version)
• Auto-Login Functionality
• App Autostart
• Call Settings

See the full featured list of supported operating systems:

_______________________________________________

Live Debugging with Chrome DevTools

You can debug your applications on the Simplifier in real time on mobile devices.

Enter chrome://inspect into your Chrome browser.

Connect your mobile device via USB and enable “USB Debugging” within the device settings. Chrome will autodiscovering your mobile device and integrating it within the developer tools options.

When connected, you can begin screencasting by clicking the appropriate button in the developer tools window. Then your mobile device can be supplied directly with input from your desktop screen. Any changes are instantly displayed on your mobile device.

By the way, the “Port forwarding” button above provides some flexibility for those who don’t have their screen and developer machine on the same network. In this scenario, you can create a TCP port on your mobile device and assign it to a specific TCP port on your development machine. All forwarded traffic is transferred via USB, bypassing the mobile device’s network configuration.

Mobile Imitation

By clicking the “Toggle device toolbar” button, the current page is reduced to the imitated screen parameters according to the set properties. This imitated display can be operated with the mouse in the same way as with the finger on a physical device.

In this view, you can simulate pinch zooming, finger scrolling and even multi-touch events.

_______________________________________________

Supported Barcode formats

_______________________________________________

Simplifier Mobile Client

Download the Simplifier Mobile Client in the appropriate stores, depending on your mobile device.

Descriptions of how the Simplifier Mobile Client works can be found in the subpages.

_______________________________________________

iOS Client

Below is a description of the Simplifier Mobile Client for iOS. After you have downloaded the Simplifier Mobile Client from the App Store, start it on your mobile device.

First you have to authenticate yourself on the login screen with your Simplifier username and password. Enter the instance you want to access. If the device has a fingerprint reader, you can choose to restore your password with it. You can save your login so you don’t have to re-enter it every time.

Since it is uncomfortably to type the instance, you can also use the QR code login. Read here how to create a corresponding QR code in the Simplifier.

Once you have successfully authenticated yourself, you are in the overview of installed applications. At the beginning, this overview is empty. At any time, you can log out by clicking on the logout button in the top left corner. At the top right, on the Simplifier icon, various information will be displayed.

To now use apps on your mobile device, switch to the screen Browse Apps. You now see an overview of all applications that are on the specified instance. To install apps, simply click on them. When the apps are downloaded, Installed will display a notification with the number of newly installed apps. You can delete installed application by swiping to the left.

If an app, that you have already installed, has been newly deployed on the instance, you will be informed about updates of the application.

At the bottom right, you will find an overview of all settings.

_______________________________________________

Client installation on Windows

If the Cordova Simplifier client and -server are running in a closed network, and the SSL certificates are self-signed, it is necessary to install a special version of the Simplifier mobile client on Windows. This version contains certain permissions that are not compatible with the Windows Store.

You need 2 files for the installation:

• <name>.appxbundle – Contains the client for x86, x64 and ARM processors.
• <name>.cer – Contains the developer certificate of the app.

There are 2 ways to install the client. In either case, the “developer mode” must be enabled in Windows to allow applications to be “cross-loaded”. This process is equal to Android and the menu item “Unknown origin”.

If a “certificate error” is displayed in one of the steps, please refer to the section “Installing the certificate” below.

*ATTENTION*

It is mandatory to be in the local domain. This requires at least Windows 10 Pro or Enterprise!

Prerequisites

Developer-Mode

Please follow these steps:

• Settings → Update and Security → For Developers
• Enable the developer mode and install the equivalent packages
• finished

Install the certificate

At first, the developer certificate must be installed:

A wizard opens where you should follow the steps below:

• In the welcome screen, select the second item “Local computer”
• Continue
• The Import Wizard opens
• We need again the second point “Save all certificates in the following memory”
• Click “Browse”
• Select “Trusted Root Certification Authorities”

• Click “OK”
• Continue
• A summary of the previous steps is now displayed
• A click on “Finish” completes the operation and the certificate is installed

Option 1: App-Installer

The following app must be installed on the Windows 10 computer: https://www.microsoft.com/en-us/store/p/app-installer/9nblggh4nns1 Store link.

This will associate .appxbundle files and you can start the installation process with a double-click on the file.

This screen will also check the required app permissions. The keyword is “Access to home or workplace networks” to head to the local Simplifier instance and “Use company domain credentials”, which is required for the certificate to the instance.

Option 2: Powershell

Switch with the Powershell to the folder with the Simplifier-Files (.appxbundle, .cer). Please note that this is a local location. Network addresses will fail.

Enter the command “Add-AppxPackage <filename> .appxbundle”. The file name may vary.

Example:

The installation process is started.

In the end, the Simplifier app can be started from the Start menu or the Tile menu.

If you are interested in the official Microsoft explanation click on the links below for more information.

• Information about side loading: https://docs.microsoft.com/de-de/windows/application-management/sideload-apps-in-windows-10
• Information about the capabilities: https://docs.microsoft.com/en-gb/windows/uwp/packaging/app-capability-declarations

In our Mobile Client, we use the following capability scenarios:

• Access your Internet connection
• Access your home or work networks (Required for On Premise only)
• Use your enterprise domain credentials (Required for On Premise only)

_______________________________________________

Client Schema

You have the possibility to launch your business application via URL.

Schema: 

simplifierclient:///<action>/<value>?<param>=<value>[&<paramN>=<valueN>]

For explanation:

simplifierclient:// – The url type, on that the simplifier client is registered. All uris with this link opens the client by default. If parameters or path components are missing, at least the client is always started.

/<action> – The action to take. For now only “appDirect” is available.

/<value> – The value for the action.

?<param>=<value> – The URL arguments are beeing passed to webview so business app can access them. So on the client the local href would be something like file:///some_very_long_ios_path/www/businessapps/Simplifier_Explored?foo=1&bar=2

Example: 

simplifierclient:///appDirect/Simplifier_Explored?foo=1&bar=2

The example above launches the simplifier client if installed and runs app “Simplifier_Explored”.

Restrictions:

• Simplifier Client needs to be installed
• if client is not running, client will be startet and user has to login
• shows popup with countdown when a link was clicked
• url-launch is higher prioritized than automatic app-launch
• if client is already running with a business app, nothing will happen to prevent misbehavoir in app lifecyle
• shows warning if desired app is not installed
• if autoupdate before launch is enabled, the business app will be updated before launch
• broken or non valid links are not beeing processed

_______________________________________________

Android Client

Below is a description of the Simplifier Mobile Client for Android. After you have downloaded the Simplifier Mobile Client from the Play Store, start it on your mobile device.

First you have to authenticate yourself on the login screen with your Simplifier username and password. Enter the instance you want to access. If the device has a fingerprint reader, you can choose to restore your password with it. You can save your login so you don’t have to re-enter it every time.

Since it is uncomfortably to type the instance, you can also use the QR code login. Read here how to create a corresponding QR code in the Simplifier.

Once you have successfully authenticated yourself, you are in the overview of installed applications. At the beginning, this overview is empty. At any time, you can log out by clicking on the logout button in the top left corner. At the top right, on the Simplifier icon, various information will be displayed.

To now use apps on your mobile device, switch to the screen Browse Apps. You now see an overview of all applications that are on the specified instance. To install apps, simply click on them. When the apps are downloaded, Installed will display a notification with the number of newly installed apps. You can delete installed application by swiping to the left.

If an app, that you have already installed, has been newly deployed on the instance, you will be informed about updates of the application.

At the top right, you will find an overview of all settings.

_______________________________________________

Access Business Objects within Applications

To address Business Objects in your application, you do not have to call them in JavaScript code any longer. Simply use the activity “Data Objects” in the Process Designer. For more information, take a look at the documentation of the activity Business Object.

_______________________________________________

Access Connectors

You can access all connectors you’ve previously assigned to your business object inside your script template.

Simplifier.Connector.<ConnectorName>(payload?: string|object): object

Example:

var connectorResult = Simplifier.Connector.MySoap({bindingName: "Binding", "operationName": "MyOp", "soap": {"foo": "bar"}});

Each call to a connector in a script template follows this convention:

Simplifier.Connector.<ConnectorName>.<CallName>(payload?: string|object): object

Example:

var connectorCallResult = Simplifier.Connector.MySoap.myCall({"Foo": "bar"});

_______________________________________________

Access other Business Objects

You can call any other Business Objects in your current one in a similar way than calling a connector, using the following syntax:

Simplifier.BusinessObject.<BOName>.<MethodName>(payload?: string|object, parametrized?: boolean = true): object

Simplifier.CurrentBusinessObject.<MethodName>(payload?: string|object, parametrized?: boolean = true): object 

The payload has to be a stringified JSON object. The result of the business object method is a string and therefore it has to be parsed.

Example:

var otherMethodResult = Simplifier.BusinessObject.OtherBO.someMethod({"foo": "bar"});

var unparamtetrizedResult = Simplifier.BusinessObject.OtherBO.someMethod("{\"foo\": \"baz\"}", false);

var sameBoResult = Simplifier.CurrentBusinessObject.someMethodOnSameBO({"baz": "baz"});

var noArgsResult = Simplifier.CurrentBusinessObject.methodWithoutArgs();

_______________________________________________

Access Plugins

Call a plugin from your business object using this syntax:

Simplifier.Plugin.<PluginName>.<SlotName>(payload?: string|object): object

Example:

var repos = Simplifier.Plugin.contentRepoPlugin.listRepos(); 

var newRepo = Simplifier.Plugin.contentRepoPlugin.createRepo({name: "MyRepo"}); 

Simplifier.Plugin.contentRepoPlugin.updateRepo("{\"id\": 15}");

_______________________________________________

Action

Currently the Action shape is divided into Navigation, UI Action, Mobile Action and Server Action.

_______________________________________________

Active Directory

The Simplifier can sync users of Active Directories, like users from other LDAP sources.

_______________________________________________

Add a connector call to an existing connector

A connector call represents one (sub)-operation of a connector, for example a soap wsdl has one or many operations – here you can customize each one as a call.

Step 1

Choose a connector from the overview and click the call icon. In the call overview add a new call for each connector operation.

Step 2

For SOAP and SQL connectors, you have the possibility to use the Connector Wizard. It helps you to create your connector calls much easier and faster. If you click on it, you can choose the ones that you need.

Otherwise click on the plus icon in the upper right and enter a unique call name that describes the operation (e.g. read, write, update, delete, search, …).

Connector Call name

Unique name without spaces to describe the operation.

Description

Description of the operation.

 Step 3

For configuring a connector call, you have to specify input and output parameters in the following tables:
Each connector call has its own specific parameters. 

Validate

You can validate the Input and Output parameter in the backend. It validates:

• Base type against type security
• Domain type against security and restrictions
• Structures against type security and underlying property types
• Collections against type security and the underlying types / property categories

If the validation is not successful, the client is notified of all failed validations and it’s written to the Connector log or System log at the same time.

For every new Connector Call, this flag is set by default. Already existing Connector Calls do not have this checkbox flagged to guarantee the compatibility.

Parametername

The technical path or name within a rest api definition or web service description language or csv header column.

Alias

A meaningful non-technical description for the technical parameter. This wording is used in the edit mode for a user story (Process Designer) for mapping data with ui elements.

Description

Optional description of the parameter.

Constant Value

A constant value like SAP Client or company code that can’t be overwritten by any business apps. The value will be validated, so that it’s not possible to use a constant value with a wrong base type in Connector Calls and Buisness Objects.

Data Type

Assigned Simplifier data type for validating data before it gets back or from a backend system.

Step 4

After finishing the parameters, you can save the connector call settings.

_______________________________________________

Add a new Library

To add a new library click on the “+” in the right corner.

Now you can fill in the following parameter:

Angular 2 libraries

If you mark a library as “Angular 2 compatible”, you have to fill in additional configuration data in the Content Area (you don’t need a file upload for Angular 2 libraries anymore).

In this additional configuration data field, you can configure npm dependencies of your Managed Library and import custom components. With this high level configuration it is possible to include any Angular 2 specific npm package and configure vanilla Angular 2 apps.

_______________________________________________

Add a PDF Template

Add Template

To add a template, you need the following parameter:

Example for a call:

{     "name": "templatename",     "data": "SGFsbG8gV2VsdA==\",     "stylesheet: "SGFsbG8gV2VsdA==\",     "previewJson": "SGFsbG8gV2VsdA==\" }

{     "success": true }

_______________________________________________

Add an Icon to a Widget

If you want to set an icon to a Widget, use the following syntax:

sap-icon://iconName

You can find all possible Icons with the OpenUI5 Icon Explorer.

_______________________________________________

Add Metadata to the Release

With this Action Button in the Release Overview, you will be redirected to the metadata dialog.

Here you can insert additional information like requirements, compatible devices or add screenshots of the application.

The metadata will be displayed in the Marketplace, if you upload the app. You can maintain the metadata in German or English.

_______________________________________________

Add Widgets to the Screen

To fill your screen with UI elements like text fields, charts or action buttons, you can search and choose them from the widget panel on the left side:
First, search for a specific widget using the name or just browse the the list, then add the widget to the screen. The widget will appear in your content area.

_______________________________________________

Additional Requirements for Oracle Databases as Backend

On-Premise Installation

Oracle as a DB backend for the Simplifier requires some additional server settings, which are listed below. The Simplifier is currently running with MySQL 5.7 and Oracle 11g.

Database Settings within the Oracle Database:

Supported Oracle version:

Oracle Database 11g Release 11.2 – 64bit

Desired/recommended instance names (Productive and Test):

simplifierp and simplified

Required tablespaces:

simplifier 5G, Temp 1G, Undo 512 MB, Users 5MB

Oracle user and required roles and permissions:

simplifier, simplifier_np (in Prod and Test) permissions to run DDL

Database Characterset:

AL32UTF8

National Characterset:

UTF8

Default language:

German, Germany

Processes and Sessions:

Value to 1000

_______________________________________________

Administrate Templates

Templates are HTML Templates which for example can be used to send emails. With Templates you can build patterns that you can use consistently.

In our example we use one Template for an e-mail that will be sent to a new user to get a password. We use another Template in case a user has forgotten his password, so that he has the opportunity to reset the password. The Templates are arranged in the Namespace ‘system’.

Namespace Section

Namespaces are logical groupings of Templates.

Template Section

You can create and customize the Templates in HTML. With the mustache notation you can add data dynamically at runtime.
(For information about how to send the Templates go to: Business Object Script Template – Send Email).

The HTML Templatecontent looks like this:

Preview Section

The Preview Section shows live updates while editing a Template or provides a quick view when selecting a Template.

_______________________________________________

Anonymous Profile for Plugins

If you want to access plugins, you can work with anonymous users. Therefore the PluginAPI works with AnonymousAppProfile.

So only the assigned role to your Application needs the permission to use the Plugin.

Read more about roles.

_______________________________________________

App SAP Material

The App “SAP_Material_Academy” shows exemplarily how to search for SAP Material Numbers and display the Material Name and Stock Data. You can reduce the stock through “Goods Withdrawal” or reduce the quantity through “Goods Receipt”.

_______________________________________________

App SAP Technischer Platz

The App “SAP_TechnischerPlatz_Academy” enables you to search for SAP Technical Location and display Header Data with the structure of the Technical Location. You can install and remove structural Items of the Technical Location.

_______________________________________________

App Simplifier Explored

The App “Simplifier_Explored_Academy” is a feature-based mobile App, showing the native capabilities of the Simplifier running on mobile devices.

It is subdivided into individual User Stories:

_______________________________________________

Applications

The Simplifier transforms your business process into a configured business application for

• Web Portals for Desktop-Browsers (Internet Explorer, Firefox, Chrome)
• Mobile Phones and Tablets
• Wearables Devices like  Smartwatches and Glasses

We use the abbreviation “Apps” for all applications regardless of the device and user. An app should run on any device category because it is generated on common open standard technology.

Overview

By clicking on the Applications tile, you will be lead to the overview. There you will see a table with all created applications. Within this table you’ll get several information like the name of the apps, the author, default language, the version number, customization ratio, framework, and several actions.

Read how to create a new application.

_______________________________________________

Assets

To upload files like documents, images, videos, 3D models or office documents to your application, click on the assets button.

You can choose between three different options:

• Images like .PNG, .TIFF, .JPEG or .BMP Files
• Javascript for extending your application with other libraries
• Other files like .PDF Documents,  3D-Models or Media-Files (Audio, Video, etc)

To upload an image, choose it from your client via the upload button – a preview will be generated after uploading and also the path for referencing it later into an parameter of an image widget. In our screenshot the path is img/Wine.jpg.
By clicking on the red cross on the right side, you can delete the asset file.

To insert the assets into your user interface add, an image widget and write the path in the source field (src) in the Edit Area on the right.  

_______________________________________________

Assign Roles

Roles control who receives the messages. Any user who has the corresponding role and uses the Simplifier client at the time of sending a message will receive the message.

Enter the required roles in JSON notation as follows:

{
"roles": [
"<Role-1>", 
"<Role-2>", 
...
"<Role-n>"
]
}

_______________________________________________

Assigning Libraries to Apps

You can assign libraries to your application in the “UI Designer”.

Click on “Libraries” in the upper menu bar to see an overview of all the libraries that are currently used in your app.
If you click “+” you can add a library.
The icon left-handed computes all dependend libraries (of the App itself and its Widgets as well as all transitive dependend libraries).

_______________________________________________

Asynchronous Connector

You can configure asynchronous connectors in the Process Designer. The configuration works as same as with the synchronous connector.

When setting a connector to asynchronous, the assistant only offers connectors with asynchronous interfaces (Push, MQTT and OPC/UA).

The activity has two inputs “subscribe” and “unsubscribe” and one output.

_______________________________________________

Asynchronous Connector Request Json Examples

This section contains the required request data Jsons for different connectors and the description of each individual field.

The following Connectors are described with an example:

• OPC/UA Connector (Monitoring Requests)

_______________________________________________

Authentication Settings

The Authentication settings allow you to establish a connection to a LDAP or SAP system in order to sync external user to the Simplifier.

_______________________________________________

Backups

Every instance is backed up daily in the Simplifier Cloud.

Both files and a logical database backup (dump) are stored directly on the machine. These are held locally for 4 weeks. This is very useful when restoring a single Simplifier instance.
Furthermore, the Simplifier Cloud is image-based backed up every day. These backups are held for 14 days.
Should the system fail completely, we can initiate a complete restore at any time.

_______________________________________________

BROWSE Call - OPC/UA Connector

Call for BROWSE operations (The name TIA_BROWSE_ALL_VARIABLES is the arbitrary chosen name for this call)

Input Parameter

For the Browse Connector Call, you need to configure the “operationType ” and the “nodeId” (consisting of 2 parameter: identifier and namespaceIndex). Furthermore you need to define the operationTarget, a returnSet and filterSettings (optional).

operationType: Defines which operation you want to execute, in this case “BROWSE”.
Parameter Name: operations/arrayItem[0]/operationType
Constant Value: BROWSE
Data Type: String

nodeID: Defines the identification of the OPC/UA node. It is split in 2 Parameter:

• Identifier:
  Parameter Name: operations/arrayItem[0]/nodeId/identifier
  Data Type: String or Numeric
• NamespaceIndex:
  Parameter Name: operations/arrayItem[0]/nodeId/namespaceIndex
  Data Type: String
  In every namespace, each ID must be unique (it is possible to use the String “7617” and the Numeric 7167 together in one namespace)

operationTarget: You can browse references forward, backward or in both directions. Choose between the basic attributes (simple) or further ones, depending on the class (extended).
Parameter Name: operations/arrayItem[0]/operationTarget
Data Type: String
Constant Value: Choose between

• SIMPLE_ALL_CHILDREN
• SIMPLE_ALL_PARENTS
• SIMPLE_BOTH
• EXTENDED_ALL_CHILDREN
• EXTENDED_ALL_PARENTS
• EXTENDED_BOTH

returnSet:
Parameter Name: operations/arrayItem[0]/returnSet
Data Type: String
Constant Value: LIST

filterSettings (optional):

• Type:
  Parameter Name: operations/arrayItem[0]/filterSettings/filter/filterType
  Data Type: String
  Constant Value: NODE_CLASS
• Value:
  Parameter Name: operations/arrayItem[0]/filterSettings/filter/filterValue
  Data Type: String
  Constant Value: Choose between
  • DATA_TYPE
  • METHOD
  • OBJECT
  • OBJECT_TYPE
  • REFERENCE_TYPE
  • VARIABLE
  • VARIABLE_TYPE
  • VIEW
  • UNSPECIFIED

NOTE: The specific commands are NOT defined here!

Output parameters

You can return all Output Parameter like this:

Parameter Name: /
Data Type: String

If you want to get only selected Output Parameter, use the following syntax:

Parameter Name: operationsResult/[0]/browseResult/children/nodes/
Data Type: depends on the Parameter you want to be returned.

For now only the complete unformatted JSON will be returned.

_______________________________________________

Built a PDF Template

Administration

To generate a PDF and manage templates, the role “pdfPlugin” has to be assigned to your User.

Templates

You can build a PDF Template by using HTML, CSS and Mustache. A live preview is provided, so you can see changes in real time.

The rendering is executed with wkhtmltopdf, therfore every html format and feature that supports the QT Webkit render engine is working.

With every Template, a stylesheet in LESS format is generated and will be embedded automatically. You can maintain this stylesheet via the same interface as the HTML template.

The inclusion of graphics (<img src=”…”>) and additional stylesheets (<link rel=”stylesheet” href=”…”>) is also supported.
These external asserts are retrieved via the “assets” slot of the AppServer (they should be uploaded there in advance). You can refer to them in the template with a relative filename (no “http://” prefix, no path, etc.!).
Example: <img src=”image.jpg”> (if the file was uploaded as “image.jpg”).

Furthermore, you can add expressions in mustache format. These “variables” are later replaced by values from the update file to a session.

The dynamic data is retrieved as a JSON string in the key-value-store with the key: “sessiondata/$session“.
($session = the session ID that is specified for the generation)

Merging

You can combine your PDF document with other PDFs or images from the key-value store.

For this purpose you can call the list of all ressouces you want to merge with the key “merge/$session” in the key-value store. The list should correspond to a JSON-Array, where the entries of the JSON-Array are the keys of the resources to be merged. For example: [“dokument1.pdf”, “document2.pdf”, “bild.jpg”].

The binary data of the corresponding documents should be filed in the key-value store under the keys “dokument1.pdf”, “document2.pdf” and “bild.jpg”.

_______________________________________________

Business Object

The input and output mapping of Business Objects works equivalent to the mapping of Connector Calls.

After selecting the right Business Object and the predefined script template, you can map the input and output parameters.

The assistant offers all configured Business Objects that includes methods. You can search for the name of the Business Object. When selecting a Business Object, all methods are listed on the right-hand side.

_______________________________________________

Business Object Script Template - Send Email

try
 {
     var message = TOOLS.sendTemplateMail(
         JSON.stringify(
             {
                 templateNamespace: "test",
                 templateName : "demo",
                 emailCharset : "UTF-8",
                 emailMime: "text/html",
                 receiver : input.Receiver,
                 //receiverCC : ["", ""],
                 subject : "Release 51 Demo",
                 data : {
                     Release : "51" // any data you want to use in the mustache template
                 }
             }
         )
     );

           output.message = "Mail sent";
 } catch (e) {
     output.message = e.message;
     output.success = false;
 }

_______________________________________________

Business Object via Script

this.callBusinessObject(businessObjectName, method, payload, callback, showBusyIndicator, failOnError, failCallback, parametrized)

_______________________________________________

Business Objects

The Simplifier allows you to create complex integrated applications up to a high degree solely through configuration. Nevertheless, at some point in time, advanced business logic might be required, which can’t be implemented merely by configuration. This is when Business Objects come into play.

Business Objects are implemented via Javascript. This way they integrate seamlessly into Simplifier applications. They enable you to write arbitrary business logic and interact with other Simplifier artifacts like connectors, plugins or other Business Objects. They can also be shared among different applications. Although written in Javascript, Business Objects execute on the server side, keeping possibly complex and time-consuming operations away from the client.

_______________________________________________

Certificates

Our cloud infrastructure provider, T-Systems operates data networks for customers worldwide and processes data in its own data centers – data protection and data security have absolute priority. The ICT provider, therefore, has its services regularly audited by independent institutions and has itself certified that it complies with global standards and norms, for example through ISO certifications.

Here you will find an overview of the current certificates:

_______________________________________________

Change your Password

For security reasons, it is always a good idea to update your password regularly.

In order to change your password, you have to switch to the ‘Users‘ tile in the Simplifier dashboard. After that, search for the user whose password you want to change and click on the edit icon underneath ‚Actions‘.

You will be lead to the user details of the selected user. Now click on the ‘Send Password Link‘. You will receive an email with a link to change your password.

If you need help, please contact an admin.

If you’re an admin and want to change someone’s password, click on the ‚Password‘ tab in the upper left corner. Now all you have to do is enter the new password, confirm it and finally click on ‚Change Password‘.

_______________________________________________

Checklist - Simplifier onPremise Installation

Here you will find a checklist for all On Premise installations. You can check off the points when you’ve finished them. During this time, please do not reload this page.

$ docker run -v $SIMPLIFIER_DIR:/opt/simplifier/data \

-p 80:80 -p 443:443 -p 8090:8090 \

-d ––name simplifier docker.itizzimo.com/simplifier-onpremise

$ docker run -v $SIMPLIFIER_DIR:/opt/simplifier/data \

-p 80:80 -p 443:443 -p 8090:8090 \

-d ––name simplifier itizzimo/simplifier:latest

_______________________________________________

Checklist SAP SSO over SOAP

Check 1: SSO2 Check

1. Start Transaction SE80
2. Choose Type BSP Application
3. Choose SYSTEM_TEST/test_sso2.htm
4. Test/Run (F8)
   http://hostname.example.com:8000/sap(bD1kZSZjPTgwMA==)/bc/bsp/sap/system_test/test_sso2.htm
5. Check if Cookie ‚MYSAPSSO2=…‘ available

Check 2: SSO Parameter

1. Run transaction code RZ11(temporary) RZ10 ( permanent)
2. Check if the following parameter has been set
   

   login/accept_sso2_ticket	1
   login/create_sso2_ticket	2 (without certificate)
   icm/host_name_full	FQDN (e.g. hostname.example.com)

Check 3: SSO Login

1. Open transaction SA38
2. Choose report SEC_TRACE_ANALYZER

Check 4: Permissions

Every user needs the following permission object:

S_SERVICE

Troubleshooting / Common Errors & Solutions

The following section documents the most common errors with possible solutions.

Q: What should I do when HTTPS/SSL is not available?

A: If you have problems with the connection set it from SSL to None

Q: What if the WSDL Consumer has problems parsing the WSDL?

A: Manually replace the string ws_policy in the WSDL with standard

Q: How can I monitor the error log of SAP Web services?

A: The error log can be viewed with transaction “srt_util”.

Q: How can I change the SAP web service login language?

A: The standard login language is also via SAP Webservices in English. Thus, all data determinations according to e.g.: Status texts, material text ect. always return in English language.

To be able to change it to German, the following prefix must be appended to the SOAP Webservice operation URL: “?sap-language=DE”
This does NOT mean the WSDL URL!

Q: How can I call the web service from another SAP client?

A: The web service operation call must be done with the parameter?sap-client=[client] so that the system can recognize the client.

Q: What if the Simplifier does not have access to the SAP system?

A: Check the following points:

Please make sure that there is a physical connection between the Simplifer (host) instance and the system. Firewall/Ports may need to be enabled to allow communication in both directions.
The Simplifier Docker or host system must be maintained with the correct network settings for on premise installations. This includes, for example, the setting for DNS servers.

_______________________________________________

Client Validation

The Data Type of default properties in application items can now be overwritten, but only domain types with the same basic type can be used.

You can find the settings in the Property Panel of the UI Designer. The button will open a popover, which lets you define the Data Type and the validation event. If the validation is enabled (checkbox), an indicator will be displayed. You can change the valueState and valueStateText as result.

In this example, we wanted to make sure, that the Input field will be filled with the correct data, a ZIP Code. Therefore we added the validation for the predefined Datatype “ZIP” (a String with exactly 5 numbers) on the change Event.

Now, if you open the application in the preview and type in anything else than 5 numbers, the valueState of the Input field would change to “ERROR” and the valueState text “Wrong Input” would be displayed.

_______________________________________________

Client-Side Business Object API

You can access any methods of the Simplifier by using the Simplifier Object.

Connectors

Simplifier.Connector.<ConnectorName>(payload: object, successCallback: function, busyFlag?: boolean, failOnError?: boolean, errorCallback?: function): void
Simplifier.Connector.<ConnectorName>.<CallName>(payload: object, successCallback: function, busyFlag?: boolean, failOnError?: boolean, errorCallback?: function): void

Example:

var payload = {bindingName: "Binding", operationName: "MyOp", soap: {foo: "bar"}};
function onSuccess (data) { resolve(data); };
Simplifier.Connector.MySoap(payload, onSuccess, true, true);
Simplifier.Connector.MySoap.myCall(payload, onSuccess, true, false, function () { console.log("something went wrong"); });

Business Objects

 Simplifier.BusinessObject.<BOName>.<MethodName>(payload: object, successCallback: function, busyFlag?: boolean, failOnError?: boolean, errorCallback?: function, parametrized?: boolean = true): void

Example:

var payload = {leftOperand: 3, "operation": "add", rightOperand: 4};
function onSuccess (data) { resolve(data); };
Simplifier.BusinessObject.OtherBO.someMethod(payload, onSuccess, true, false, function () { console.log("something went wrong"); }, true);

Client-side Business Objects

Simplifier.ClientsideBusinessObject.<CSBOName>.<FunctionName>(payload: object, successCallback: function, busyFlag?: boolean, failOnError?: boolean, errorCallback?: function): void
Simplifier.CurrentClientsideBusinessObject.<FunctionName>(payload: object, successCallback: function, busyFlag?: boolean, failOnError?: boolean, errorCallback?: function): void

Example:

var payload = {leftOperand: 3, "operation": "add", rightOperand: 4};
function onSuccess (data) { resolve(data); };
Simplifier.ClientsideBusinessObject.OtherBO.someMethod(payload, onSuccess, true, false, function () { console.log("something went wrong"); });
Simplifier.CurrentClientsideBusinessObject.someMethod(null, onSuccess, true, false, function () { console.log("something went wrong"); });

Plugins

Simplifier.Plugin.<PluginName>.<SlotName>(payload: object, successCallback: function, busyFlag?: boolean, failOnError?: boolean, errorCallback?: function): void

Example:

var payload = {name: ""};
function onSuccess (data) { resolve(data); };
Simplifier.Plugin.contentRepoPlugin.listRepos(null, onSuccess);
Simplifier.Plugin.contentRepoPlugin.createRepo(payload, onSuccess);

CryptoJS

var sMySecretKey = "secret";
var oCrypted = CryptoJS.AES.encrypt("dontStealMyData", sMySecretKey);
output.result = CryptoJS.AES.decrypt(oCrypted, sMySecretKey).toString(CryptoJS.enc.Utf8)

Take also a look at crypto-js.

_______________________________________________

Code Designer

The Code Designer is a web based development environment that can be used to write source code like in a normal IDE. Entered Code will be highlighted according to the programming language used (e.g. Javascript, HTML or CSS).

On the left side there is a Document tree view where all the files of an application are displayed in a structured hierarchy. New files can be created, uploaded or moved within the tree view.

All opened files are displayed in tabs and can thus be edited easily by switching tabs. The search function is used to search through code by keyword. Also change can be undone or redone with the Undo / Redo Buttons.

If you add or change code here, it can not be displayed in the edit mode of a user story (Process Designer). The connection is only unidirectional. Click on the “Download App” button to get the code file.

_______________________________________________

Collection Type

Collections represents multiple results of Structs. For example a databank request may deliver a list of addresses from numerous people.

To create a new Collection Type click on the “+” button.

You can define a unique collection name and a description.

By clicking on “Parenttype” a new pop up opens, where you can choose the parenttype from.
NOTE: A Collection can only reference to a Struct or single Domain Types.

After you have clicked on apply, the parenttype will be used.

_______________________________________________

Components of Applications

A Simplifier application usually contains the following configurable components:

_______________________________________________

Condition

Conditions give you the possibility to make the process flow dependent on the evaluation of certain expressions.

In such an expression, you can compare Autofields, Variables, an actual value of a widget or a given constant with each other and decide upon the result, if the process continues one way or the other. Or you might decide to continue the process only, if one condition holds and omit the alternative, which in turn results in a process stop at this stage.

If you double click on the shape, it will add a new condition. Alternatively you can click on the plus icon on the right.

Let’s see an example:

The process pane contains a condition, that’s executed after the login button got pressed. The condition compares a widget value (value property of widget InputUsername) with the fixed constant value “admin”. This means, that the expression evaluates to true, if the input value of field username equals “admin”. In this case, the process flow leads to a navigation to screen “BusinessScreen”. If the username does not equal “admin”, the user will be navigated to the Screen “PrivateScreen”.

Comparing a Widget

Selecting a widget for comparison is guided via a three-step dialog. It asks you to select the screen in the first step, then one of the widgets on this screen and finally the property of the widget that you like to read for the comparison:

Comparing a Constant

Defining a constant value for comparison is even easier: you specify the data type via a selection in a dropdown box and set the value in the field below.

Comparing a Variable

If you want to compare a Variable, every existing one in the Data Workbench will be shown within the list. You can switch between the tabs Base Types, Domain Types, Structs an Collections.

Comparing an Autofield

And you can select every generated Autofield for comparision as well.

_______________________________________________

Connector

A typical example for a Data Object is a previously defined connector call. An assistant offers all configured connectors that owns connector calls. You can search for the connector name or even the connector type. If you select a connector, all calls are listed on the right side.

Choose the required Connector and the Call you want to execute.

You have the possibility to configure if the UI is blocked by the busy indicator, or can configure which element on your screen should be blocked by it.

If you want to assign a connector call to a Data Object, you have to define the sources for the connector input (the request) and the destination for its output (the response). This is called the “Input Mapping” and “Output Mapping”:

Clicking one of these two buttons opens a new popup which allows you to connect widgets with the input or output attributes of a connector call. Independent of whether you’re defining the input or output mapping, you’ll always find the mapping sources in the left pane and the destinations on the right. If you define the input mapping, for example, you’ll find the list of widgets in the left pane and the available connector call request parameters on the right. Within the output mapping dialog, the widgets are on the right pane, as they are the destination of the received data. Below is an example for the input mapping screen:

_______________________________________________

Connector Call Specific Parameters

The user interface for configuring a connector call is generic, thus it looks the same for all kinds of underlying types of connectors. Having the same interface for all kinds of connector calls is very convenient. But one drawback of this approach is, that some connectors require fixed parameters to be set, in order to work properly. This section tells you more about these details.

You can declare parameters of Connectors as optional.

When declaring a parameter as non optional, the validation of the call will fail if the parameter is not provided.

Data Type Selector

If you click on the data type field, a selector opens.

_______________________________________________

Connector Call via Script

In order to execute a connector call please use this code snippet:

this.callConnectorCall(connectorName, connectorCallName, payload, callback, showBusyIndicator, failOnError, failCallback)

_______________________________________________

Connector Call Wizard

In the Connector Call overview you can find the assistant in the top right corner.

The assistant will open and helps you to create the Connector Call.

*Note: At the moment the Wizard is only available for SOAP and SQL Connectors.

SOAP Connector Wizard

In the first step you can select the operation you want to execute.

In the second step you can edit the name and description of the Connector Call.

SQL Connector Wizard

With the SQL Wizard it’s easy to configure new Connector Calls based on SQL Connectors for MySQL and Oracle.

When opening the Wizard, all tables available for the schema are displayed.

You can search for your Table, and then select under “Actions” whether you want to select all columns (right icon) or only certain ones (left icon).

If you only want to select certain ones, click on the left icon. A new popup opens in which you can select the desired columns. Then click OK.

After you have selected the desired tables and, if necessary, their columns, you can edit the connector calls by clicking on “Edit Connector Calls”.

When you have edited the calls, click on “Create connectorcalls”.

_______________________________________________

Connector Calls

Connectors define the connection (entry point) to an external system. Given such a connection, you might send several different requests to the connected system. We call one such concrete pair of request / response a “connector call”. In order to use a connector call in the edit mode of a user story (Process Designer), you must create at least one connector call for each connector.

_______________________________________________

Connector Details

In step three, you can add data to your Connector.
Each Connector has specific details that depend on the properties of the communication protocol.

_______________________________________________

Connector Types

You can choose between different Connector Types. A Connector Type represents the technical protocol.

_______________________________________________

Connector via Script

this.callConnector(connectorName, payload, callback, showBusyIndicator, failOnError, failCallback)

_______________________________________________

Connectors

Connectors are used to retrieve data from backend systems and third-party sources and write back changed data into them. They can be used by a unique name within configured business applications or business objects. It represents the systems part of the simplifier.

_______________________________________________

Convert XML to/from JSON

You can use this template to convert XML to/from JSON.

Convert XML to JSON

Simplifier.Util.xml2json(xml: string): string

Parses an XML string, converts it to JSON and returns the representing JSON string.

try{

    var convertedJson = Simplifier.Util.xml2json("<xml></xml>");

    

    output.json = convertedJson;

    output.message = "Convertion successful";

    output.success = true;

} catch (e) {

    output.message = e.message;

    output.success = false;

}

Convert JSON to XML

Simplifier.Util.json2xml(json: string): string

Parses a JSON string, converts it to XML and returns the representing XML string.

try{

    var convertedXML = Simplifier.Util.json2xml(JSON.stringify({attribute: "value"}));

    

    output.xml = convertedXML;

    output.message = "Convertion successful";

    output.success = true;

} catch (e) {

    output.message = e.message;

    output.success = false;

}

_______________________________________________

Copy Business Objects

To copy a Business Object, just click in the Overview of Business Objects on the ‘Copy Business Object’ Button.

After you have clicked on it, a pop-up appears in which you can specify the new name of the Business Object. Then click on ‘Save’.

Now the Business Object has been copied. All included Connectors, Plugins and other Business Objects as well as the Script Templates are available in the copy.

_______________________________________________

Copy Connector Calls

You can copy a connector call within a connector in the connector call overview by clicking the appropriate copy button.

By clicking the button a new pop up opens in which you can specify the name of the copied connector call. The default value is the name of the copied connector call added _copy.

Once you have assigned a name, click on the save button. Your connector call has been copied with all input and output parameters.

_______________________________________________

Copy Data Types

You can copy any Data Type of the Simplifier. The copy will have all attributes/fields and any tags given to the copied template.

Click on the copy icon and a new pop-up will appear.

By default, “_Copy” is added to the current Data Type Name. However, you can also assign a new name. Click ‘Save’ and the copy has been created.

_______________________________________________

Copy your Widgets

You can copy Widgets and insert them on a different Screen or even another Application.

_______________________________________________

Create a New Application

Please set up the following checkpoints before you create an app:

• All connector calls should be configured in case of using backend interfaces
• You should know the right technology for your use-case before you build app

To create a new application, click on the Applications module. Then click on the “+” button on the top right to create a new business app:

The following dialog will appear:

Fill out the necessary fields analog to the table below:

After the app creation you can configure it with the following tabs:

	UI Designer	Configure the User-Interface and mark all necessary events to design your workflow.
	Process Dashboard	Define your workflow with simple visual events and actions.
	Code Designer	Add additional javascript files to your app and extend it in web-based integrated development environment.

_______________________________________________

Create an individual Transport

Enter tile “Transports” on the Simplifier Dashboard and click on Transportcollection to define a new Transport or edit an existing one. This leads you to the overview page, which lists all existing Transports:

To create a new Transport, or edit an existing one, make sure you’ve got the “Transport Creation” permission associated to one of your roles. Click on “+” on in the upper right corner to create a new Transport from scratch or press the edit button beside one of your existing one to edit it. This leads you to a new page which allows you to define all Transport artifacts:

The upper part of the screen allows you to enter a name for your Transport.

The lower part of the screen is dedicated to the selection of the artifacts which shall be part of your Transport. The left pane lists all available features (Apps, Connectors, Roles, Business Objects, Datatypes, Widgets & Libraries) and allows you to search for specific ones. Ideally, the features of your app have an identical name part, so you can easily find all belonging features through the search bar. You can filter the list by clicking on “Name” or “Feature” and select e.g. only Widgets.

Select an artifact by checking the checkbox beside it. After clicking the right arrow, all selected artifacts are immediately listed in the right pane. (Attention: The “Application” feature represents only the cover of your app and its standard Widgets, not all your used features like e.g. customized Widgets, Business Objects or Connectors!

When you’re done, press the “Save” button in the upper right corner or “Cancel”, if you want to omit your changes.

_______________________________________________

Create an OpenUI5 Widget

If you choose to create a new OpenUi5 Widget, you have to take a look at the constructor details in its API reference.

Here you can find the OpenUi5 API of all Widgets and a description when to use them.

Start

Let’s create a mobile version of a Panel. For starters search new sap.m.Panel in the API reference.
You will see the supported settings, in this case: Properties, Aggregations and Events.

• Properties describe the different attributes of an element (e.g. width or height).
• Aggregations describe which other elements the Widget could contain (e.g. a panel consists of a header & info toolbar and content).
  Depending on the Control that is displayed in the API, you can use every or just specific Controls (e.g. sap.ui.core.Control vs sap.m.Toolbar)
• Events describe the possible direct interactions for the user (e.g. expand the panel).

Step 1

For the first step name your Widget, write a short description and choose a category in the Widget tab.

In addition you’ve got now the possibility to add custom tags to the widget. You can search and filter for widget tags in the search field of the widget overview list and in the widget search field of the UI designer.

Step 2

Click on the OpenUI5 tab to fill out the specific parameters.
The Widget Type has to be the same as the UI5 control name. In this case: sap.m.Panel

Step 3

Fill in the template for the Widget. It represents a blueprint of the Widget which can be used by the Simplifier.
The OpenUI5 templates are written in JSON with Mustache placeholder syntax.

The Simplifier supports three different types:

• String: “{{&placeholderName}}”
• Boolean: {{placeholderName}}
• Aggregation: [{{#placeholderName}}”{{&}}”,{{/placeholderName}}]

The placeholderName will be used to declare properties, events, etc.. It is advisable to use the OpenUI5 names.
For SAP Controls (e.g. sap.m.BackgroundDesign) you can use the „String“ Data Type.

Step 4

All attributes that are declared with a mustache value in the template, have to be declared in the properties / events / etc. area below as well, so you can work with them in the UI Designer later in the process. You can use constant values instead of mustache e.g. if you don‘t want a property to be editable.

• Properties:
  Fill in the name (your template placeholderName), a description (optional), the default value and the data type (as written in the API reference). If a property should be translatable, you have to check it here.
• Events:
  Simply put the name (again the template placeholderName) on the list.
• Aggregation:
  Transfer your template placeholderName and the content type (API reference).
  If your aggregation shall be able to contain more than just one control, check the “Multiple” checkbox.

Step 5

If all properties are listed, you can set the Default Binding-Property which is the prioritized widget property used in the edit mode of a user story (Process Designer).

End

After hitting the “Save” button, you’ve successfully created a Panel Widget for your application.

_______________________________________________

Create and Edit Transports

There are two different options to create a Transport:

• Adding an individual Transport via the “Transportcollection” tile

• Releasing your app in the UI Designer

_______________________________________________

Create and Manage Connectors

Create a Connector

To create a new connector, click on the plus icon on the upper right corner. It opens a new pop up where you can enter the required and optional information. 

Connector Type

Login Method

You can add or select the login method for the specific backend systems. To select an existing login method, click on the corresponding field. It opens a drop down where you can select it.

If you want to create a new one, you can choose between using UserCredentials and SingleSignOn.

If you’d like to get an overview on your existing login methods and manage them, click on the “Logins” tab in the connector overview.

Connector Details

On the right side you can add data to your connector. Each connector has specific details that depend on the properties of the communication protocol. Read more on the following pages.

Copy a Connector

You can also copy an existing Connector. The complete configuration of the Connector, including its Connector Calls, is copied and created with the duplicate.

Usage of Connector

You can see which applications are using the Connector. For that click on the appropriate icon within the Connector overview underneath ‘Actions’.

It opens a new popup that displays all applications that uses the connector:

_______________________________________________

Create client-side Business Object

Business Objects are managed under the module “Business Objects”. The main screen lists all existing Business Objects in table form. On the top left you can switch between server-side and client-side Business Objects. 

Press “+” in the upper right corner to create a new one from scratch. This fires up the following screen:

First, choose a name for your client-side Business Object, e.g. “MyNewBusinessObject” and set a description (optional). Add some tags, so you can search in the overviews and the UI Dsigner by the tags.

You may then select any Connector, Plugin, Server-side Business Object, Client-side Business Object or managed libraries on the left side. It opens a dialog where you can select it. Each selected item appears in the list below, from where you might also remove it again by clicking the delete icon underneath ‘Actions’.

When you’re done, leave the screen by hitting the “Save” button and return to the overview page. Your new Business Object appears in the table.

Usage of Business Objects

You can see which applications or interfaces are using the Business Object. For that click on the appropriate icon within the Business Object overview underneath ‘Actions’.

It opens a new popup that displays all used applications:

Accessing input and output parameters of client-side Business Objects

You can access your input parameters via oPayload.<myInputParameter>.

To use the output parameters you have to return an object that has your parameters as properties. E.g.

return {
      myOutputParameter : myOutputValue
}

_______________________________________________

Create server-side Business Objects

Business Objects are managed under the module “Business Objects”. The main screen lists all existing Business Objects in table form. On the top left you can switch between server-side and client-side Business Objects. 

Press “+” in the upper right corner to create a new one from scratch. This fires up the following screen:

First, choose a name for your Business Object, e.g. “MyNewBusinessObject” and set a description (optional). Add some tags, so you can search in the overviews and the UI Dsigner by the tags.

You may then select any Connector, Plugin or other Business Object you want to refer on the left side. It opens a dialog where you can select it. Each selected item appears in the list below, from where you might also remove it again by clicking the delete icon underneath ‚Actions‘.

When you’re done, leave the screen by hitting the “Save” button and return to the overview page. Your new Business Object appears in the table.

Usage of Business Objects

You can see which applications or interfaces are using the Business Object. For that click on the appropriate icon within the Business Object overview underneath ‘Actions’.

It opens a new popup that displays all used applications:

_______________________________________________

CSS Editor

To design your application, you can use CSS for styling with standard web cascading style sheets.

If you would like to learn more about CSS, take a look at the tutorials of the w3 schools.

After changing css properties you have to reload your application in the preview tab

To Do so please use the following shortcuts

_______________________________________________

CSV Connector Calls

Go to CSV Connector Details for more information about the CSV Connector.

A CSV Connector can be configured in 3 different modes:

* READ: The connector can only read from the specified CSV file path, no write operations are permitted.

* WRITE: The connector can only write to the CSV file, but not read from it.

* READ/WRITE: The connector can read from the file and also write to it.

Currently, only the READ operation is implemented!

READ

The CSV Connector Call for a READ operation requires 2 Input parameters: “action” and “resultmode“.

To execute a read operation, call the Connector with the parameter “action” and the constant value “read“.

Reading Connectors get the result as JSON array of arrays by default. There can be definied two “resultmode“parameter:

• “columnnumber” returns an array of JSON objects, where the key is “col0”, “col1”, … “colX” for the column.
• “columnname” returns an array of JSON objects where the key is the String taken from the header row (only available if `headerInFirstLine` is true – see CSV Connector Details).

The Connector returns everything if you use “/” as Output parameter.

_______________________________________________

CSV Connector Details

Path

Filepath and Filename to local .CSV File that should be written, relative to the current working directory of the application server. It is recommended to give an absolute path, so it doesn’t matter which directory is set as “Current Working Directory” from the appserver start script.

Delimiter

Delimiter of the columns that separates the values like comma or semicolon. This must be exactly one character, more than one character is not supported by the library.
**In order to use the tabulator character, the expression ‘\t’ can be used in the Admin UI.** If more than one character is specified, all but the first character will be discarded.

Charset

Character encoding used to read/write the file. If a charset is used that is unknown to the application server JVM, all read/write operations will fail.

Mode

Operation Mode of the Connector, either READ, WRITE or READ/WRITE – the CSV Connector can currently only read the referenced csv file.

Header

Activate the checkbox if the CSV File has a header in the first row.

Quote all Items

Activate the checkbox if all items should be quoted in terms of strings (“). Otherwise only values which contain the delimiter are put in quotes. This setting is irgnored when reading.

Go to CSV Connector Calls to configure the corresponding Calls.

_______________________________________________

Custom Extension of Simplifier SAP Connector

It’s also possible to extend our interface with implicit enhancements

• at the end of all the programs (Includes, Reports, Function pool, Module pool, etc.), after the last statement
• at the beginning and end of all FORM subroutines
• at the end of all Function Modules
• at the end of all visibility areas (public, protected and private) of local class

This feature is official documented on the sap wiki.

The second option is to use BADIS to enhance our Namespace.

Minimum Requirements for the Simplifier SAP Connector

To install the Simplifier SAP Connector, your SAP system should meet at least the following requirements:

• SAP ERP 6.0 EHP 7
• SAP ABAP 7.4+
• SAP Base 7.40
• SAP IS-U Release 6.17 EHP 7 (optional only for IS-U interface)

_______________________________________________

Data Centers of Simplifier Cloud

The Simplifier Cloud is hosted in data centers of T-Systems Germany.

The locations of the twin-core data centers are:

[vc_gmaps link=”#E-8_JTNDaWZyYW1lJTIwc3JjJTNEJTIyaHR0cHMlM0ElMkYlMkZ3d3cuZ29vZ2xlLmNvbSUyRm1hcHMlMkZkJTJGdSUyRjAlMkZlbWJlZCUzRm1pZCUzRDEwYWxiVVlCVTh1S0szRUhYa3lDb1JyeXltZDNXenRtdiUyMiUyMHdpZHRoJTNEJTIyMzgwJTIyJTIwaGVpZ2h0JTNEJTIyNDgwJTIyJTNFJTNDJTJGaWZyYW1lJTNF”]

_______________________________________________

Data Object

Data Objects represent data sources and destinations, which can be triggered for execution. You can choose either a predefined Connector (you can activate it to asychronous) or Business Object. 

Validation of mandatory Parameters

All configured parameters has an indicator if it’s mandatory.

If you haven’t map all input parameters of a data object that has been marked as mandatory, the following warning will appear:

_______________________________________________

Data Types

The module “Data Types” is the central way to define different types of data, structures and collection of Data Types and their validation rules.

Data Types are a way to ensure data are sent and received in the right type format to and from the backend systems.
With this feature, you can define data definitions to validate your data with client and server-side validation to prevent security issues and backend saving problems due to wrong data formats or hacker attacks.

Data Types can be assigned to widgets and connector calls to validate input and output data.

There are six Base Data Types defined in the Simplifier:

With the “Data Types” tile, you are able to enhance the Base Types and define your own logic.
The new Data Types are split into three different types:

• Domain types
• Structs
• Collections

You can assign tags to Data Types to find them easily in the searchbar. Already existing tags are suggested including tags of widgets.

_______________________________________________

Data Workbench

Within the Data Workbench, you can administer global Events, Variables and Auto Fields that you want to use cross-functional in the User Stories.

*PLEASE NOTE*

The Data Workbench is no longer available for applications using AngularJS.
If you build your application with Angular 2, there are no limitations.

_______________________________________________

Delete a PDF Template

{     "name": "templatename" }

{     "success": true }

_______________________________________________

Deployment & Installation Instructions

A Simplifier application can be deployed in different ways. You can deploy to your local machine for development and testing, you can deploy to the Simplifier cloud, Cloud Foundry-based platforms, Azure, AWS, SAP Cloud, or a server you configured yourself.

Cloud installations are hosted and maintained by iTiZZiMO. Each instance is reachable via a unique DNS name:

https://<instance-name>.simplifier.io

On-premise installations are hosted by our customers, on their own infrastructure. This scheme is especially useful if the Simplifier shall be integrated into a closed network infrastructure.

 Checklist for Installation

For Installation of the Simplifier, the following persons and things are required:

• IT Security Officer
• Systemowner regarding Backend Interfacing
• Firewall Administrators
• Reverse Proxy Administrator
• IT Administrators
• SSL Certficates for HTTPS

Use the following checkpoints for an successful installation

Checkpoint	Description
	System-Requirements are clear
	Domain-Name for Development, QA and Productive Systems are clear
	SSL Certifcates for all 3 Instances is available
	Firewallports 443 and 587  are open
	Backendsystem is reachable via Supported Protocols

_______________________________________________

Device Condition

The Simplifier is able to recognize the device type that is using the application, so you can assign different functionalities to it, e.g. different designed login screens for mobile or wearable devices.

At first you need to create a new autofield type with the autofield type “Device” and the characteristic “Device Type”. How to create autofields, you can see here.

Within the Process Designer, you can refer to this autofield using a condition. Select the corresponding auto field and assign it to a constant (string).

Choose between:

• desktop
• phone
• smartglass
• tablet
• watch

Please pay attention to lower case!

_______________________________________________

Docker Hub

The Simplifier is also available on Docker Hub.

Short Instructions

Create the directory which will host all external user-specific data:
$ mkdir -p /home/simplifier/data
$ export SIMPLIFIER_DIR=”/home/simplifier/data”

Install SSL certificates:
$ mkdir -p $SIMPLIFIER_DIR/certs
$ cp <certificate.pem> SIMPLIFIER_DIR/certs/default.crt
$ cp <keyfile.pem> SIMPLIFIER_DIR/certs/default.key

Run docker:
Alternative 1: with SSL/Certificates
$ docker run -d -v $SIMPLIFIER_DIR:/opt/simplifier/data \
-p 80:80 -p 443:443 -p 8090:8090  \
––name=simplifier itizzimo/simplifier

Alternative 2: without SSL/Certificates
$ docker run -d -v $SIMPLIFIER_DIR:/opt/simplifier/data \
-p 80:8080 -p 8090:8091 \
––name=simplifier itizzimo/simplifier

_______________________________________________

Docker Installation

Get Docker CE

Referenced to the official Docker instructions.

Note: This installation instructions is based on the example of the operating system Ubuntu 16.04 LTS.

SET UP THE REPOSITORY

Update the apt package index:

$ sudo apt-get update

Install packages to allow apt to use a repository over HTTPS:

$ sudo apt-get install \

    apt-transport-https \

    ca-certificates \

    curl \

    software-properties-common

Add Docker’s official GPG key:

$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

Verify that you now have the key with the fingerprint 9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88, by searching for the last 8 characters of the fingerprint.

$ sudo apt-key fingerprint 0EBFCD88

pub   4096R/0EBFCD88 2017-02-22

      Key fingerprint = 9DC8 5822 9FC7 DD38 854A  E2D8 8D81 803C 0EBF CD88

uid                  Docker Release (CE deb) <docker@docker.com>

sub   4096R/F273FCD8 2017-02-22

Use the following command to set up the stable repository. You always need the stable repository, even if you want to install builds from the edge or test repositories as well. To add the edge or test repository, add the word edge or test (or both) after the word stable in the commands below.

Note: The lsb_release -cs sub-command below returns the name of your Ubuntu distribution, such as xenial. Sometimes, in a distribution like Linux Mint, you might have to change $(lsb_release -cs) to your parent Ubuntu distribution. For example, if you are using Linux Mint Rafaela, you could use trusty.

amd64:

$ sudo add-apt-repository \

   "deb [arch=amd64] https://download.docker.com/linux/ubuntu \

   $(lsb_release -cs) \

   stable"

INSTALL DOCKER CE

Update the apt package index:

$ sudo apt-get update

Install the latest version of Docker CE:

$ sudo apt-get install docker-ce

_______________________________________________

Docker on Mac

Install Docker for Mac

Docker for Mac is the Community Edition (CE) of Docker for MacOS. To download Docker for Mac, head to Docker Store.

Download from Docker Store

What to know before you install

README FIRST for Docker Toolbox and Docker Machine users

If you are already running Docker on your machine, first read Docker for Mac vs. Docker Toolbox to understand the impact of this installation on your existing setup, how to set your environment for Docker for Mac, and how the two products can coexist.

• Relationship to Docker Machine: Installing Docker for Mac does not affect machines you created with Docker Machine. You have the option to copy containers and images from your local default machine (if one exists) to the new Docker for Mac HyperKitVM. When you are running Docker for Mac, you do not need Docker Machine nodes running at all locally (or anywhere else). With Docker for Mac, you have a new, native virtualization system running (HyperKit) which takes the place of the VirtualBox system. To learn more, see Docker for Mac vs. Docker Toolbox.
  • Mac hardware must be a 2010 or newer model, with Intel’s hardware support for memory management unit (MMU) virtualization, including Extended Page Tables (EPT) and Unrestricted Mode. You can check to see if your machine has this support by running the following command in a terminal: sysctl kern.hv_support
  • macOS El Capitan 10.11 and newer macOS releases are supported. We recommend upgrading to the latest version of macOS.
  • At least 4GB of RAM
  • VirtualBox prior to version 4.3.30 must NOT be installed (it is incompatible with Docker for Mac). If you have a newer version of VirtualBox installed, it’s fine.System Requirements: Docker for Mac launches only if all of these requirements are met.

Note: If your system does not satisfy these requirements, you can install Docker Toolbox, which uses Oracle VirtualBox instead of HyperKit.

• What the install includes: The installation provides Docker Engine, Docker CLI client, Docker Compose, Docker Machine, and Kitematic.

Install and run Docker for Mac

1. Double-click Docker.dmg to open the installer, then drag Moby the whale to the Applications folder.
2. Double-click Docker.app in the Applications folder to start Docker. (In the example below, the Applications folder is in “grid” view mode.)You are prompted to authorize Docker.app with your system password after you launch it. Privileged access is needed to install networking components and links to the Docker apps.The whale in the top status bar indicates that Docker is running, and accessible from a terminal.If you just installed the app, you also get a success message with suggested next steps and a link to this documentation. Click the whale () in the status bar to dismiss this popup.
3. Click the whale () to get Preferences and other options.
4. Select About Docker to verify that you have the latest version.

Congratulations! You are up and running with Docker for Mac.

_______________________________________________

Docker on Ubuntu / Debian

Get Docker CE

Referenced to the official Docker instructions.

Note: This installation instructions is based on the example of the operating system Ubuntu 16.04 LTS.

SET UP THE REPOSITORY

Update the apt package index:

$ sudo apt-get update

Install packages to allow apt to use a repository over HTTPS:

$ sudo apt-get install \

    apt-transport-https \

    ca-certificates \

    curl \

    software-properties-common

Add Docker’s official GPG key:

$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

Verify that you now have the key with the fingerprint 9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88, by searching for the last 8 characters of the fingerprint.

$ sudo apt-key fingerprint 0EBFCD88

pub   4096R/0EBFCD88 2017-02-22

      Key fingerprint = 9DC8 5822 9FC7 DD38 854A  E2D8 8D81 803C 0EBF CD88

uid                  Docker Release (CE deb) <docker@docker.com>

sub   4096R/F273FCD8 2017-02-22

Use the following command to set up the stable repository. You always need the stable repository, even if you want to install builds from the edge or test repositories as well. To add the edge or test repository, add the word edge or test (or both) after the word stable in the commands below.

Note: The lsb_release -cs sub-command below returns the name of your Ubuntu distribution, such as xenial. Sometimes, in a distribution like Linux Mint, you might have to change $(lsb_release -cs) to your parent Ubuntu distribution. For example, if you are using Linux Mint Rafaela, you could use trusty.

amd64:

$ sudo add-apt-repository \

   "deb [arch=amd64] https://download.docker.com/linux/ubuntu \

   $(lsb_release -cs) \

   stable"

INSTALL DOCKER CE

Update the apt package index:

$ sudo apt-get update

Install the latest version of Docker CE:

$ sudo apt-get install docker-ce

_______________________________________________

Docker on Windows 10

Install Docker for Windows

Docker for Windows is the Community Edition (CE) of Docker for Microsoft Windows. To download Docker for Windows, head to Docker Store.

Download from Docker Store

What to know before you install

If your system does not meet the requirements to run Docker for Windows, you can install Docker Toolbox, which uses Oracle Virtual Box instead of Hyper-V.

• README FIRST for Docker Toolbox and Docker Machine users: Docker for Windows requires Microsoft Hyper-V to run. The Docker for Windows installer enables Hyper-V for you, if needed, and restart your machine. After Hyper-V is enabled, VirtualBox no longer works, but any VirtualBox VM images remain. VirtualBox VMs created with docker-machine (including the defaultone typically created during Toolbox install) no longer start. These VMs cannot be used side-by-side with Docker for Windows. However, you can still use docker-machine to manage remote VMs.
• Virtualization must be enabled in BIOS and CPU SLAT-capable. Typically, virtualization is enabled by default. This is different from having Hyper-V enabled. For more detail see Virtualization must be enabled in Troubleshooting.
• The current version of Docker for Windows runs on 64bit Windows 10 Pro, Enterprise and Education (1607 Anniversary Update, Build 14393 or later).
• Containers and images created with Docker for Windows are shared between all user accounts on machines where it is installed. This is because all Windows accounts use the same VM to build and run containers.
• Nested virtualization scenarios, such as running Docker for Windows on a VMWare or Parallels instance, might work, but come with no guarantees. For more information, see Running Docker for Windows in nested virtualization scenarios
• What the Docker for Windows install includes: The installation provides Docker Engine, Docker CLI client, Docker Compose, Docker Machine, and Kitematic.

About Windows containers

Looking for information on using Windows containers?

• Switch between Windows and Linux containers describes the Linux / Windows containers toggle in Docker for Windows and points you to the tutorial mentioned above.
• Getting Started with Windows Containers (Lab) provides a tutorial on how to set up and run Windows containers on Windows 10 or with Windows Server 2016. It shows you how to use a MusicStore application with Windows containers.
• Docker Container Platform for Windows Server 2016 articles and blog posts on the Docker website

Install Docker for Windows desktop app

1. Double-click Docker for Windows Installer.exe to run the installer.If you haven’t already downloaded the installer (Docker for Windows Installer.exe), you can get it from download.docker.com. It typically downloads to your Downloads folder, or you can run it from the recent downloads bar at the bottom of your web browser.
2. Follow the install wizard to accept the license, authorize the installer, and proceed with the install.You are asked to authorize Docker.app with your system password during the install process. Privileged access is needed to install networking components, links to the Docker apps, and manage the Hyper-V VMs.
3. Click Finish on the setup complete dialog to launch Docker.

Start Docker for Windows

Docker does not start automatically after installation. To start it, search for Docker, select Docker for Windows in the search results, and click it (or hit Enter).

When the whale in the status bar stays steady, Docker is up-and-running, and accessible from any terminal window.

If the whale is hidden in the Notifications area, click the up arrow on the taskbar to show it. To learn more, see Docker Settings.

If you just installed the app, you also get a popup success message with suggested next steps, and a link to this documentation.

When initialization is complete, select About Docker from the notification area icon to verify that you have the latest version.

Congratulations! You are up and running with Docker for Windows.

_______________________________________________

Domain Type

A Domain type represents a single Data Type that inherits from a Base Type like String, Integer, Float, Date etc. and can include different properties.
For example a ZIP Code is an inherited type of string with the property of a maximum of 5 chars length.

To create a new Domain Type click on the “+” button.

Enter a unique Name for the Domain Type and an optional Description.
Also select a Parenttype to inherit from by clicking on the appropriate field.

In the area below you can set the properties of your Data Type:

Min 

Minimum length of a String, minimum number of a range, earliest date of a date range.

Max

Maximum length of a String, maximum number range, latest date of a date range.

RegEx

Regular expression to validate this Domain Type – for more information see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp.

Possible Values

Simple JSON Array of Strings repesenting literals of chosen Base Type.

Nullable

If activated, this value can be empty (null).

_______________________________________________

Don't overwrite data

The options „Don’t overwrite“ and „Overwrite“ are going to import the data to your system.
By choosing “Don’t overwrite”, only new features are uploaded. Every feature with the same name like an existing one is skipped.

_______________________________________________

Downloads

This section offers various Downloads as examples on how to use different features of the Simplifier.

If you have a problem building your App, you can import a fitting Transport to your Simplifier instance and reproduce the steps.

_______________________________________________

DQP System

For each step in the development and update process of the Simplifier, an independent instance should be used.

• Development
• Quality Assurance
• Productive

Here we would like to give you an example for deploying a DQP system on three virtual machines.

Deployment and Integration Workflow D-Q-P

• Development of an app on the DEV instance
• Transport to the QA instance
• Testing the app on the QA instance
• Transport to the Productive instance

_______________________________________________

Dry run

A “Dry run” analyzes the content of the file and displays a list of all features.
It does not import the data so you can simply test how the transport would work out.

_______________________________________________

Edit a PDF Template

{     "name": "templatename",     "data": "SGFsbG8gV2VsdA==\",     "stylesheet: "SGFsbG8gV2VsdA==\",     "previewJson": "SGFsbG8gV2VsdA==\" }

{     "success": true }

_______________________________________________

Email Connector Call

The Email Connector Call requires 3 input parameters to be defined:

All Data Types should be set as String.

There are 3 optional parameters that can be configured as well:

_______________________________________________

Email Connector Details

SMTP host

Hostname of SMTP Server

SMPT port

Port of SMTP server

SMTP authentication

If enabled, the client attempt to authenticate the user using the AUTH command. Default to false.

SMTP StartTLS

If activated, it enables the use of the STARTTLS command (if supported by the server) to switch the connection to a TLS-protected connection before issuing any login commands. Note that an appropriate trust store must configured, so that the client will trust the server’s certificate. Default to false.

_______________________________________________

Encode/Decode Base64

Encode Base64

Encodes a string to a base64 string.

Simplifier.Util.encodeBase64(string: string): string

Example:

try{

    var encoded = Simplifier.Util.encodeBase64("String to encode");
    

    output.b64 = encodedD64;

    output.message = "Encoding successful";

    output.success = true;

} catch (e) {

    output.message = e.message;

    output.success = false;

}

Decode Base64

Decodes a base64 string.

Simplifier.Util.decodeBase64(json: string): string

Example:

try{

    var decoded = Simplifier.Util.decodeBase64(encoded);

    

    output.b64 = decodedBase64;

    output.message = "Decoding successful";

    output.success = true;

} catch (e) {

    output.message = e.message;

    output.success = false;

}

_______________________________________________

Enumeration in Widget Properties

You can maintain enumeration for Widget properties. Enumerated properties can only hold the defined values and will be displayed as selection in the UI Designer.

In order to define the enumerations you have to add them in an Array notation to the default value of the property. It is not necessary to set the values in quotes.

Example

There are different predefined types of buttons in OpenUI5. The properties can be maintained as a list in the widget mask. In our example, we look at all different button types in the OpenUi5 API Reference and transfer them into the widget edit mask with the appropriate syntax: [typ1, typ2].

Result in the UI Designer

_______________________________________________

Event

Each workflow in the Process Designer starts with an event. Click on the Event element under “Activities” on the left pane and drag & drop it into the drawing area.

If you double click on the shape of the activity, the event selection assistant opens. You can also open it by clicking right underneath “Subscribe event” / “Publish event”, an Event selection assistant will be open. It guides you to your required Event. When subscribing an Event, you can select Events from three categories: Screens (Widget Events/Screen Events), Custom Events and System Events. Each category is sorted and searchable.

If you want to use your Event in the User Story you are currently working in, select one of the Events under the tab “Subscribe Events”.

The assistant considers every Event managed by the application.

It is only possible to publish Custom Events. The Assistant is aware of this and only displays this category when you define your publishing activity.

If you want to make an Event usable in another Stories, create a new Custom Event under the tab “Publish Event”. Then you can subscribe to it in another User Story. A shorcut for creating Custom Events can be found in the top right-hand corner.

Example:

You have a process in User Story 1 that contains a condition to check if an Input field is filled out after clicking on a “Login” Button. Afterwards, the User should be navigated forward to the next Screen.

Imagine you have an extra User Story exclusively for the whole Navigation of your App. So naturally you want the end of the Event from User Story 1 (the Navigation) displayed in User Story 2.

Therefore we published the new custom Event “LoginButton” in User Story 1 and subscribed to it in User Story 2.

User Story 1:

User Story 2:

Published Events can be maintained in the Data Workbench.

_______________________________________________

Example Cordova Plugin for Mobile Action

As an example, we would like to show a pdf document as a native mobile action after clicking on a button in a business application.

Step 1

Add a button to your screen in the UI Designer.

Step 2

Edit your user story and add the activity “Event” and “Script” to your working area. Assign your button (press) to the Event and click on “Script” to edit the JavaScript code.

Step 3

To view a pdf document, you need the Cordova Plugin “File Transfer” and “Document Viewer“. Open their documentation and head down to “3. Using the Plugin”. Here you can find the necessary JavaScript Code. Add it to your Script.

In this example:

var options = {
 title: "Title",
 documentView : {
 closeLabel : "close"
 },
 navigationView : {
 closeLabel : "close"
 },
 email : {
 enabled : false
 },
 print : {
 enabled : false
 },
 openWith : {
 enabled : false
 },
 bookmarks : {
 enabled : false
 },
 search : {
 enabled : false
 },
 autoClose: {
 onPause : false
 }
}

function onPossible(){
 window.console.log('document can be shown');
 //e.g. track document usage
}

function onMissingApp(appId, installer)
{
 if(confirm("Do you want to install the free PDF Viewer App "
 + appId + " for Android?"))
 {
 installer();
 }
}

function onImpossible(){
 window.console.log('document cannot be shown');
 //e.g. track document usage
}

function onError(error){
 window.console.log(error);
 alert("Sorry! Cannot show document.");
}

function onShow(){
 window.console.log('document shown');
 //e.g. track document usage
 
 //reset baseurl
 document.getElementsByTagName('base')[0].href = temp;
}

function onClose(){
 window.console.log('document closed');
 //e.g. remove temp files
}

function onMissingApp(id, installer)
{
 if(confirm("Do you want to install the free PDF Viewer App "
 + appId + " for Android?"))
 {
 console.log("trigger installer");
 }
}

var fileTransfer = new FileTransfer();
var uri = encodeURI("https://projects.simplifier.io/appDirect/Xenon_OPC_UA_Consolidated/data/Parametrierung_Dosiereinheit.pdf");
var fileURL = cordova.file.cacheDirectory + "asdf.pdf"

//save current base
var temp = document.getElementsByTagName('base')[0].href;

//download file
fileTransfer.download(
 uri,
 fileURL,
 function(entry) {
 console.log("download complete: " + entry.toURL());
 
 //set base to local to make it work
 console.log("resetting base");
 document.getElementsByTagName('base')[0].href = "";
 
 cordova.plugins.SitewaertsDocumentViewer.canViewDocument(
 entry.toURL(), 'application/pdf', options, onPossible, onMissingApp, onImpossible, onError);
 
 cordova.plugins.SitewaertsDocumentViewer.viewDocument(
 entry.toURL(), 'application/pdf', options, onShow, onClose, onMissingApp, onError);
 
 },
 function(error) {
 console.log("download error source " + error.source);
 console.log("download error target " + error.target);
 console.log("download error code" + error.code);
 },
 false
);

Step 4

Save and deploy the app.

_______________________________________________

Execution Log

You can use the execution log to trace the execution of e.g. connectors.

The following type of entries are logged:

_______________________________________________

Fetch a PDF Template

{     "name": "templatename" }

{     "success": true,
 "value": { "template": "SGFsbG8gV2VsdA==\", "stylesheet: "SGFsbG8gV2VsdA==\" "previewJson": "SGFsbG8gV2VsdA==\" } }

_______________________________________________

Filter

The Logs & Monitoring Tile uses all search features of the backend (i.e. pagination or filtering).

On the left-hand side you can set filters.

You can choose between the following filters.

In the logs on the right-hand side you can click a detail button, which will open further information.

_______________________________________________

FQDN

A fully qualified domain name (FQDN) is sometimes also referred to as an absolute domain name.

Example on our Simplifier cloud:

Example for onpremise installation:

_______________________________________________

Frontend Exercise - Mobile SAP Purchase Orders

This Transport provides all components you need to do the Frontend Exercise course.

It contains:

• the Connector “MyGo_SAP_RFC_Connector”
• the Data Types:
  • POITEM
  • ES_RETURN_BOM
  • POItemList

_______________________________________________

General Instructions

Here you will find general instructions about Simplifier deployment:

• Docker Installation
• Reverse Proxy Requirements
• Additional Requirements for Oracle Databases as Backend
• Docker Hub

_______________________________________________

General Requirements for On-Premise-Installations

We support you with on-premise installations of the Simplifier on one of his own instances. To do that, we deliver a prepared Docker image to you. The image comes pre-configured and contains all the required components, including the Simplifier server in its most recent version.

The target instance must fulfill the following requirements:

• At least 8 GB RAM minimum, 12 GB recommended
• 64 BIT x86, server processor with 4 cores and at least 2 GHz per core
• At least 20 GB of free hard disk space
• Open ports: 80 (TCP),  443 (TCP) , 8090 (TCP)
• SMTP relay (port 587)
• SSL Certificate for encrypted connection
• Operating system:
  • Linux
    • In general, the Docker engine can run on all Linux versions with kernel version> = 3.10, but for the versions below, there are “official” releases.
    • If you are uncertain about the compatibility go to the Docker website.
      Tested Distributions:
      • Ubuntu
      • CentOS
      • Debian
      • Fedora
      • RHEL (Redhat Enterprise Linux) und SUSE Enterprise are officially supported only by paid docker variants
  • Mac
    • Install Docker for Mac
      Note: Our docker containers, respectively the database server, require a file system which can be case-sensitive under MacOS. Therefore, it may be necessary to create a seperate volume for the user data which is configured with the option “-v” when the container is started.

      The Simplifier MacOS Deployment is not recommend for production use, because of the limited support for container

• • Windows
    Install Docker for Windows
    • Windows 10 Professional
    • Windows Server 2016 (Please download the “Docker Edge” version on the website.)
      The runtime is given, but not as a Windows Service. The Docker Containers only stay up and running in a locked user session.

      The Simplifier Windows Deployment is not recommend for production use, because of the limited support for container

Depending on what kind of maintenance service level has been defined, we might need access to your machine in order to install updates or analyze logs. In this case, the target machine should fulfill the following additional requirements:

• Your server is connected to the Internet
• SSH daemon is installed and running (preferable on port 22)

_______________________________________________

Global Auto Fields

Auto Fields are automatically computed / filled fields. You can use them e.g. if you want to greet the user who is logged in with his/ her actual name or load the version number.

You can declare Autofields from five categories

• Application
• User
• URL
• Geolocation
• Device

How to use Auto Fields

You can use Auto Fields within a Data Object. In this example, we created an Auto Field that automatically gets your user name. Then we mapped it with the Input Parameter “userName” of a preconfigured Business Object.

We configured some more Auto Fields like “applicationVersion” or 2 URL Parameter. The result is shown below:

At first, you can see the former way of typing in the information by hand. On the second Screen, we used the Auto Fields and you get the information automatically, simply by clicking on the button.

_______________________________________________

Global Events

Global Events can be imagined as tunnels which connect different User Stories or processes. If you publish an Event, you open the entrance to the tunnel and by subscribing to this particular Event, you create the exit of the tunnel. This enables you to jump between the Stories and helps you to have a clearly laid out working space.

Go to Events for an example use of global Events.

_______________________________________________

Global Variables

You can use global Variables as a container to buffer data. E.g. if a Connector returns a lot of data and you would like to use some of it later in your work process, you can save the parameter as Variables and map them later.

You can reference Variables in Data Objects as In- or Output parameter. To do so, drag a Variable (that you’ve created previously in the Data Workbench) from the toolbar in the mapping dialog.

_______________________________________________

Glossar

Here you will find general and Simplifier specific abbreviations, technical terms and their meaning.

_______________________________________________

Group Overview

A group contains several users and could be used for workflow logic in business apps like informing a team via email or push notification about a certain event or task.

Details View of a Group

To create a new group you have to specify a unique name and an optional description e.g. for a team or special task force group.

To add users, click into the “Add User to Group” Field and search for specific usernames. Mark several users and click OK to add them.

_______________________________________________

Handling & Updating an On-Premise Installation

Docker Basic Commands

Start the Simplifier container:

$ docker start simplifier

Stop the Simplifier container:

$ docker stop simplifier

Restart the Simplifier container:

$ docker restart simplifier

Create a backup of the complete Simplifier data directory, e.g.

$ docker stop simplifier

$ tar cvzf simplifier_backup.tar.gz /home/simplifier

Updating

In case of updates, we will prepare a new docker image for you, preserving your personal settings. Please download the image to a temporary directory of your choice (e.g. /tmp) and change into the directory. Finally unpack and load it, as described in steps 3-4 in the installation instruction.

To perform the update, proceed as follows:

1. Stop the container and remove it from Docker. Take care NOT to remove your data directory /home/simplifier/data !
2. Perform the following commands in order:

$ docker stop simplifier

$ docker rm simplifier

$ docker run ––name simplifier {additional options as in step 6 before}

_______________________________________________

Hardware

_______________________________________________

How to Customize Screens for Different Devices

You can design your screens individually for different devices, e.g. a login screen that is optimized for mobile phones and one for smartwatches.

Simply select as screen property the devices you want to address and e.g. create a second screen for the alternatives.

Now you can filter your screens and work precisely on one at a time.

_______________________________________________

How to rename your Screens

To rename screens, select it and change the ID within the properties section.

Use the Description field to comment and annotate the screen. This helps to identify the purpose of the screen later on.

_______________________________________________

How to use Widgets in the UI Designer

In the follwing sub-sites, you can get some information on how to use Widgets in the UI Designer, e.g. adding an Icon or changing the order of the Widgets.

_______________________________________________

Implement logic to your Business Object

The logic of a Business Object is implemented via Script Templates. Each Business Object can hold as many Script Templates as wanted. Click on the “Script” Icon to add some Templates.

Creating a Script Template involves writing a method via JavaScript and editing parameters. In the Script Editor you can code logic that can be called in the edit mode of a user story (Process Designer).

The content corresponds to the inner body of a Javascript function. In other words: your main code block must not be wrapped into a separate function definition, but rests on the top level context. It’s nevertheless possible to define sub-functions on top of your main code block.

It’s best practice to wrap your main code block in a try-catch-block to handle possible errors.

Let’s have a typical hello world example:

In the toolbar above you have several possibilities: undo, redo, search, search and replace, format code and settings.

This example reads a name which is provided to the Business Object as an input parameter, compiles it into a greeting message and writes the result to the output.

Take a look at the try-catch-block surrounding the main code section:
If no error occurs, the upper part of the code inside the “try”-section will execute and return the greeting message and output.success = true. However, if any error occurs, the function will jump down into the “catch” section and return output.success = false and assign any details of the failure to attribute output.error.

In order to use the Script Template correctly, you have to add the same Input and Output parameters you used in the payload. Those parameters will be shown in the mapping dialogs in the edit mode of a user story (Process Designer). Please note the correspondent handling of in- and output through the (JSON) objects “input” and “output”. Both of them may carry arbitrary attributes.

In this example the object “input” carries the attribute:

• input.name  to read the inserted name.

The “output” object carries the attributes:

• output.message to send a greeting message.
• output.success (true/false) to indicate whether the Script Template executed successfully.
• output.error to hold the root cause of an error in case of failure.

Validate

You can validate the Input and Output parameter in the backend. It validates:

• Base type against type security
• Domain type against security and restrictions
• Structures against type security and underlying property types
• Collections against type security and the underlying types / property categories

If the validation is not successful, the client is notified of all failed validations and it’s written to the Business Object log or System log at the same time.

For every new Business Object, this flag is set by default. Already existing Business Objects do not have this checkbox flagged to guarantee the compatibility.

*NOTE* You have the possibility to declare parameters as optional. When declaring a parameter as non optional, the validation will fail if the parameter is not provided.

_______________________________________________

Import Transport

To import a file to your Simplifier instance click on the “Import Transport” tile. You will be forwarded to an import overview page.

Choose your file you want to import. If you select ‘Dry Run’,  it simulates the import.

If the transport works correctly, you can import it with the option ‘Overwrite’. When certain artifacts already exist and you do not select ‘Overwrite’, only the new artifacts are transported.

_______________________________________________

Installation PDF Plugin

Configuration

To use the pdf Plugin, you have to configure it first.
Copy the file “settings.conf.dist” from the directory “plugins/pdfPlugin/src/main/resources”, save it as “settings.conf” and adjust it as follows:

In order to start the conversion, you need to install the program wkhtmltopdf on your operation system. The path to the wkhtmltopdf executable must be stated in the “settings.conf” file. Furthermore you need two folders, one to file your template and the other for the temporary data during the conversion. You can either use relative or absolute paths for the folders.

For example:

pdfPlugin {
     storageDir = "templates"
     tempDir = "tmp"
     wkhtmltopdf = "C:/Program Files/wkhtmltopdf/bin/wkhtmltopdf.exe"
}

....

NOTE:

If you use wkhtmltopdf on a Linux without the X11 Server, the error  “wkhtmltopdf: cannot connect to X server” may occur.

In this case you need to install the program “xvfb” via the package manager to simulate the X11 server.

Create a wrapper (e.g. /usr/local/bin/wkhtmltopdf-xvfb) for the “wkhtmltopdf” program and write the path in the PdfPlugin Config.

<#!/bin/bash>
xvfb-run --server-args="-screen 0, 1024x768x24"/usr/bin/wkhtmltopdf$*

_______________________________________________

Installing an On-Premise Image

We always prepare an all-in-one Docker image for our customers which contains all required components.

Given a target machine that matches the requirements described in the previous chapter, the installation is quite easy:

1. Create the directory which will host all external user-specific data:

$ mkdir -p /opt/simplifier/data

$ export SIMPLIFIER_DIR="/opt/simplifier/data"

2. Copy the downloaded file with ending .tar.gz to a temporary directory on the target machine, e.g. /tmp and cd to this directory.

$ wget -O <filename>.tar.gz

3. Unpack the file in place:

$ tar xzvf <filename>.tar.gz

You will get two files: one readme.txt and the docker image with the ending .tar.

4. Inside the directory which contains the unpacked file, run the following commands as root- (super-) user:

$ docker load -i <imagefile.tar>

5. Install SSL certificates:

$ mkdir -p $SIMPLIFIER_DIR/certs

$ cp <certificate.crt> $SIMPLIFIER_DIR/certs/default.crt

$ cp <keyfile.key> $SIMPLIFIER_DIR/certs/default.key

6. Run docker image:

Alternative 1: with SSL/Certificates

$ docker run ––name simplifier -v $SIMPLIFIER_DIR:/opt/simplifier/data \

-p 80:80 -p 443:443 -p 8090:8090 \

-d docker.itizzimo.com/simplifier-onpremise

Alternative 2: without SSL/Certificates

$ docker run ––name simplifier -v $SIMPLIFIER_DIR:/opt/simplifier/data \

-p 80:8080 -p 8090:8091 \

-d docker.itizzimo.com/simplifier-onpremise

7. In case you want to install from DockerHub, use itizzimo/simplifier as image suffix. The docker engine automatically downloads the image from DockerHub and you can skip step 2., 3. and 4.

Example without SSL/Certificates:

$ docker run ––name simplifier -v $SIMPLIFIER_DIR:/opt/simplifier/data \

-p 80:8080 -p 8090:8091 \

-d itizzimo/simplifier 

8. Open your browser

Now use your browser at your Client Computer to access http(s)://<IP> or <FQDN>/UserInterface. The Simplifier will prompt a license dialog. After pasting that license
you can start configuring Apps in the AdminUI.

_______________________________________________

Integration of external Libraries

Sometimes it is necessary to add an extra library to your app, e.g. if you want to display some special charts. You can upload and manage those external libraries under the “Libraries” tab in the Application tile.

If you want to know how to implement them into your application, go to “Assigning Libraries To Apps”

In the list overview you get information about:

• the name
• the version info
• the vendor
• if it is compatible to Angular JS, Angular 2 or UI5
• if it was set as a default for Angular JS, Angular 2 or UI5
• if the library is referenced in any application

Standard Equipment

The Simplifier provides the following libraries by default:

_______________________________________________

Integration of Libraries - addAfterInitHandler

addAfterInitHandler

_______________________________________________

Integration of Libraries - addBeforeInitHandler

addBeforeInitHandler

_______________________________________________

Integration of Libraries - addScript

To integrate the library with a js code snippet, use the following parameter:

addScript(ScriptPath, Name, Dependencies)

It is important to ensure that all scripts specified under “dependencies” are either integrated into the same library, or a dependency is set on the library in which the script is integrated.

_______________________________________________

Integration of Libraries - addStyle

To integrate the library with a js code snippet, use the following parameter:

addSyle

_______________________________________________

Iterator

An iterator is an object that sequentially passes data structures. It respectively returns the following element and determines if there are another elements following.

With the Iterator Activity you iterate over a variable. It has two output ports: each and after.

The Iterator selection helper can be accessed by opening the mapping dialog. The mapping dialog can also be opened by double clicking on the shape.

You can drag and drop the parameter in the drawing area in the middle. By double clicking on the parameter you can select the collection you want to iterate.

The mapping dialog is aware of its type and offers only collection variables that are defined in the app.

By opening the Mapping Dialog you can drag and drop the element on the left and on the right in the middle. By double clicking on it, you find all paramter/variables that can be mapped listed in a pop up.

_______________________________________________

Jobs

Jobs are server side executed and recurring tasks which use Business Objects as logic. They can be found by clicking on the “Jobs” tile on the Dashboard.

They are used to automate Business Objects. Commands can be defined and will be executed by the Simplifier on a periodic basis. You may schedule the jobs in order to trigger them without further user intervention.

The red and green icons within the overview indicate whether the job is active. The red icons signify that it’s inactive and the green icons signify that it’s active.

To create a new job, you have to name it and set an interval after which the job is called in repeatedly. Selecting the Business Object and the function provides the job with functionality. Furthermore you can choose the user who should execute the job (in case he has all permissions required). The active time zone on the server applies to all dates and time settings. You can choose between the 5 following intervals:

Interval

It’s an recurring interval at which the job is executed in the format <hh>:<mm>:<ss>. If the new execution overlaps with a previous run, it’s only started after it has been completed and after a further interval.

One Time

With this you can set an actual date <dd>.<MM>.<yyyy> and time <hh>:<mm>:<ss>.

If the selected time is in the past, the job will not be executed!

Daily

You can set a daily time in the format: <hour>:<minute>:<second>

Weekly

If you select this interval, it will be repeated every week. Set it in <hour>:<minute>:<second> and the appropriate day(s).

Monthly

Set this interval if you want that it’s repeated monthly. Set it in <hour>:<minute>:<second> and the day(s) within this month.

If the selected day doesn’t occur in this month, e.g. the 30th February, the job will not be executed in this month.

_______________________________________________

Language

Applications can be localized easily by adding language files (.po-format) to the application. A fallback language has to be defined. At default the language will be set according to user’s environment, browser or device language. 

For the translation of the individual applications, .po files are used in the Simplifier. Those can be viewed, downloaded and uploaded via the Language tab in the UI Designer.

To create a new translation file, you can download a template from this overview by clicking on the corresponding button.

The downloaded file can be edited in the text editor of your choice (e.g. Notepad ++).

Important: translatable values must be flagged within a widget in order for them to appear in the default language file!

In this template, all values marked as translatable in the widgets used are listed and can be translated into the target language.

This file can then be added via the Plus icon. You have to select the target language and the file you want to edit.

If the desired language is not available, please contact your administrator, as these are maintained in the server settings.

To change the language at runtime, the following script must be inserted in the Process Designer: sap.ui.getCore().getConfiguration().setLanguage(“en”), where “en” can be replaced by the desired abbreviation.

To start an application with a specific language, the URL of the following query parameters can be added:

?sap-language=en

_______________________________________________

LDAP

Using LDAP:

You can test the connection by inserting a Username and Password.

_______________________________________________

Libraries

You can assign different libraries to your application and get an overview on their dependencies.
Go to “Integration of external Libraries” for more details.

_______________________________________________

List of Plugins

The Simplifier comes with the following plugins:

You can find more plugins on the Marketplace.

_______________________________________________

List your PDF Templates

List Templates

To list your templates, you need the following parameter:

{     "success": true,     "value": [         "templatename1",         "templatename2",         "templatename3"     ] }

_______________________________________________

Locally

You can install the Docker engine on your local machine and start the Simplifier Docker for development and testing.

The Docker Engine runs on

• Windows 10 Pro
• Mac OS
• Linux

To see how to start the Simplifier, click here.

_______________________________________________

Logging Write Connector Details

Choose the Connector Path:

How to use a Logging Connector in a REST-Client

You can choose between READ and WRITE.

Write Logging Connector Handler

{
   "connectorName": "WriteLoggingConnectorHandler",
   "json": {
             "msg": "Test Log Konnektor umgeschrieben",
             "logLvl": "debug",
             "logGroup": "pickIt",
             "deviceMac": "",
             "timestamp": 1425293416
   }
 }

Read Logging Connector Handler

{
   "connectorName": "ReadLoggingConnectorHandler",
   "json": {
             "logGroup": "pickIt",
             "logLvl": "debug"
   }
 }

_______________________________________________

Logic

Currently the Logic shape is divided into Condition, Iterator and Script.

_______________________________________________

Logs & Monitoring

The error log is the central logging and monitoring area where all data-streams and errors are logged and saved.
You can display all data of a specific User by using the search bar.

_______________________________________________

Manage Screens

Each process step can be configured as a screen.  A screen represents one single user interface page and can contain several widgets.

In the screen section you can do the following actions:

	Copy Screen	Copy a screen and paste it into the actual or a different application.
	Paste Screen	Paste the previously copied screen into the current or a different application.
	Edit Screen	Activate the edit mode to change screen order or delete screens.
	Add Screen	Add a new screen to the actual application.

_______________________________________________

Mapping Collections

Collections represent multiple results of Structs. For example a databank request may deliver a list of addresses from numerous people and you can map them to the equivalent Widget within a Data Object.

The Input Mapping

Unfortunately, the input mapping of collections is not yet possible. Nevertheless, you can use the “Script” tile and map your data via code.

There is a general pattern you can follow and adapt it to your specific data. To map data to your table, you must have a predefined Connector with at least one Connector Call.
Now click on the Script tile  and edit the code.

Step 1

Build an object.

Step 2

Add payload to your object. If the input parameter of your Connector Call are filled in with an “Alias”, you can add them as keys to your object.
Otherwise, you need an escape function. Example:

payload[escape("soap/_-ITIZ_-OBJ_BUS2012_UPDATE/IT_PO_ITEMS(1)/QUANTITY")] = "X"

Step 3

Add a global function call with the following Parameters:

1. Parameter: Connector name
2. Parameter: Connector Call name
3. Parameter: Keys you added above (payload)
4. Parameter: Success function
5. -7. Parameter: Error function, showBusy Indicator and error message

The Output Mapping

The output mapping of a Data Object to table, a list or a select Widget can be easily done in the Process Designer.

Click on “Output Mapping” and add the output parameter (on the left) and your table widget (on the right) to the screen. Double click on each to select the items.
Now map the equivalent items together via drag & drop.

_______________________________________________

Mapping Structs

Structs describe a package of Domain Types. For example the Struct “address” contains different Domain Types like Name, Street, City, ZIP Code, etc.

You can map Structs as Input and Output parameter within your Data Object or when using a UI Action.

Example:

In the example below, we want to use a Business Object that needs the information first name, last name, street and city as Input parameter. Prior to our work in the edit mode of the user story (Process Designer), we have created the Struct Data Type “Person” that contains several Domain Types like “Firstname” and another Struct which is called “Address”.

Within the Input Mapping of our Business Object, we can assign the Input fields with the equivalent data to the Struct “Person” that the Business Object needs.

By double-clicking on the Struct you can choose exactly which parameter you want to select.

Navigate higher or deeper in the Struct by clicking on the arrows (e.g. to select the Domain Type “Street” within the Struct “Address”).

_______________________________________________

Mark Widgets as deprecated

You can mark widgets as deprecated to prevent them from being displayed within the UI Designer.

For that you have to go back to the application overview and switch to the widgets tab. Search for the appropriate widget and edit it. All you have to do now is to activate the toggle ‘Deprecated’ of the widget and click on save.

If deprecated is active, the Widget will no longer be available on the left side of the UI Designer.

Deprecated widgets that were used before they were marked as deprecated, will still be shown within the application content. The application will also still be saved and deployed without issues or warnings and runs as before.

_______________________________________________

Marketplace

The marketplace module is central to the Simplifier Experience and Workflow. It does not only provide a variety of applications ready to import to your own account, but also any other type of module content such as Connectors, Virtual Connector packages, Business Objects, custom widgets and more.

To add any type of content to your own account, browse the marketplace and click “request” to send us an e-mail with all the information we need so we can provide the content to you.

In the future, this feature will be automated, so you can add content with one click.

_______________________________________________

Mobile Action

The Mobile Action Element enables you to use mobile features within the application.

Drag and drop the activity “Mobile Action” underneath “Action” into the drawing area.

Currently, there are 14 different actions implemented in the Simplifier. Use the Input/Output Mapping to define the source for the input (request) and the destination for its output (response).

Capture Image

Determine how many pictures should be taken.

Scan Barcode

Set the format of the code you want to scan, the orientation of the camera and write a text in the prompt property.

Vibrate

Define how many miliseconds the mobile device should vibrate.

Scan Meter

For the output mapping you can use the following parameter:

Play Video

By providing the mobile action a path to a video, it will play the video in a full screen mode.

*NOTE: Please use this mobile action with caution. Some devices don’t support this feature.

Play Audio

The mobile action Play Audio just needs an audio file path.

Show Notification

This mobile action will trigger a native notification.

So the Notification will be displayed on your mobile device.

Text to Speech

With this mobile action you can specify a text to be read out, as well as the output language. You can choose between English (US) and German (DE).

Acquire GPS

The mobile action GPS need to be initialized at first. It’s recommend to do this in a screen onInit function.

When it’s initialized, you can access the longitude and latitude by the Auto Field type Geolocation. For that you need to open the mapping dialog of the UI Action. Then you can drag the auto field in the middle and by double clicking on it you can select the longitude/latitude/. Then connect it with the appropriate widget.

Show Toast

This mobile action will show a native toast, with a constant or by using the input mapping. You can specify the duration how long the toast should be displayed (Short or Long) and the position (Top, Center or Bottom).

Screen Orientation

You can set and lock the screen orientation of the mobile device. Possible values are Landscape, Portrait, Landscape (Primary), Landscape (Secondary), Portrait (Primary), Portrait (Secondary) and Unlock.

The current screen orientation can be accessed by a new characteristic of the Device Auto Field.

Light

With this mobile action, your mobile device can toggle light.

Background Mode

If the background mode is enabled, JavaScript will be executed even if the app is running in the background or the display is locked.

Read the subpages to use other mobile actions.

_______________________________________________

Mobile Action for WebRTC Calls

General infos

Plugin to provide WebRTC P2P functionality via Intel’s WebRTC SDK.

Intel WebRTC SDK Version: 3.4

Platforms:

• Android (4.0.4+ – x86, armV7)
• iOS (8+)

Cordova: 6+

When the local user connects to a remote user, this plugin overlays the cordova webview to show local and/or remote media streams.

General event object description

{
  "action": "<action>", //see "Possible Actions"
  "message": "<String>", //some message depending on action and success
}

Possible Actions

Active Actions

Actions triggered by local user

• INIT – takes stun/turn-, userconfig and initializes peer connection
• LOGIN – login to peerserver
• LOGOUT – logout from peerserver
• INVITE – inite some user
• HANGUP – peerconnection to remote user disconnected
• PUBLISH – a/v media published to remote user
• UNPUBLISH – a/v media unpublished
• SWITCH_CAMERA – switch camera front <-> back
• SEND_DATA – send data to remote user
• SCALE_VIEW – view got scaled
• SWITCH_SPEAKER – switching from internal to external speaker
• FULLSCREEN – view has been set to fullscreen
• START_SHARESCREEN – Started sharing/streaming screen content
• STOP_SHARESCREEN – stopped screen sharing

Passive Actions

Actions triggered by server/remote user/network

• ONINVITED – remote user invited local user
• ONACCEPTED – remote user accepted invitation from local user
• ONDENIED – remote user denied invitation from local user
• ONDATARECEIVED – remote user sent date to local user
• ONCHATSTOPPED – connection to remote user stopped
• ONCHATSTARTED – connection to remote user initialized
• ONDISCONNECTED – local user got disconnected from remote server
• ONSTREAMADDED – remote user published a/m media to local user

Cordova API

init

Initializes view, connects to server.

runTimeSuccessCallback / runTimeErrorCallback: is being used to provide a callback interface during plugin runtime

If the plugin has already been initialized, the plugin just attaches the runtime callbacks to regain context.

IntelWebRTC.init(config, runTimeSuccessCallback, runTimeErrorCallback);

logout

if connected to peer it closes the connector, disconnects from Server, removes view components

IntelWebRTC.logout();

invite

connect to desired peer

IntelWebRTC.invite("peerid", scopedSuccessCB, scopedErrorCB);

publish

publishes audio/video to connected peer (is automatically called when peerconnection is established)

IntelWebRTC.publish(scopedSuccessCB, scopedErrorCB);

unpublish

stops sending audio/video to connected peer

IntelWebRTC.unpublish(scopedSuccessCB, scopedErrorCB);

hangup

disconnects from currently connected peer

IntelWebRTC.hangup(scopedSuccessCB, scopedErrorCB);

switchcamera

cycles through cameras

IntelWebRTC.switchCamera(scopedSuccessCB, scopedErrorCB);

sendData

sends a string to connected peer

IntelWebRTC.sendData("",scopedSuccessCB, scopedErrorCB);

scaleView

scales and aligns view to given parameters

IntelWebRTC.scaleView(0.5, "top_left", scopedSuccessCB, scopedErrorCB);

fullscreen

sets callUI to fullscreen

IntelWebRTC.fullscreen(scopedSuccessCB, scopedErrorCB);

startShareScreen

starts screen sharing

IntelWebRTC.startShareScreen(scopedSuccessCB, scopedErrorCB);

stopShareScreen

stops screen sharing

IntelWebRTC.stopShareScreen(scopedSuccessCB, scopedErrorCB);

Examples

var config = {
               "connectionConfig": {
                 "username": "paul",
                 "server": "https://simplifier-dev.itizzimo.com:8090"
               },
               "iceConfig": [
                 {
                   "url": "stun:turn.itizzimo.com:3478"
                 },
                 {
                   "url": "stun:turn.itizzimo.com:3479"
                 },
                 {
                   "url": "stun:turn.itizzimo.com:5349"
                 },
                 {
                   "url": "stun:turn.itizzimo.com:5350"
                 },
                 {
                   "url": "turn:turn.itizzimo.com:3478?transport=tcp",
                   "username": "admin",
                   "password": "admin"
                 },
                 {
                   "url": "turn:turn.itizzimo.com:3478?transport=udp",
                   "username": "admin",
                   "password": "admin"
                 },
                 {
                   "url": "turn:turn.itizzimo.com:3479?transport=tcp",
                   "username": "admin",
                   "password": "admin"
                 },
                 {
                   "url": "turn:turn.itizzimo.com:3479?transport=udp",
                   "username": "admin",
                   "password": "admin"
                 },
                 {
                   "url": "turn:turn.itizzimo.com:5349?transport=tcp",
                   "username": "admin",
                   "password": "admin"
                 },
                 {
                   "url": "turn:turn.itizzimo.com:5349?transport=udp",
                   "username": "admin",
                   "password": "admin"
                 },
                 {
                   "url": "turn:turn.itizzimo.com:5350?transport=tcp",
                   "username": "admin",
                   "password": "admin"
                 },
                 {
                   "url": "turn:turn.itizzimo.com:5350?transport=udp",
                   "username": "admin",
                   "password": "admin"
                 }
               ],
               "viewConfig": {
                 "scalingFactor": 0.3,
                 "gravity": "bottom_right"
               },
               "mediaConfig": {
                 "maxWidth": 640,
                 "maxHeight": 480,
                 "cameraDialog": true,
                 "preferFrontCamera": false,
                 "maxFps": 30,
                 "maxVideoBandwidth": 5000,
                 "maxAudioBandwidth": 200,
                 "videoCodec": "H264"
               },
               "debug": {
                 "local": {
                   "fps": false,
                   "bitrate": false,
                   "audiolevels": false
                 },
                 "remote": {
                   "fps": false,
                   "bitrate": false,
                   "audiolevels": false
                 }
               }
             };


var runtimeSuccessCallback = function(event){
    console.log("Success: " + event);
}

var runtimeErrorCallback = function(event){
    console.warn("Error: " + event);
}

//initialize plugin
IntelWebRTC.init(config, runtimeSuccessCallback, runtimeErrorCallback);

Success: successCallback ->  {"action":"INIT","message":"initialized"}

Success : successCallback -> {"action":"LOGIN","message":"stresstest2"}

//socket could not connect
Error : errorCallback -> {"action":"LOGIN","message":"com.intel.webrtc.base.WoogeenException: io.socket.engineio.client.EngineIOException: websocket error","success":false}

//socket rejected (e. g. user not valid) - Logout needs to be called to reinitialize connection with new credentials
Error: errorCallback -> {"action":"LOGIN","message":"com.intel.webrtc.p2p.WoogeenP2PException: Socket.IO reports connect to signaling server failed.","success":false}

//initialized twice
Error: errorCallback -> {"action":"INIT","message":"already initialized","success":false}
    

Invite

Invite some user which is also connected to peerserver

IntelWebRTC.invite('<username>');

Success: {"action":"INVITE","message":"stresstest4"}
Success: {"action":"ONACCEPTED","message":"stresstest4"}
Success: {"action":"ONCHATSTARTED","message":"stresstest4"}

Error: {"action":"INVITE","message":"com.intel.webrtc.p2p.WoogeenP2PException: Target user is unreachable.","success":false}

Logout

IntelWebRTC.logout(function(success){console.log(success)}, function(error){console.log(error)});

Event Samples

Login

Initiator: IntelWebRTC::init

Success : successCallback -> {"message":"connected","action":"LOGIN"}

Error : errorCallback: -> {"message":"connected","success":false,"action":"LOGIN"}

Disconnected

Initiator: Device is offline / Connection to server lost Triggers on each connection retry (every ~5 Seconds)

Error: errorCallback: ->  {"action":"ONDISCONNECTED","message":""}

When connection is established again:

Success: successCallback -> {"action":"LOGIN","message":"stresstest2"}

Sample Eventlog

//login initialized
IntelWebRTC.init(config, runtimeSuccessCallback, runtimeErrorCallback);
//initialization success
Success: {"action":"INIT","message":"initialized"}
//initial view parameters added to layout
Success: {"action":"SCALE_VIEW","message":""}
//login success
Success: {"action":"LOGIN","message":"stresstest2"}
//remote invited local user
Success: {"action":"ONINVITED","message":"stresstest3"}
//local user accepted
Success: {"action":"ONCHATSTARTED","message":"stresstest3"}
//local user published stream (happends auto on ONCHATSTARTED)
Success: {"action":"PUBLISH","message":"stresstest3"}
//remote user published stream
Success: {"action":"ONSTREAMADDED","message":"stresstest3"}
//local user hung up
Success: {"action":"HANGUP","message":"stresstest3"}
//connection to remote user closed
Success: {"action":"ONCHATSTOPPED","message":"stresstest3"}
//tablet set to airplane-mode -> device now offline
Error: {"action":"LOGIN","message":"com.intel.webrtc.base.WoogeenException: io.socket.engineio.client.EngineIOException: websocket error"}
//user got successfully disconnected
Success: {"action":"ONDISCONNECTED","message":""}
//6 reconnection errors
(6)Error: {"action":"LOGIN","message":"com.intel.webrtc.p2p.WoogeenP2PException: Socket.IO reports connect to signaling server failed."}
//airplane-mode turned off, wifi connected, connected to server again
Success: {"action":"LOGIN","message":"stresstest2"}
//local user invites remote user
IntelWebRTC.invite("stresstest3")
//successfully invited remote user
Success: {"action":"INVITE","message":"stresstest3"}
//remote user accepted invitation
Success: {"action":"ONACCEPTED","message":"stresstest3"}
//connection to remote user established
Success: {"action":"ONCHATSTARTED","message":"stresstest3"}
//local user published stream
Success: {"action":"PUBLISH","message":"stresstest3"}
//remote user published stream
Success: {"action":"ONSTREAMADDED","message":"stresstest3"}
//view scaling while in call
IntelWebRTC.scaleView(0.2,"top_right")
//scaling succeeded
Success: {"action":"SCALE_VIEW","message":""}
//remote user disconnected
Success: {"action":"ONCHATSTOPPED","message":"stresstest3"}

More Info

Intel WebRTC SDK: https://software.intel.com/en-us/webrtc-sdk

_______________________________________________

MQTT Connector Details

How to use a MQTT Connector in a REST-Client

You can choose between 2 operations: PUBLISH and SUBSCRIBE.

Build the payload like this: