Simplifier Academy

Courses & Documentation

PDF generated July 30, 2019

Access Business Object via Script

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

_______________________________________________

Action

Navigation | UI Action | Mobile Action | Server Action

Navigation

The Navigation element is used to trigger a navigation from one screen to another. By dragging it to the main screen, a list of screens to navigate to will appear in the right pane. 

You can set that the navigation should navigate back, or choose between several transitions: Slide, Fade, Flip or None.

Example In most cases, a navigation will be used when clicking on a button, so by combining a clickable event (e.g. button press) with a navigation element this can easily be achieved.

UI Action

With the UI Action element, you can map different widgets, variables and auto fields to another.

Let’s say there is a very simple login screen with an input field for the name and a button to submit.
The button should not be responsive, as long as the login field is empty. This can be achieved with the UI Action in the Process Designer.

Step 1 At first, assign the input field “InputUsername” to the Event.
Step 2 Next, a condition is needed. Check, if the value of the input field equals an empty string.
Step 3 If the condition is true and there is nothing written in the input field, the button should not be responsive. Add a UI Action and set within the mapping dialog the constant (boolean, false) on the left side (source) and map it to the equivalent widget on the right side (target). Select the screen, widget and property (in this case “enabled”).
For the other scenario, when there actually is an input written, you can connect the condition to a second UI Action and set the boolean via the constant on true.

Example

In this example, we have an application that writes the value of the first widget to the second input field and writes the value of the auto field (username) to the third widget after clicking on the corresponding buttons.
Now in the Process Designer, use 2 Events and 2 UI Actions for this. We’ve already added the press event on the first button and now we have to add the UI Action. By clicking on the mapping dialog, you can open the mapping. Connect the value of the widget Input1 with the widget Input2. Select the property that we’d like to connect by double-clicking on the widget.
To connect the auto field with the third input field, add the auto field and select the one you need, also by double-clicking on it.
This is the result of the mapping:

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 milliseconds the mobile device should vibrate.

Scan Meter

Parameter	DataType	Valid Values
Meter appearance	String	See the table below
Number of counters	Integer	1, 2 (from dropdown)
Integer digits	Integer/String	AUTO, 1-n
Fraction digits	Integer/String	AUTO, 1-n

You can choose from the following values for meter appearance:

Key	Value
mechanical_black	White text on black rollers
mechanical_white	Black text on white rollers
lcd	LCD Display
lcd_edl21	EDL21 and similar meters with LCD 7 (three-digit OBIS code to the left)

For the output mapping you can use the following parameter:

Paramter	DataType	Description
image	string	Image of the scanning process as data url
line1	string	Result of scanning the first counter (always set)
line2	string	Result of scanning the second counter (only set if 2 counters were scanned)
line1ObisCode	string	Result of scanning the first counter’s OBIS code (only set if meter appearance was set to lcd_edl21)
line2ObisCode	string	Result of scanning the second counter’s OBIS code (only set meter appearance was set to lcd_edl21 and 2 counters were scanned)

Audio/Video Call

This is a native feature for talking with a user via audio- or video live streaming. The user can be statically configured. Furthermore, you can set a fullscreen.

Play Video

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

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 recommended 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.

Server Action

The Server Action enables you to configure the login or logout for an application, address a template or send an e-mail.

Login

After mapping the according parameters you can decide which port you’d like to connect.

User Credentials

The Server Action needs two parameters as input if you want the user of the application to fill in his username and password. You can map the widgets in which the user fills in the information with the equivalent input parameter. (By double clicking on the widget, you can choose the exact property that you need).
The Login screen of your application might look like this:

Single Sign-on

You can use a Single Sign-on if you want to allow a user to use a single set of login credentials to access multiple applications. In difference to the first login method, you have to map an additional parameter, the authentication. Therefore you have to add this authentication method to the Simplifier in advance (this will be an admin task – take a look at “Settings for Admins“). The name that was given to the authentication is the one that is needed as an input parameter.
This is what the input mapping should look like:
The login screen of your application might look like this:

OAuth 2.0

Select OAuth as login in the server action and open the mapping dialog.

Within the mapping dialog you have the opportunity to choose between two parameters: Service describes the OAuth service provider (e.g. Google, Amazon, Azure…) that expects a string that represents the name of a provider configured in the server settings. UserSync expects a Boolean value to switch between the following two possibilities: Login via OAuth by synching a user profile (true) This will synchronize the retrieved information with a Simplifier user (if there is one for the credentials) or create a new user. In both cases, the current login is overwritten and all permissions are revoked. Login via OAuth by adding the OAuth token only to the Simplifier token of the current user or app (false) This does not synchronize the user, but adds the received token to the current user or app profile (if the app is configured to allow anonymous users), retaining all previous logins and associated permissions.

SAML 2.0

It is possible to log into a business app via SAML 2.0. Within the mapping dialog, you have the opportunity to choose between two parameters: Service – must be an existing SAML authentication setting. UserSync – should be true if a successful login replaces the primary user login. The behavior is analogous to the OAuth login.

Logout

For the Server Action Logout you don’t have to configure anything additionally.

Template

Use the Server Action Template to address templates.
With the help of parameters, it is possible to pass data to the template. Don’t forget to map the input and output. The complete template will be returned as a string.

E-Mail

The Server Action can be configured to send e-mails. Enter the sender and receiver e-mail, optionally CC and Bcc. You can enter multiple e-mail addresses for the receiver, CC and Bcc – in this case, the e-mail addresses have to be separated with a semicolon. At least, enter the subject and the body in HTML. For better user experience, it is possible to maximize the editor. It is also possible to use the mapping dialog to this instead of using the settings panel. Important: If a mapping is set, the settings in the panel are not considered.

_______________________________________________

Active Directory

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

_______________________________________________

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:

URL	/client/1.0/PLUGIN/pdfPlugin/adminTemplateAdd
Input-Parameter	Name	Template name
	Data	Template content (Base64-coded)
	Stylesheet	Content of the LESS Stylesheets (Base64-coded, optional)
	PreviewJson	Content of the sample data in JSON format (Base64-coded, optional)
Output-Parameter	None

Example for a call:

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

Output example:

{
    "success": true
}

_______________________________________________

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 that allow you to create and consistently use patterns.

To create a new template, click on the plus icon in the template overview. Select the folder name and enter a template name, optionally a description. Now enter the HTML template content and click on Save.

In the Template Editor, you have several options in the toolbar:

• Undo
• Redo
• Search
• Search and Replace
• Settings
• Fullscreen

In addition, it is possible to parameterize templates. To do this, switch to the tab ‘Parameters’. Via the plus icon you can add new input parameter.

For information about how to send the Templates go to: Business Object Script Template – Send Email.

_______________________________________________

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.

_______________________________________________

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 Links

Through App Links you can launch specific Simplifier business applications via Deep Links / URL. Use this feature to crosslink different business applications on your mobile device.
App Links can be used with the following URL scheme:

Scheme: 

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

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 the 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

_______________________________________________

Applications

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

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

Applications run on any device because it is generated on common open standard technology. 

Overview

By clicking on the Applications tile, you will be lead to the overview. At default, there you will see a table with all created applications. Within this table, you’ll get information like the name of the app, created by, last edited by, version, customization ratio, framework, and several actions.
At the top, to the right of the plus icon, you can switch between the list and table view. By changing the view, all lists in the Simplifier are changed. There you will see all created applications with information like the name of the app, the description, created by, last edited by, and the framework.

If you click on an application in the overview, further information and actions are displayed on the right side. On the one hand, you can edit the app name, switch directly to the application preview, or delete the application. On the other hand, you can customize the description, the app icon, look at the customization ratio and the version. Below this information, you then have various actions, in this case, Copy Application and Show Releases.

You can hide the details on the right with the button right of the search bar.

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 dependent libraries (of the app itself and its widgets as well as all transitive dependent libraries).

_______________________________________________

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 external Identity Providers in order to sync external user to the Simplifier.
The following Providers are supported:

LDAP	Active Directory (AD)	SAML 2.0	oAuth 2.0	SAP Single-Sign-On (SSO)

Note: if all authentication systems that are set have been run through and no result has been obtained, a login is executed against the Simplifier User database.

_______________________________________________

Automated Testing

On application deployment, the app generator provides a basic self-test for the business application. The automated tests are based on the SAP OPA5 test framework.

The URL of the test page is relative to the deployed business application used under the subpath /test/integration/opaTests.qunit.html and can be opened with a browser.

As an admin, you can perform an automated test. Make sure you are already in the UI Designer for the testing application. Switch to the tab Testing.

To create a new test case, click on the plus icon. Enter a test case name and the testing code. Then click on show test page.

_______________________________________________

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.

_______________________________________________

Basic Concept / Technology

All Simplifier applications are based on OpenUI5.

The Simplifier App Generator generates OpenUI5 Applications based on OpenUI5 Controls. Within Simplifier OpenUI5 Controls are represented by Widgets.

User Interface

To create the user interface of Simplifier applications visually the UI Designer is used. In general, OpenUI5 uses pages to represent views within a single-page-app. Within Simplifier UI Designer, pages are represented by screens. Simplifier applications consist of one or more screens and every screen can be populated with widgets.

Application Logic

Within Simplifier application logic is separated by user stories within the Process Dashboard. Every user story contains an isolated part of the overall application logic and can be edited with the Process Designer. The Process Designer is a visual scripting environment to create application logic based on configuration elements. To find out how to use configuration elements see chapter Process Designer.

How OpenUI5 concepts are handled within Simplifier

_______________________________________________

BROWSE Call - OPC/UA Connector

Call for BROWSE operations (the name TIA_BROWSE_ALL_VARIABLES is the arbitrarily 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[0]/nodeId/identifier
  Data Type: String or Numeric
• NamespaceIndex:
  Parameter Name: operations[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)
• identifierType (optional): Searches for the Identifier with a fixes Data Type.
  Parameter Name: operations[0]/identifierType
  Constant Value: Numeric, UUID, String, Byte String

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[0]/returnSet
Data Type: String
Constant Value: LIST

filterSettings (optional):

• Type:
  Parameter Name: operations[0]/filterSettings/filter/filterType
  Data Type: String
  Constant Value: NODE_CLASS
• Value:
  Parameter Name: operations[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.

_______________________________________________

Build 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 JSON. A live preview is provided on the right, so you can see changes in real time.

The rendering is executed with wkhtmltopdf, therefore 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 the resources 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: [“document1.pdf”, “document2.pdf”, “image.jpg”].

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

_______________________________________________

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 used among different applications. 

To copy a business object, just click in the overview of business objects on the ‘Copy Business Object’ button on the right of the selected entry.

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.

Related Forum Topics:

_______________________________________________

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 simplifierag/onpremise: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-Side - Access Connectors

 
var lfx_success = function(data) {
console.log(data)
};
var lfx_error = function(data) {
console.log(data)
};
var lb_showBusyIndicator = true;
var lb_failOnError = true;
Simplifier.Connector.GIS.getGisDivision({}, lfx_success, lb_showBusyIndicator, lb_failOnError, lfx_error)

_______________________________________________

Client-Side - Access other Business Objects

Access Server-Side Business Object

Simplifier.BusinessObject.ContentRepository.contentFolderEdit({}, lfx_success, lb_showBusyIndicator, lb_failOnError, lfx_error

Access Client-Side Business Object

Simplifier.ClientsideBusinessObject.ClientSideBO.getData({}, lfx_success, lb_showBusyIndicator, lb_failOnError, lfx_error)

_______________________________________________

Client-Side - Access Plugins

var lfx_success = function(data) {
console.log(data)
};
var lfx_error = function(data) {
console.log(data)
};
var lb_showBusyIndicator = true;
var lb_failOnError = true;
Simplifier.Plugin.contentRepoPlugin.contentFileEdit({}, lfx_success, lb_showBusyIndicator, lb_failOnError, lfx_error)

_______________________________________________

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. Changes can be undone or redone with the Undo / Redo Buttons. To get the code file, click on the “Download App” button.

_______________________________________________

Collaboration

It is possible to see if another user is editing the screens within the application. The number on the top left of the screen tile represents the number of editors on each screen.

As soon as another user starts editing the same screen, the color of the button (in the upper right as well as in the content area) changes to red. To show all editors, click on the button to open a popover with the editing users.

The list of editors is always up to date, so you get an immediate response if someone else starts editing the screen.

Due to the autosave function, there are possibilities to make changes undo or redo. That means, that user actions within the screen content and properties can be undone by clicking on the undo-icon.

The undo-list offers the last actions on the current screen, starting with the last one. If you select an entry from the list, it will be undone including its subsequent actions.

An avatar screen of the corresponding user is displayed within the list. In the case of collaboration, it becomes obvious that the operation will eventually undo the work of another user.

The following actions are listed:

• edit the screen properties
• add and remove widgets (screen elements)
• move widgets in the element tree
• edit widget properties, including ID, data aggregation, validations and events

Please note:

The undo lists at the application level are only retained as long as a user is active in the UI Designer. When the last user leaves the application, the lists and all deleted screens are permanently deleted.

The redo-icon provides recently undone actions to redo. The list is cleared when regular editing takes place.

_______________________________________________

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.

_______________________________________________

Conferencing Plugin for WebRTC Calls

The Cordova Conferencing provides WebRTC Conferencing functionality via Intel’s WebRTC SDK.

Intel WebRTC SDK Version: 4.1

Platforms:

• Android (5.0+ – x86, armV7, arm64-v8a)
• iOS (11+)

Cordova: 8+

General information

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

Possible Actions

Active Actions

Actions triggered by local user

• init – Take stun/turn-, userconfig and initializes connection
• joinRoom – Join a room
• leaveRoom – Leave a room
• getParticipant – Get participants of a room
• editParticipant – Update participant properties
• kickParticipant – Kick a participant
• createRoom – Create a room
• getRoom – Get a room
• editRoom – Update room options
• deleteRoom – Delete a room
• subscribe – Subscribe a remote stream
• unsubscribe – Unsubscribe a remote stream
• publish – Publish a local stream to a room
• unpublish – Unpublish a local stream
• startScreenSharing – Start to sharing/streaming the screen content
• stopScreenSharing – Stop screen sharing
• sendMessage – Send message to selected participants
• resizeRemoteContainer – Resize the native view of remote stream
• resizePublishContainer – Resize the native view of local stream
• getStream – Get a stream of selected room
• editStream – Update stream properties
• deleteStream – Delete a stream
• startRecording – Start recording a stream
• editRecording – Update recording options
• stopRecording – Stop recording a stream
• getRecording – Get a recording
• startStreamIn – Add an external stream to room
• stopStreamIn – Remove the external stream

Passive Actions

Actions triggered by server/remote user/network

• onReceivedChatMessage – User receives a chat message
• onChangedParticipantStatus – Participant leaves room
• onChangedConnectionStatus – Server/room get disconnected

Usage

Configuration description

Cordova API

init

/** 

 * Initializes native views and config properties. 

 * 

 * @param config     JSONObject - The config data 

 * @param success    The success callback is triggered when process is successful 

 * @param error      The error callback is triggered when process failed 

 */ 
ConferencingPlugin.init(config, success, error);

joinRoom

/** 

 * Create a conferencing token and join the selected room 

 * 

 * @param data JSONObject - Username, roomId and role 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 
ConferencingPlugin.joinRoom(data, token, success, error);

leaveRoom

/** 

 * Leave the current room and unpublish and unsubscribe all streams 

 * 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.leaveRoom(success, error);

getParticipant

/** 

 * Get all participants or the selected participant of a room 

 * 

 * @param data JSONObject - RoomId and userId 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.getParticipant(data, token, success, error);

editParticipant

/** 

 * Update the participant properties 

 * 

 * @param data JSONObject - RoomId, userId and userProperties 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.editParticipant(data, token, success, error);

kickParticipant

/** 

 * Kick a participant 

 * 

 * @param data JSONObject - RoomId and userId 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.kickParticipant(data, token, success, error);

createRoom

/** 

 * Create a room 

 * 

 * @param data JSONObject - Name and roomOptions 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.createRoom(data, token, success, error);

getRoom

/** 

 * Get all rooms or the selected room 

 * 

 * @param data JSONObject - RoomId 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.getRoom(data, token, success, error);

editRoom

/** 

 * Update the room options 

 * 

 * @param data JSONObject - RoomId and roomOptions 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.editRoom(data, token, success, error);

deleteRoom

/** 

 * Delete a room 

 * 

 * @param data JSONObject - RoomId 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.deleteRoom(data, token, success, error);

subscribe

/** 

 * Subscribe a remote stream 

 * 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.subscribe(success, error);

unsubscribe

/** 

 * Unsubscribe a remote stream 

 * 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.unsubscribe(success, error);

publish

/** 

 * Publish a local stream in a room 

 * 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.publish(success, error);

unpublish

/** 

 * Unpublish a local stream 

 * 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.unpublish(success, error);

startScreenSharing

/** 

 * Start screen sharing 

 * 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.startScreenSharing(success, error);

stopScreenSharing

/** 

 * Stop screen sharing 

 * 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.stopScreenSharing(success, error);

sendMessage

/** 

 * Send messages to the selected participants in a room 

 * 

 * @param message String - The config data 

 * @param data JSONArray - Selected participants 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.sendMessage(message, participants, success, error);

onReceivedChatMessage

/** 

 * Action triggered by server when received a chat message 

 * 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.onReceivedChatMessage(success, error);

onChangedParticipantStatus

/** 

 * Action triggered by server when participant changed his status (participant leave room) 

 * 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.onChangedParticipantStatus(success, error);

onChangedConnectionStatus

/** 

 * Action triggered by server when server/room changed his connections status 

 * 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.onChangedConnectionStatus(success, error);

resizeRemoteContainer

/** 

 * Resize the native view of a remote stream 

 * 

 * @param div HTML Object - The HTML remote stream view 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.resizeRemoteContainer(div, success, error);

resizePublishContainer

/** 

 * Resize the native view of a local stream 

 * 

 * @param div HTML Object - The HTML local stream view 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.resizePublishContainer(div, success, error);

getStream

/** 

 * Get all streams or the selected stream of a room 

 * 

 * @param data JSONObject - RoomId and streamId 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.getStream(data, token, success, error);

deleteStream

/** 

 * Delete a stream 

 * 

 * @param data JSONObject - RoomId and streamId 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.deleteStream(data, token, success, error);

editStream

/** 

 * Update the stream properties 

 * 

 * @param data JSONObject - RoomId, streamId and streamProperties 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.editStream(data, token, success, error);

startRecording

/** 

 * Start recording a stream of a room 

 * 

 * @param data JSONObject - RoomId, container (mp4), media 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.startRecording(data, token, success, error);

editRecording

/**

 * Update the recording options

 *

 * @param data JSONObject - RoomId, recordId, recordingOptions

 * @param token String - The simplifier token

 * @param success The success callback is triggered when process is successful

 * @param error The error callback is triggered when process failed

 */

ConferencingPlugin.editRecording(data, token, success, error);

stopRecording

/** 

 * Stop recording of a stream 

 * 

 * @param data JSONObject - RoomId and recordId 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.stopRecording(data, token, success, error);

getRecording

/** 

 * Get all or the selected recording of a room 

 * 

 * @param data JSONObject - RoomId and recordId 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.getRecording(data, token, success, error);

startStreamIn

/** 

 * Add an external stream to a room 

 * 

 * @param data JSONObject - RoomId, url, transport (tcp), media (audio or video) 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.startStreamIn(data, token, success, error);

stopStreamIn

/** 

 * Remove the external stream 

 * 

 * @param data JSONObject - RoomId and streamId 

 * @param token String - The simplifier token 

 * @param success The success callback is triggered when process is successful 

 * @param error The error callback is triggered when process failed 

 */ 

ConferencingPlugin.stopStreamIn(data, token, success, error);

General event object description

{
  "action": "<action>", //see "Possible Actions"
  "result": "<String>", //some results depending on action
}

Examples

Predefined callbacks and variables for the examples

let successCallback = function(event){
    console.log("Success: " + event);
}

let errorCallback = function(event){
    console.warn("Error: " + event);
}

let token = "dk4dfanew30239naa12dk2323r90asdf=="

– init

let config = {
        "connectionConfig": {
            "username": "paul",
            "server": window.serverUrl,
            "untrustedCertificate": true
        },
        "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": true,
            "maxFps": 60,
            "maxVideoBandwidth": 5000,
            "maxAudioBandwidth": 200,
            "videoCodec": "H264"
        },
        "debug": {
            "local": {
                "fps": false,
                "bitrate": false,
                "audiolevels": false
            },
            "remote": {
                "fps": false,
                "bitrate": false,
                "audiolevels": false
            }
        }
    };

ConferencingPlugin.init(config, successCallback, errorCallback);

– joinRoom

let data = {
    "role": "presenter",
    "username": "specialUser28",
    "room": "3023dak23dka1"  //roomId
};

ConferencingPlugin.joinRoom(data, token, successCallback, errorCallback);

– getParticipant

let data = {
    "room": "ksdfkfsdew3232",  //roomId
    "userId": "9SN_jqHVelwHksjaAACf"  //optional
};

ConferencingPlugin.getParticipant(data, token, successCallback, errorCallback);

– editParticipant

let data = {
    "room": "5c1b966d9869270cb9134328",
    "participantId": "HfwkX_3D1HYHjq-4AAEC",
    "items": [{
        "op": "replace",
        "path": "/permission/publish",
        "value": {
            "audio": false,
            "video": false
        }
    }]
};

ConferencingPlugin.editParticipant(data, token, successCallback, errorCallback);

– kickParticipant

let data = {
    "room": "5c1b966d9869270cb9134328",
    "participantId": "wRgmC31dz3hJHJzjAAEB"
};

ConferencingPlugin.kickParticipant(data, token, successCallback, errorCallback);

– createRoom

let data = {
    "name": "Testroom",
    "options": {
        "views": [{
            "video": {
                "parameters": {
                    "resolution": {
                        "height": 1080,
                        "width": 1920
                    },
                    "framerate": 60
                },
                "format": {
                    "codec": "h264"
                }
            }
        }],
        "participantLimit": 10,
        "inputLimit": -1
    }
};

ConferencingPlugin.createRoom(data, token, successCallback, errorCallback);

– getRoom

let data = {
    "room": "5c1b966d9869270cb9134328"  //optional
};

ConferencingPlugin.getRoom(data, token, successCallback, errorCallback);

– editRoom

let data = {
    "room": "5c1b966d9869270cb9134328",
    "options": {
        "name": "Testroom2",   //required
        "views": [{
            "video": {
                "parameters": {
                    "resolution": {
                        "height": 480,
                        "width": 640
                    },
                    "framerate": 30
                },
                "format": {
                    "codec": "h264"
                }
            }
        }],
        "participantLimit": 24
    }
};

ConferencingPlugin.editRoom(data, token, successCallback, errorCallback);

– deleteRoom

let data = {
    "room": "5c1b966d9869270cb9134328"
};

ConferencingPlugin.deleteRoom(data, token, successCallback, errorCallback);

– getStream

let data = {
    "room": "5c3c632f2686480cbf83e7e1",
    "streamId": "519038650981614300"    //optional
};

ConferencingPlugin.getStream(data, token, successCallback, errorCallback);

– deleteStream

let data = {
    "room": "5c3c632f2686480cbf83e7e1",
    "streamId": "519038650981614300"
};

ConferencingPlugin.deleteStream(data, token, successCallback, errorCallback);

– editStream

let data = {
    "room": "5c3c632f2686480cbf83e7e1",
    "streamId": "140827592383601540",
    "items": [{
        "op": "replace",
        "path": "/media/video/status",
        "value": "inactive"
    }]
};

ConferencingPlugin.editStream(data, token, successCallback, errorCallback);

– startRecording

let data = {
    "room": "5bbb5a846ee20b02aa9cf430",
    "container": "mp4",
    "media": {
        "audio": {
            "from": "764484888390779500",
            "format": {
                "codec": "opus",
                "sampleRate": 48000,
                "channelNum": 2
            }
        },
        "video": {
            "from": "764484888390779500",
            "format": {
                "codec": "h264"
            },
            "parameters": {
                "resolution": {
                    "width": 640,
                    "height": 480
                },
                "framerate": 30,
                "bitrate": "x0.8",
                "keyFrameInterval": 30
            }
        }
    }
};

ConferencingPlugin.startRecording(data, token, successCallback, errorCallback);

– getRecording

let data = {
    "room": "5c3c632f2686480cbf83e7e1",
    "recordId": "287103235454593920"  //<optional>
};

ConferencingPlugin.getRecording(data, token, successCallback, errorCallback);

– editRecording

let data = {
    "room": "5c3c632f2686480cbf83e7e1",
    "recordId": "287103235454593920",
    "items": [
        {
            "op": "replace",
            "path": "/media/video/parameters/framerate",
            "value": 60
        }
    ]
};

ConferencingPlugin.editRecording(data, token, successCallback, errorCallback);

– stopRecording

let data = {
    "room": "5c3c632f2686480cbf83e7e1",
    "recordId": "915058137572230700"
};

ConferencingPlugin.stopRecording(data, token, successCallback, errorCallback);

– startStreamIn

let data = {
    "room": "5c3c632f2686480cbf83e7e1",
    "url": "<video url>",
    "transport": "tcp",
    "media": {
        "audio": true,
        "video": true
    }
};

ConferencingPlugin.startStreamIn(data, token, successCallback, errorCallback);

– stopStreamIn

let data = {
    "room": "5c3c632f2686480cbf83e7e1",
    "streamId": "5c3c6313752307bf83e7d121"
};

ConferencingPlugin.stopStreamIn(data, token, successCallback, errorCallback);

Sample Eventlog

//initialization success
Success: {"action":"init","result":"App initialized"}
//get all rooms - Result: Name, id, options
Success: {"action":"getRoom","result": JSONArray}
//join room
Success: {"action":"createToken","result":"asdj0dDK3kf239332=="}
//get participant - Result: id, user, role, permissions
Success: {"action":"getParticipant","result": JSONArray}
//publish local stream to room
Success: {"action":"publish","result":"Published stream"}
//subscribe common stream of the selected room
Success: {"action":"subscribe","result":"Subscribed stream"}
//unsubscribe remotestream
Success: {"action":"unsubscribe","result":"Unsubscribed stream"}
//create room - Result: Name, id, options
Success: {"action":"createRoom","result": JSONObject}
//delete room
Success: {"action":"deleteRoom","result":"Room deleted"}
//start screen sharing
Success: {"action":"startScreenSharing","result":"ScreenSharing started"}
//stop screen sharing
Success: {"action":"stopScreenSharing","result":"ScreenSharing stopped"}
//start stream recording - Result: id, storagePath, mediaOptions
Success: {"action":"startRecording","result": JSONObject}
//stop stream recording
Success: {"action":"stopRecording","result": ""}
//add external stream to room - Result: id, info, options
Success: {"action":"startStreamIn","result": JSONObject}
//remove external stream
Success: {"action":"stopStreamIn","result":""}
//leave room
Success: {"action":"leaveRoom","result":"Room left"}

More Information

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

_______________________________________________

Connector Access via Script

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

_______________________________________________

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)

_______________________________________________

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.

_______________________________________________

Content Files

Add

FileSystem:

Input parameters

Note:

The content of the file can be transferred in three different ways. Exactly one of the following parameters must be passed:

• data: The content is passed directly with the JSON request as a Base64 encoded byte array.
• uploadSession: The content is first transferred to the AppServer via chunked HTML5 upload and the returned session is used as source. The Content Repository plugin downloads the file from the app server and uses it as content of the file
• copyFrom: The content is copied from another existing content file (copyFrom contains the ID of the file to be copied). Attention: The calling user must have the appropriate permissions to read the content file. Only the content is copied, not other properties (such as names, access rights, etc.). Any content file can be used as a source file, even in a different repository.

{
    "folderId" : 5,
    "name" : "test.txt",
    "description" : "My file description",
    "securitySchemeID" : "public",
    "permissionObjectType" : "Session",
    "permissionObjectID" : "abc",
    "data" : "dGVzdA=="
}

Output parameters

{
    "id": 15,
    "name": "test.txt"
}

ClearFileSystem:

Input parameters

Note:

The content of the file can be transferred in three different ways. Exactly one of the following parameters must be passed:

• data: The content is passed directly with the JSON request as a Base64 encoded byte array.
• uploadSession: The content is first transferred to the AppServer via chunked HTML5 upload and the returned session is used as the source. The Content-Repo plugin downloads the file from the AppServer and uses it as the content of the file
• copyFrom: The content is copied from another existing content file (copyFrom contains the ID of the file to be copied). Attention: The calling user must have the appropriate permissions to read the content file. Only the content is copied, not other properties (such as names, access rights, etc.). Any content file can be used as a source file, even in a different repository.

{
    "contentId" : 5,
    "fileName" : "test.txt",
    "folderPath" : "MyParentFolder/MyChildFolder"
    "data" : "dGVzdA=="
}

Find

FileSystem:

Input parameters

{
    "folderId": 3,
    "name": "test.txt"
}

Output parameters

{
    "files": [
        {
            "id": 3,
            "name": "test.txt",
            "description": "My file description 1",
            "statusSchemeID": "Default",
            "statusID": "Default",
            "securitySchemeID": "public",
            "permissionObjectType": "Session",
            "permissionObjectID": "abc",
            "mimeType": {
                "extension": "jpg",
                "mimeType": "image"
            },
            "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/ParentFolder/ChildFolder/file.jpg/",
        }
    ]
}

ClearFileSystem:

Input parameters

{
    "contentId": 3,
    "filename": "test.txt",
    "folderPath: "MyParentFolder/MyChildfolder"
}

Output parameters

{
    "files": [
        {
            "filePath": "MyParentFolder/MyChildFolder/test.txt",
            "mimeType": {
                "extension": "txt",
                "mimeType": "text"
            },
            "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyParentFolder/MyChildFolder/test.txt/"
        },
        {
            "filePath": "MyParentFolder/MyChildFolder/MyFolder/test.txt",
            "mimeType": {
                "extension": "txt",
                "mimeType": "text"
            },
            "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyParentFolder/MyChildFolder/MyFolder/test.txt/"
        }
    ]
}

List

FileSystem:

Input parameters

{
    "folderId": 3
}

Output parameters

{
    "files": [
        {
            "id": 3,
            "name": "test.txt",
            "description": "My file description 1",
            "statusSchemeID": "Default",
            "statusID": "Default",
            "securitySchemeID": "public",
            "permissionObjectType": "Session",
            "permissionObjectID": "abc",
            "mimeType": {
                "extension": "txt",
                "mimeType": "text"
            },
            "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyParentFolder/MyChildFolder/test.txt/"
        },
        {
            "id": 4,
            "name": "test2.txt",
            "description": "My file description 2",
            "statusSchemeID": "Default",
            "statusID": "Default",
            "securitySchemeID": "public",
            "permissionObjectType": "Session",
            "permissionObjectID": "abc",
            "mimeType": {
                "extension": "txt",
                "mimeType": "text"
            },
            "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyParentFolder/MyChildFolder/test2.txt/"
        }
    ]
}

ClearFileSystem:

Input parameters

{
    "contentId": 3,
    "folderPath": "MyFolder"
}

Output parameters

{
    "files": [
        {
            "fileName": "test.txt",
            "mimeType": {
                "extension": "txt",
                "mimeType": "text"
            },
            "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyParentFolder/MyChildFolder/test.txt/"
        },
        {
            "name": "test2.txt",
            "mimeType": {
                "extension": "txt",
                "mimeType": "text"
            },
            "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyParentFolder/MyChildFolder/test2.txt/"
        }
    ]
}

Get

FileSystem:

Input parameters

{
    "id": 3
}

Output parameters

{
    "id": 3,
    "folderId": 5,
    "name": "test.txt",
    "description": "My file description",
    "statusSchemeID": "Default",
    "statusID": "Default",
    "securitySchemeID": "public",
    "permissionObjectType": "Session",
    "permissionObjectID": "abc",
    "data": "dGVzdA==",
    "mimeType": {
        "extension": "txt",
        "mimeType": "text"
    },
    "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyParentFolder/MyChildFolder/test.txt/"
}

ClearFileSystem:

Input parameters

{
    "contentId": 3,
    "filePath": "MyFolder/test.txt"
}

Output parameters

{
    "filePath": "MyFolder/test.txt",
    "data": "dGVzdA==",
    "length": 59570,
    "mimeType": {
        "extension": "txt",
        "mimeType": "text"
    },
    "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyFolder/test.txt/"
}

Get Metadata

FileSystem:

Input parameters

{
    "id": 3
}

Output parameters

{
    "id": 3,
    "folderId": 5,
    "name": "test.txt",
    "description": "My file description",
    "statusSchemeID": "Default",
    "statusID": "Default",
    "securitySchemeID": "public",
    "permissionObjectType": "Session",
    "permissionObjectID": "abc",
    "mimeType": {
        "extension": "txt",
        "mimeType": "text"
    },
    "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyParentFolder/MyChildFolder/test.txt"
}

ClearFileSystem:

Input parameters

{
    "contentId": 3,
    "filePath": "MyFolder/test.txt"
}

Output parameters

{
    "filePath": "MyFolder/test.txt",
    "mimeType": {
        "extension": "txt",
        "mimeType": "text"
    },
    "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyFolder/test.txt"
}

Get Metadata batched

FileSystem:

Input parameters

{
    "contentId": 1,
    "files": [{
        "id": 1
    },
    {
        "id": 2
    }]
}

Output parameters

{
    fileMetadata: [{
        "id": 1,
        "folderId": 5,
        "name": "test.txt",
        "description": "My file description",
        "statusSchemeID": "Default",
        "statusID": "Default",
        "securitySchemeID": "public",
        "permissionObjectType": "Session",
        "permissionObjectID": "abc",
        "mimeType": {
            "extension": "txt",
            "mimeType": "text"
        },
        "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyParentFolder/MyChildFolder/test.txt"
    },
    {
        "id": 2,
        "folderId": 3,
        "name": "picture.jpg",
        "description": "My file description",
        "statusSchemeID": "Default",
        "statusID": "Default",
        "securitySchemeID": "public",
        "permissionObjectType": "Session",
        "permissionObjectID": "abc",
        "mimeType": {
            "extension": "jpg",
            "mimeType": "picture"
        },
        "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/MyParentFolder/MyChildFolder2/picture.jpg"
    }]
}

ClearFileSystem:

Input parameters

{
    "contentId": 6,
    "files": [{
        "filePath": "Folder/picture.jpg"
    },
    {
        "filePath": "Folder2/text.txt"
    }]
}

Output parameters

{
    fileMetadata: [{
        "filePath": "Folder/picutre.jpg",
        "mimeType": {
            "extension": "jpg",
            "mimeType": "picture"
        },
        "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/Folder/picture.jpg"
    },
    {
        "filePath": "Folder2/test.txt",
        "mimeType": {
            "extension": "txt",
            "mimeType": "text"
        },
        "url": "http://localhost:8080/client/2.0/plugin/contentRepoPlugin/file/RepoName/Folder2/test.txt"
    }]
}

Edit

FileSystem:

Input parameters

{
    "id" : 5,
    "name" : "test.txt",
    "description": "My new file description",
    "securitySchemeID" : "public",
    "permissionObjectType" : "Session",
    "permissionObjectID" : "abc",
    "data" : "dGVzdA=="
}

ClearFileSystem:

Input parameters

{
    "contentId" : 5,
    "sourceFilePath" : "MyParentFolder/test.txt",
    "destFilePath": "MyParentFolder/MyChildFolder/myRenamedMovedFile.txt"
}

Delete

FileSystem:

Input parameters

{
    "id": 15
}

ClearFileSystem:

Input parameters

{
    "contentId": 10,
    "filePath" : "MyFolder/myFile.txt"
}

_______________________________________________

Content Repository

The Content Repository Plugin is used to implement a persistence layer for data so that you can store images and videos using this plugin. It contains a repository, folders and files, so you create a repository (parent folder) in which subfolders can be stored in any hierarchy.

Example call of a Content Repository Plugin function via a server-side Business Object:

var payloadClearFileSystem = {
    slot: "contentRepositoryAdd",
                payload: {
                               "provider": "ClearFileSystem",
                               "name": input.name,
                               "description": input.description
                }
};

var result = JSON.parse(PLUGIN_contentRepoPlugin.run(JSON.stringify(payloadClearFileSystem)))

The payload configuration depends on the required slot.

Difference between File System and Clear File System:

The file system stores the received content repository data in a database.
The clear file system stores this data in an actual file system (compare Windows Explorer).

Content Repositories

Add

FileSystem:

Input parameters

{
    "permissionObjectType" : "App",
    "permissionObjectID": "DummyApp",
    "provider" : "FileSystem",
    "name": "MyTestRepo",
    "description": "MyTestRepoDescription"
}

{
    "id": 15
}

ClearFileSystem:

Input parameters

{  
    "name": "MyTestRepo",
    "provider" : "ClearFileSystem",
    "description": "MyTestRepoDescription"
}

Output parameters

{
    "id": 15,
    "description": "MyTestRepoDescription"
}

Find

FileSystem:

Input parameter

{
    "name": "MyRepo"
}

Output parameters

{
    "repositories": [
        {
            "id": 3,
            "name": "MyRepo",
            "description": "My repo description",
            "permissionObjectType": "App",
            "permissionObjectID": "DummyApp",
            "provider": "FileSystem",           
        }
    ]
}

ClearFileSystem:

Input parameter

{
    "name": "MyRepo"
}

Output parameters

{
    "repositories": [
        {
            "id": 3,
            "name": "MyRepo",
            "description": "My repo description",
            "provider": "ClearFileSystem"
        }
    ]
}

List

FileSystem:

Input parameter

{
    "provider": "FileSystem"
}

Output parameters

{
    "repositories": [
        {
            "id": 3,
            "name": "MyRepo",
            "description": "My repo description",
            "permissionObjectType": "App",
            "permissionObjectID": "DummyApp",
            "provider": "FileSystem",          
        },
        {
            "id": 4,
            "name": "MyRepo2",
            "description": "My repo description 2",
            "permissionObjectType": "Session",
            "permissionObjectID": "abc",
            "provider": "FileSystem",          
        }
    ]
}

ClearFileSystem:

Input parameter

{
    "provider": "ClearFileSystem"
}

Output parameters

{
    "repositories": [
        {
            "id": 5,
            "name": "MyRepo5",
            "description": "My repo description 5",
            "provider": "ClearFileSystem"
        },
        {
            "id": 6,
            "name": "MyRepo6",
            "description": "My repo description 6",
            "provider": "ClearFileSystem"
        }
    ]
}

Get

FileSystem:

Input parameter

{
    "id": 3
}

Output parameters

{
    "id": 3,
    "name": "MyRepo",
    "description": "My repo description",
    "permissionObjectType": "App",
    "permissionObjectID": "DummyApp",
    "provider": "FileSystem",
}

ClearFileSystem:

Input parameter

{
    "id": 3
}

Output parameters

{
    "id": 3,
    "name": "MyRepo",
    "description": "My repo description",
    "provider": "ClearFileSystem",
}

Edit

FileSystem:

Input parameters

{
    "id" : 15,
    "permissionObjectType" : "App",
    "permissionObjectID": "DummyApp",
    "name": "MyTestRepo",
    "description": "My new description",  
}

ClearFileSystem:

Input parameters

{
    "id" : 15,
    "name": "MyTestRepo",
    "description": "My new description"
}

Delete

A repository can only be deleted if it does not contain any content folders.

{
    "id": 15
}

_______________________________________________

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.

_______________________________________________

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

API reference

Simplifier Widget Type

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 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.

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.

_______________________________________________

Create and Manage Connectors

Connector Type | Login Method | Connector Details | Copy a Connector | Usage of Connector

To create a new connector, click on the plus icon on the upper right corner within the connector overview. It opens a new pop up where you can select the connector type and 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 popup that displays all applications that uses the connector:

By clicking on an entry, the application opens so that you can edit it.

_______________________________________________

Create and manage Methods

The logic of a business object is implemented via script templates/methods. Each business object can hold as many methods as wanted. Click on the ‘Edit methods’ icon to add some templates via the ‘+’.

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 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, settings and fullscreen.

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 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.

_______________________________________________

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 Designer 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 client-side 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 popup that displays all used applications:

By clicking on an entry, the application opens so that you can edit it directly.

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
}

As client-side Business Objects and their contents are called asynchronously, it may happen when a connector call is called that it is not yet finished and is returned undefined or null.

To avoid this, you must call fnSuccess instead.

fnSuccess ({
      myOutputParameter : myOutputValue 
})

It must be called in your last callback/function of your client-side Business Object and returns the data.

In the case of an error, the following can be specified:

fnError ({
      myErrorMessage : myErrorMessageValue 
})

_______________________________________________

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 Designer by the tags.

You may then select any connector, plugin or other business objects 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 server-side Business Objects

You can see which applications or interfaces are using the business object. For that, click on the appropriate icon on the right.

It opens a popup that displays all used applications:

By clicking on an entry, the application opens so that you can edit it directly.

_______________________________________________

Create your first Application

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.

_______________________________________________

CSS Editor

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

Warning: The syntax for accessing widgets by ID with CSS is: #<screenId>–<widgetId>

After changing CSS properties you have to deploy your application.

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

_______________________________________________

CSV Connector

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.

_______________________________________________

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.

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.

_______________________________________________

Current Release & Archive

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

Download Previous Simplifier Documentations:

Version	PDF	HTML
Simplifier Documentation Release 3.5

New Features Release 4.0

Collaboration

In order to optimize the teamwork in the UI Designer, it is now possible to work on an application simultaneously with several users. The new AutoSave function ensures that no changes can get lost and that every user works with the latest version.
Like in version 3.5, user stories can be saved separately. In addition, the Simplifier indicates who is currently working in which user story to enable conflict-free working in the Process Designer.

UI Designer:
Read more »

Process Designer:
Read more »

Test-History

To simplify the testing of interfaces (connectors) and business objects, there is now a test history. Input parameters and test results for the test procedures are stored and archived. Users can retrieve this information at any time and repeat the tests as required.

Connectors:
Read more »

Business Objects:
Read more »

Automated testing

To reduce the manual testing effort of applications, users can create automated tests by using the OPA5 technology. An absolute innovation in the low-code market is the connection to an automated German test cloud. This allows the app to be tested automatically on different browsers and operating systems*.

*paid feature

Read more »

App documentation

For a better traceability during the app creation, the app process documentation is now automatically generated in Markdown format. In addition, the last editor of applications and connectors is displayed.

Read more »

Additional authentication methods

For external user management systems and single sign-on scenarios, the Simplifier now supports even more authentication methods such as OAuth 2.0, SAML 2.0 and OpenID Connect. The connection to an existing LDAP, Active Directory or SAP system via SSO2 is still supported.

Open Authorization (OAuth):
Read more »

Security Assertion Markup Language (SAML):
Read more »

Archive Logs

With version 4.0, the central log for the monitoring of Simplifier applications during runtime can be archived via the central settings.

Conferencing Plugin

The Conferencing Plugin for real-time audio and video calls has been optimized.

Read more »

Data Workbench

Elements can be edited within the Data Workbench. Users also get more information about variables and auto fields at first glance, e.g. the exact data type.
In addition, we have added some attributes to the Auto-Field URL, such as protocol, port and source address.

For more information, have a look at Data Workbench and the following pages.

_______________________________________________

Data Centers of Simplifier Cloud

[vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]The Simplifier Cloud is hosted in data centers of T-Systems Germany.

The locations of the twin-core data centers are:

[/vc_column_text][/vc_column][/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_gmaps link=”#E-8_JTNDaWZyYW1lJTIwc3JjJTNEJTIyaHR0cHMlM0ElMkYlMkZ3d3cuZ29vZ2xlLmNvbSUyRm1hcHMlMkZkJTJGdSUyRjAlMkZlbWJlZCUzRm1pZCUzRDF2YXJBRGVLbkpzYkQ0UW9ZX19FTWl5OUpLT0ZhcE5JdyUyMiUyMHdpZHRoJTNEJTIyNjQwJTIyJTIwaGVpZ2h0JTNEJTIyNDgwJTIyJTNFJTNDJTJGaWZyYW1lJTNF” title=”T-Systems data center”][/vc_column][/vc_row]

_______________________________________________

Data Object

Connector | Asynchronous Connector | Business Object | Mapping Collections | Mapping Structs

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 asynchronous) or a business object.

Connector

A typical example of a data object is a previously defined connector call. An assistant offers all configured connectors that own 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 complete UI should be blocked by the busy indicator, or which element(s) 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 pop up 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 e.g. the input mapping, 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.In this example, the request of the selected connector call provides only a single input parameter, an ID field named “TechnischerPlatzId”. This input parameter is connected with the value of the widget “CustomerType”. This means, that once the data object is triggered, e.g. through a button press event, the connector will be called with the actual value of the widget “CustomerType” as the request parameter.You can choose the exact source that you want to use for the input parameter by double-clicking on the widget. It opens a list of all properties so you can choose the one you need as input.

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).

Business Object

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

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

The dialog shows all configured business objects that include methods. You can search for the name of the business object. By selecting a business object, all methods are listed on the right-hand side.

Mapping Collections

Collections represent multiple results of Structs. For example, a database request may deliver a list of addresses from numerous people and you can map them to the equivalent widget within a data object.

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 is 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, showBusyIndicator and error message

Output Mapping

The output mapping of a data object to a table, a list or a selected 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.

Validation of mandatory Parameters

All configured parameters have an indicator if it’s mandatory. If you haven’t mapped all input parameters of a data object that has been marked as mandatory, the following warning will appear:

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 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”).

_______________________________________________

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

Custom Events | Global Variables | Global Auto Fields

Within the Data Workbench, it is possible to administer custom events, global variables and auto fields that you want to use cross-functional in the user stories.

Custom Events

Custom events can be imagined as tunnels which connect different user stories or processes. By publishing an event, you open the entrance to the tunnel and by subscribing to this particular event, you create the exit of the tunnel. This enabled you to jump between the user stories and helps you to have a clearly laid out working space. To create a new custom event, click on the plus icon. Enter a name and then you can use it in the Process Designer. Go to Events for an example of using the custom event in the Process Designer. In this section, you can also find out how to create a custom event directly in the Process Designer.

Global Variables

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.
To create a new one, click on the plus icon. Enter a variable name, variable type and default value (optional).
You can also select, e.g. a struct as the variable type.
If you have selected a struct as a variable type and clicking on the value helper for the variable type, the dialog on the right appears. The dialog lists the fields of the ‘Machine’ struct on the left side like a tree. The struct is expanded to its first children so that the user can immediately see which are the fields of the parent node ‘Machine’.

You get the information about the fields on the right panel to configure the default values.

In general, the fields have four different appearances depending on their own data type:

Example of a link press for clarification:

By pressing the ‘lubricant’ link from the dialog above, there are also different appearances of the tree items depending on their datatype:

Data type	Icon	Is Expandable	Plus Button	Remove Button
Base (String, Integer, Float, Date, Boolean)		No	No	No
Domain		No	No	No
Struct		Yes	No	No
Collection		Depending on collection items	Yes	No (only if it is a collection in a collection)

Collection exception:

By adding a collection object, the item is inserted into the structure below the collection. The collection object can then be clicked like an ordinary tree element. The only difference is that a collection item can be removed using the delete button.

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.

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 actual name or load e.g. the version number. To create a new auto field, click on the plus icon in the Data Workbench. Enter a name for the auto field, the type, and the characteristic. It is possible to declare auto fields from five types: Application User URL Geolocation Device

In the overview, the type of the auto field is displayed underneath its name and the characteristic is displayed on the right-hand side.

To edit an auto field, use the edit icon. It opens the same dialog as creating the auto field, but of course, predefined with the data, you set before. If you no longer need an auto field, delete it by clicking the appropriate icon.

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 the user name. It is mapped 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.

_______________________________________________

Delete a PDF Template

{

    "name": "templatename"

}

{

    "success": true

}

_______________________________________________

Deploy and Preview

Applications can be deployed rapidly and previewed within a standard web browser and on the mobile device using the Simplifier Mobile Client.

If you click on preview, it opens a new browser tab. Every time you will deploy your application, the browser tab will be reloaded automatically.

Warning: Make sure that pop-ups are not blocked in your browser for your Simplifier instance.

You can simulate your preview for different mobile devices with the Chrome Developer Tools or use it for debugging.

To access the DevTools, open your app preview in Google Chrome and press F12.

Alternatives:

• Select the Chrome menu at the top-right of your browser window, then select Tools > Developer Tools.

• Or use Ctrl+Shift+I (or Cmd+Opt+I on Mac).

Via the toggle device toolbar, you can simulate different devices like Galaxy S5, iPhone 6 or iPad to preview your application. More information on Google Chrome DevTools Device Mode.

_______________________________________________

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 Simplifier AG. 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
• System owner regarding Backend Interfacing
• Firewall Administrators
• Reverse Proxy Administrator
• IT Administrators
• SSL Certificates 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 used by 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 auto field type with the auto field type “Device” and the characteristic “Device Type”. How to create auto fields, you can see here.

Within the Process Designer, you can refer to this auto field 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 the 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 simplifierag/onpremise:latest

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

_______________________________________________

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.

_______________________________________________

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

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.

Take a look at Email Connector Call.

_______________________________________________

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:

{
    "session": String,
    "fileName": String,
    "attachmentMimeType": String
}

_______________________________________________

Enumeration in Widget Properties

You can maintain enumeration for widget properties. Enumerated properties can only hold the defined values and will be displayed as a 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

_______________________________________________

Events

Publish Custom Events | Subscribe to Custom Events

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”.

It guides you to your required event. When subscribing to an Event, you can select events from these categories: Widget Events, Screen Events, Custom Events and System Events. Each category is sorted and searchable.

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

---

Event Type	Description
Widget Events	Events that are available for certain widgets, e.g. button press event.
Screen Events	Events related to screens, e.g. onInit and onAfterShow.
Custom Events	Individual events within an application that can be published and subscribed at any time.
System Events	Events related to devices, e.g. onDeviceGoesOffline and onOrientationChange.

Publish Custom Events

If you want to make an event usable in other user stories, create a new Custom Event under the tab “Publish Event”.
A shortcut for creating Custom Events can be found in the top right-hand corner.

Subscribe to Custom Events

You can subscribe to a custom event in another user story to connect the logic between different user stories. 

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 the other user story exclusively for the whole navigation of your application. So you want the end of the event from User Story 1 (the navigation) subscribed to 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

Custom Events can be maintained in the Data Workbench.

_______________________________________________

Example Apps

To demonstrate various features of Simplifier the following Example Apps are available with every Simplifier Freemium Instance and can be downloaded here

_______________________________________________

Example of using OData

In this example, the data of the OData connector is displayed in a listitem. So the logic behind the application in the Process Designer may look like this:

First you subscribe to a screen event onAfterRendering. A business object is then addressed in order to read the user token of the logged in Simplifier user. Mapping takes place within the business object. The token is written to a variable that must be created in advance. You can find out how to do this here. The business object is necessary because the connector is addressed later in the script activity in the route and an authentication is necessary.

Finally, the script activity is used to set the model:

var oModel = new sap.ui.model.odata.ODataModel("/client/1.0/PATH" + this.getGlobals().getVar("token"));
console.log(this.getGlobals().getVar("token"));
oModel.read("/T_IOT_190603718A7C2818EE3D?", null, null, true, function(oData, response) {
this.setItemModel("ID of the SCREEN", "ID of the WIDGET", "ITEMS", oData.results);
}.bind(this));

In this case, it’s:

var oModel = new sap.ui.model.odata.ODataModel("/client/1.0/odata/ODATA_Procurement_Overview/?SimplifierToken=" + this.getGlobals().getVar("token"));

console.log(this.getGlobals().getVar("token"));

oModel.read("/T_IOT_190603718A7C2818EE3D?", null, null, true, function(oData, response) {

this.setItemModel("Main", "Main_List1", "items", oData.results);

}.bind(this));

_______________________________________________

Execution Log

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

The following type of entries are logged:

_______________________________________________

Features and supported operating systems

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

See the full featured list of supported operating systems:

_______________________________________________

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:

_______________________________________________

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 Simplifier. To do that, we deliver a prepared Docker image to you. The image comes pre-configured and contains all the required components, including a Simplifier server in its most recent version.

The target instance must fulfill the following requirements:

• At least 12 GB RAM minimum, 16 GB recommended
• x64 CPU with minimum 2 cores, 4 cores recommended and at least 2 GHz per core
• At least 40 GB of free hard disk space
• Opened incoming ports: http/80 (TCP),  https/443 (TCP), https/8090 (TCP)
• Optional: Opened outgoing ports for
  • preconfigured SMTP-Server (StartTLS Port 587) by Simplifier
  • your Backend Systems to configure and reach the Data Sources successfully
  • SSL Certificate for encrypted https traffic in frontend access
• Operating system:
  • Linux (recommended)
    • 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: 64-Bit Versions of Ubuntu 18.04 (Bionic Beaver), 16.04 (Xenial) or 14.04 (Trusty)
      • CentOS 7.3: 64-Bit
      • Debian: Debian Stretch (Testing), Jessie (8.0), Wheezy (7.7, with Kernel-Update to Version 3.10)
      • Fedora: Versions 24 & 25
      • RHEL (Redhat Enterprise Linux) and SUSE Enterprise are officially supported only by paid docker variants (EE), Installations from CentOS Repository respectively OpenSUSE Repository are possible to use
  • Windows
    Install Docker for Windows
    • • • Windows 10 Professional
        • The runtime is given, but not as a Windows Service. The Docker Containers only stays up and runs in a locked user session.

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

  • 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 separate 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

“D-Q-P”-landscape

To ensure high availability and qualified operations, it is necessary to build a three-stage system landscape (= DQP-landscape: development, quality, production). Please note that with a DQP-landscape the system requirements are tripled.

_______________________________________________

Getting Started

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. Basically the functionality can be divided in two main categories:

• Application Creation, Operation and Maintenance
• abstract Integration Layer to connect external data sources

Main Features:

• Collaborative web-based Development Environment to configure integrated Mobile, Wearable and Browser applications
• Customization of Applications with UI Designer and Process Designer for visual Application Logic
• Customization of Backend Interfaces through standardized Connectors
• Rapid Deployment and Over-the-Air-Updates
• Contextual Technologies (Augmented Reality / Realtime Communication, Scanning, Device Sensors)
• Multi-Device (Browser, Smartphones, Tablets, Wearables)
• Multi Platform Mobile Client for Android and iOS

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 instead can be easily configured and integrated into any system. Thus, applications can be mapped process-oriented.

The main features of Simplifier can be accessed from the central Dashboard, that consists of the following parts:

• Applications
• Connectors
• Business Objects
• Data Types
• Users
• Transports
• Plugins
• Logs & Monitoring
• Jobs
• Templates

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

_______________________________________________

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 (optional) 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}

_______________________________________________

How to use Widgets in the UI Designer

Add Widgets to the Screen

To fill your screen with UI elements like text fields, charts or action buttons, use the widget panel on the left side. First, search for a specific widget using the name or just browse the list, then add the widget to the screen via the plus icon. The widget will appear in the content area of the screen.

Sort Widgets in the right order

Widgets can also be nested in a structured hierarchy – representing the positions within the document structure. For example, a table must have columns and rows – so the columns and rows have to be added nested underneath the table element. So in the first step, add the table to the existing screen. After that, select the table and then add columns.

The column widget is now nested under the table widget. 

You can also use the arrow keys to structure the widgets in the content area into a hierarchy, or alternatively use WASD on your keyboard.

W or	moves the widget upwards
A or	de-nests the widget
S or	moves the widget downwards
D or	nests the widget underneath the one above (if possible)

With the arrow keys on your keyboard, you can navigate through the content area as follows:

Copy Widgets within the Screen Content

You can copy Widgets and insert them on a different Screen or even another Application. For that, use the Copy, Cut and Paste function.

Edit Widget Properties

Every widget has properties to configure how the widget behaves. In the following example the properties of a button widget are shown.

In this example, the text property represents the text shown on the button in the user interface. 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.

Client Validation of Default Properties

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 Properties panel of the UI Designer. The button opens 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” is displayed.

_______________________________________________

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.1 If your server has an Internet connection, you can get the Docker image from Docker Hub. 

$ docker pull simplifierag/onpremise:latest 
# for the Onpremiseversion include MySQL and Nginx

$ docker pull simplifierag/netzportal:latest
# for the Netzportalversion with config files for your own Oracle DB

View the variants and their versions. 

2.2 As an alternative we can provide a tarball for download. 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

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.

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

$ docker load -i <imagefile.tar>

3. Install SSL certificates:

$ mkdir -p $SIMPLIFIER_DIR/certs

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

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

4. 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 Tag>

Alternative 2: without SSL/Certificates

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

-p 80:8080 -p 8090:8091 \

-d <Docker Tag>

Replace the <Docker Tag> with the selected variant, e.g. simplifierag/onpremise:latest

5. 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

_______________________________________________

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.

_______________________________________________

ISO Certificates and Audits

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: