Current Release & Archive

The Documentation refers to the latest version of Simplifier (5.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 4.5
Simplifier Documentation Release 4.0
Simplifier Documentation Release 3.5

New Features Release 5.0

UI Designer  

The UI Designer which is used for the creation of user interfaces has been completely redesigned. 

Besides the already known features, such as real-time collaboration, the new WYSIWYG editor is our greatest achievement: You can drag & drop your widgets into the editor, which directly displays the preview of the interface in real time.

Live Preview

In addition, you can use the Live Preview on different device form factors to test the layout without deployment first. This makes application creation much easier and saves a lot of time! The different selection of corporate designs (themes) and your changes in the CSS editor are also directly visible.  

Icon Explorer 

To assign meaningful icons to your modern layout, we integrated an icon explorer for searching and using icons visually. 

New Database Designer and No-SQL Access 

A very special feature is the new Database Designer. It drastically simplifies database creation, as you can now create your database scheme directly visually in Simplifier and deploy it to multiple target databases like MySQL, Oracle, Microsoft SQL Server and SQLite. 

Invite developer 

Working on an application with other people makes many things way easier. The new Share Button allows you to easily invite other team members via E-Mail to work on your current app project.

New Datatype Generation of Test results of Business Objects and Connectors 

To reduce the manual work of data type definition, you can create simple or complex datatypes from connector request or business objects results in the test dialog automatically. 

Asset Editor 

To help you better manage the static content of an app, we have created a new Asset dialog. This dialog allows you to upload and preview images as well as download them and provides more clarity. 

Theming Administration 

Corporate design is very important for every company. Accordingly, themes can be directly assigned and loaded to the Simplifier instance.  

You can therefore use the application on different instances in different corporate designs.  Separate loading of themes via business objects is now a thing of the past.  

Attribute and Role Mapping from external IDP 

Security and authentication are particularly important to us: The authentication mechanisms Active Directory, SAML 2.0, LDAP and OAuth 2.0 now offer central role and user attribute mapping based on defined rules. 

Roles and attributes can thus be maintained centrally in your company’s user administration and automatically synchronized in Simplifier.  A new standard role can also be defined. This is automatically assigned to a new user.  

Not to forget the metadata exchange via URL: This ensures that client and provider always use the most up-to-date metadata. 

Administration Interface Dark Mode 

It gets dark in our administration dashboard so you won´t have to be in the dark when creating apps: The new Dark Mode follows the trend towards eye-friendly operation. 

Functionality in Server-Side Business Objects 

With the Crypto JavaScript library you can now both decrypt and encrypt data. The functions of the Lodash library offer you a wide range of data filters and manipulations. Via our Simplifier User API you can now add your own profile pictures to the user profile. 

Mobile Actions 

Now, you can also record a video configuratively with the camera on your mobile devices. Simply choose how many videos are created and how long they should be. 

Plugin Secret Administration 

You can now create your own keys in the plugin administration to register your own plugins securely with Simplifier. 

Enhanced Feature-Set for OData v2 Connector 

You can now use the test dialog for testing OData calls directly. We also support Function Imports in our OData wizard to easily use this kind of business logic as a connector call. 

SQL Database Support for IBM DB2 

In addition to the well-known databases, we now also support IBM DB2 and IBM DB2 for AS-400 systems for easy recycling of old Lotus Notes applications. 

Support for Client X.509 Certificates 

Simplifier allows you to manage X.509 certificates and use them as a login method for authentication on backend systems via our connectors. 

Enhanced widget editing 

Be it icons, widget wizard, revised interface or drag & drop zones for the WYSIWYG editor – all UI5 versions of a widget can be managed directly in the mask. This includes support for auto-generating controls from the commercial SAP UI5 library. 

Optimized Process Designer 

Links to Process Designer Items are now highlighted when selected. The selection of mobile actions has been reworked for better handling. 

The Script Action now offers a selection of ready-made and useful JavaScript code to get results even faster. 

Enhanced RFC connector 

Our SAP RFC connector now also supports TABLES parameters for exchanging data from SAP function modules and Auto Commit to trigger automatic updates to the sap database. 

Test Dialog of Connectors and Business Objects 

The test results are now displayed in the test dialog for business objects and connectors formatted as JavaScript Object Notation (JSON) View including syntax highlighting.  

Individual result rows can be folded in and out, to get a better overview. 

Enhanced transport system 

Business objects that refer back to themselves through other business objects (circular reference) are now imported correctly. 

Templates Preview  

Templates now directly generate a preview when the content is changed. 

Optimized App Deployment 

You can now optionally activate the following deployment parameters for production environments: 

• Transpiler = The application is provided for browsers that only have ECMAScript5 support
• Polyfill = Creates workarounds for older browser versions such as Internet Explorer 11
• Minify = Compresses the JavaScript and CSS source for a minimal file size to optimize loading times 

Standard rolls 

Simplifier is delivered with new standard roles 

• SF_Administrator (This is a role for all AdminUI permissions) 
• SF_AppBuilder (This role provides the permissions for App creation) 
• SF_AppUser (This role provides the permission to execute Apps) 

• SF_Developer (This role provides the permissions to create Apps and building blocks such as Business Objects, Connectors, etc.) 
• SF_ExtAuthUser (This is a role for read-only users that are synced from an external authentication service) 

Optimized library administration 

Syntax highlighting is now also available for the inclusion of third-party libraries. This makes it easier to read the code and recognize its structure. 

Existing libraries can now also be downloaded. 

 Oracle 19c compatibility 

Simplifier now also supports the latest Oracle 19c database. 

 Security Enhancement 

The legacy route for direct execution of connectors is locked by default – in special cases this lock can still be removed in the system settings. In Release 5.5 this option will be removed completely. 

Live Preview on mobile devices 

Together with our brand new WYSIYWG UI Designer, we also offer the live preview in our simplifier mobile client (has to be activated in the developer settings. That means, that every change in the user interface will be published in real–time on your real hardware. This enables you to test your layout on different device factors and smartphone / tablet models in realtime. 

Support for Honeywell Scanners 

Our Simplifier Mobile client runs natively on Honeywell laser scanners with android operating system. This means you can use the information from the laser scanner directly in your business app without any extra interface. 

Updated Mobile APIs 

Our native mobile feature sets are updated to the latest version to give you the best native mobile experience. 

IOS 13 Support 

Our iOS Client was optimized for iOS 13 

New API for TCP socket connections 

With our new native tcp support, you can exchange data directly with other devices over ethernet or wifi interface. We use this to support external fix-mounted laser scanners on a fork-lifter for intra-logistic use case in production environments or warehouses. 

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
• Database Designer

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

1. Connect systems

In the future, for each application, you can access the data that is needed contextually to make the integration process more efficient. Standardized connectors enable you to quickly connect to any back-end system and various data sources.

2. Create user interface

Easily, quickly and intuitively create the user-friendly interface for all your applications. Use the pre-designed elements designed for this purpose and create a uniform look and feel for improved user experience.

3. Configure processes

Configure the application logic of each application using the Process Designer. Based on individual user stories, reusable application logic is encapsulated within User Stories in the Process Dashboard. Each user story can be stored individually so that you can work with several people on different stories at the same time and thus be able to create application logic collaboratively.

4. Test application

Test your application at any time in the Simplifier Mobile client or in the browser. Intermediate testing allows for faster detection of misbehavior of your application at any point in time. The Simplifier Mobile Client supports the testing process by ensuring that applications can be used across devices and that the correct responsive display of the application on each end device can be ensured.

5. Publish application

The Simplifier transport system allows you to transfer the application to your productive system quickly and easily. And all without compilation or complex deployment processes. Quickly create a transport file of the finished application – it contains all the components of your applications and can be downloaded and imported directly into your production instance. Finished! The application is now available to any authorized user.

Example Apps

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

Prerequisites

For Simplifier Configuration & App Development within Simplifier Admin Interface we recommend using Google Chrome Browser.

• for Mobile Preview, Console, Debugging and DOM Inspection use Google Developer Tools
• to inspect and debug your UI5 Application install  and use the  UI5 Inspector Chrome Extension
• For testing Applications on mobile devices download Simplifier Mobile Client available for iOS and Android
  
• Apps created with Simplifier are based on OpenUI5. As OpenUI5 is based on CSS3, HTML5, and the ECMAScript 5 (ES5) JavaScript API,
  only browsers with HTML5 capabilities are supported, please find a detailed Overview of supported Browsers and Platforms
  in the OpenUI5 Documentation
• as Simplifier is a Low Code Platform there is at least basic web technology knowledge needed to build complex applications,
  we recommend the following online courses regarding webtechnology skills:

  	Codecademy: Learn HTML
  	Codecademy: Learn CSS
  	Codecademy: Introduction to Javascript
  	OpenUI5 Documentation OpenUI5 / SAPUI5 Walkthrough Tutorial Introduction to SAP OpenUI5 Apps

   

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
• The initial login credentials are admin / admin

Use the following checkpoints for a 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

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.

Reverse Proxy Requirements

The Simplifier Server needs a typcial Reverse Proxy as standard setup.

The Reverse Proxy should provide the following services for a secure setup

• SSL Offloading
• Virus / Malware Scanning
• Web Application Firewall

Forwarded Ports:

• 443 (HTTPS)

Port 443

• HTTPS (valid certificate)
• modern, secure TLS configuration (incl. HTTP Strict Transport Security)
• HTTP2 if possible
• Header:
  • “Upgrade”: Pass from client (for WebSockets)
  • “X-Real-IP”: IP address of the client
  • “X-Forwarded-Forwarded-For”: Remote address of the client, or X-Forwarded-For Header of the parent proxy server.
  • “X-Forwarded-Proto”: Original protocol of the request (“http” or “https”)
  • CORS Headers (see below)
  • (Temporary) Redirect from “/” to either AdminUI (“/UserInterface/”) or App of choice (“/appDirect/$appName”)
  • Proxy connection/read/send Timeout to high value, e. g. 10 min
  • Maximum body size (post, put) to appropriate value, e. g. 20 MB (doesn’t have to be too big, because packets > 20 MB are transferred as single chunks)
  • Proxy forwarding to Simplifier AppServer port 8080 (if on another server, must be reachable via firewall)

CORS headers

Cross-Origin Resource Sharing (CORS) is a mechanism that uses additional HTTP headers to allow a user agent to access selected resources from a server located on a different origin (domain) than the currently used Web site. A user agent makes a cross-origin HTTP request when requesting a resource from another domain, protocol, or port than the one from which the current document originates.

The CORS mechanism supports secure cross-domain queries and data transfers between browsers and web servers. Modern browsers use CORS in an API container such as XMLHttpRequest or Fetch to minimize the risks of cross-origin HTTP requests.

For request methods’ POST’,’ GET’,’ PUT’,’ DELETE’:

Additionally for request method ‘OPTIONS’:

The following paths should be configured for routing it back to Simplifier

Docker Installation

Get Docker CE

Referenced to the official Docker instructions.

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

SET UP THE REPOSITORY

Update the apt package index:

$ sudo apt-get update

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

$ sudo apt-get install \

    apt-transport-https \

    ca-certificates \

    curl \

    software-properties-common

Add Docker’s official GPG key:

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

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

$ sudo apt-key fingerprint 0EBFCD88

pub   4096R/0EBFCD88 2017-02-22

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

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

sub   4096R/F273FCD8 2017-02-22

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

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

amd64:

$ sudo add-apt-repository \

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

   $(lsb_release -cs) \

   stable"

INSTALL DOCKER CE

Update the apt package index:

$ sudo apt-get update

Install the latest version of Docker CE:

$ sudo apt-get install docker-ce

Requirements for Remote Service applications

(On-Premise Installation)

Remote Service applications demand some additional requirements, especially on the network side. To successfully establish a connection between two clients, e.g. the Remote Service Portal, running in the browser on a Desktop machine and the Remote Service Client running on a Smart Glass, they must either reside in the same network, or a STUN-/TURN-server must be used.

The minimum requirements for using a remote service application are:

• Simplifier server and clients must either be in the same physical network segment or be connected via a virtual private network (VPN). If this requirement can’t be fulfilled, a STUN-/TURN server can be used as an intermediate communication partner.
• If you want to use a STUN-/TURN server, the following TCP and UDP ports must be open: 3478, 3479, 5349, 5350.
• Fixed domain for the server and valid certificates for this domain. Remote Service requires these certificates because it runs exclusively over HTTPS for security reasons.
• If you plan to use remote service over a cellular network, be sure that your provider allows these services in your contract. In case of Deutsche Telekom, this means that option “Voice over IP” must be enabled.

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

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.

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 2.2 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 4 before}

Features and supported operating systems

• • Auto-Login Functionality
  • OAuth Login
  • Developer Mode
  • App Autostart

See the full-featured list of supported operating systems:

Live Debugging with Chrome DevTools

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

Enter chrome://inspect into your Chrome browser.

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

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

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

Simulate a Mobile Device

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

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

Simplifier Mobile Client

Simplifier provides a Universal Mobile Client which uses an App-in-App Concept to run UI5 Applications as hybrid Apps on mobile Devices.

• Login via Fingerprint, Face ID or QR-Code possible
• Access to all Applications available on the Simplifier Instance, based on roles and rights
• Rapid Deployment and Over-the-Air Updates of Applications
• Access to all device specific native functions and additional mobile-features

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

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: 

new

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

deprecated

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

Simplifier Client API

All external programs, business applications and the mobile client access Simplifier via Simplifier Client API.

Simplifier Client API is documented by Swagger and can be accessed by opening the URL:

https://<simplifierbaseurl>/client/2.0/api-docs/

A detailed documentation of the client API is displayed and you can try out the API using the tools built into Swagger. All changes in the API are automatically transferred to the documentation.

Note: Make sure that you have select HTTPS under schemes.

Authentication

URL: https://<simplifierbaseurl>/genToken/

Method: POST

postBody:

{"user": "<username>", "pass": "<password>"}

Example Response:

{"result": "<simplifierToken>", "success": true}

Application

Dependencies

Business Object

Execution

Connector

Download

Library

Mobile Client

Example

Plugin

Simplifier

Settings

Server Settings | Password Settings | License | Authentication | Messages | Log | Server Environment

As a user that is defined as an admin by the corresponding role, you can hit the settings button by clicking on your user profile name on the top right corner. Within the settings panel, you can define several settings: Server, Password, License, Authentication, Messages, Log and Server Environment. In addition to the settings, you can also send an error report, change the language (German or English) or the design (light or dark) to set or unset the dark mode. You can also view the version info of your Simplifier instance or log out.

Server Settings

The Server settings control your session. At the subtitle Authentication token, you can set the lifetime of the authentication token and its checking interval. If you set the authentication token to active, the checking interval to 10 seconds and the maximum lifetime of the authentication token to 3600 seconds, that means that every 10 seconds it will be checked if you are inactive. If you are inactive for about 3600 seconds, you will be automatically logged out.

Define the email settings within the SMTP Settings.

SMTP Port	Specify the port of the outgoing mail server, e.g. 587
Authentication required	If activated, a user/password authentication from the outgoing mail server is required
Encrypted with TLS	If activated, the transmission is encrypted by TLS
Sender E-Mail	Enter the sender’s email address, e.g. no-reply@simplifier.io
Sender	Specify the name of the sender to be displayed
Password	Set a secure password

You can switch on Experimental Features. It’s not guaranteed that these features work properly.

Password Settings

The Password settings specify the password policy for the users.

License

The License settings offer information about the current license you use. If your license expires, you can update it here. Simply copy and paste the license key in the corresponding field.

Authentication

Take a look at Authentication Settings and the following subpages.

Messages

The Message settings allow you to store system messages, which are transmitted to all logged-in users, e.g. if you want to inform them about maintenance work. With corresponding rights (assigned role “System Messages”), you can add a validity date. The messages can be written in HTML. As soon as a message is stored, it is pushed to all user. A user who logs in later receive the message as well. The message is displayed as an overlay and must be closed manually.

Log

Within the settings, you find the settings for the logs. You can define per categories, which log level will write a log in the Logs & Monitoring. Choose from the following categories: Debug Info Warn Error Critical Use the Log Archive Settings to specify the time period for archiving the logs. It runs every day at 3 a. m. when it’s activated.

Server Environment

Take a look at Server Environment.

Authentication

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.

LDAP

LDAP is based on the client-server model and is used for directory services. It describes the communication between the LDAP client and the directory server. Object-related data, such as personal data or system configurations, can be read from such a directory.

General Settings

Mechanism Settings

SAP Single Sign On via SOAP

You can use the SOAP service to authenticate via an SAP system and get an SSO2 Token for SAP SOAP web services. The user synchronization is done by the Simplifier AG own SAP RFC Module -ITIZ-_USER_READ or with a different SOAP-Webservice, which calls the standard SAP-Module BAPI_GET_USER_DETAIL.

General Settings

Mechanism Settings

SAP Single Sign On via RFC

You can use the RFC service to authenticate via an SAP system and get an SSO2 Token for SAP RFC web services. The user synchronization is done by the standard SAP-Module BAPI_GET_USER_DETAIL.

General Settings

Mechanism Settings

Active Directory

Simplifier is able to sync users of Active Directories, like users from other LDAP sources.

General Settings

Mechanism Settings

Open Authorization (OAuth)

OAuth (Open Authorization) is an open standard for token-based authentication and authorization on the Internet.

To set OAuth as authentication, make sure you have administrator rights.

After you have logged in as usual in the login mask with your user credentials, click on your name in the upper right corner and then on the settings.

Switch to the Authentication tab in the upper toolbar.

To add a new authentication mechanism, click on the plus icon in the upper right corner.

General Settings

Mechanism Settings

User Management

The User Management module lets you define many different parameters for users and the roles they take.
The QR-Code generator for easy accessing, especially with smart glasses, is also located here.

The following table explains the different User Management functions and their meanings:

User Overview – Create a new user

The user overview display all users of your own Simplifier instance. Aside from the first name and last name you also can see the username and the expiry date of the user. Four icons on the left side allow you to see details of the user, edit or delete the user (only when your role has the permissions) and see if the user has been blocked.

To add a new user click on the “+” icon on the right above the user table. Within the User Details, fill out all required user information and assign a role or group for the user.

After creating a user, a one-time-link via email will be sent to the created user. After email activation via the link, a new password can be set.

It is also possible to assign different attributes to a user.

Role Overview

The section Role Overview defines permissions for the users. Here you can configure roles that can be applied to your users in order to permit or restrict certain actions, like administering applications and users or allow the use of special applications and restrict the use of others. Usually, there is one administrator-role that is allowed to use all features and functions of Simplifier.

Create a new role by clicking on the plus icon. To add a permission, use the selection helper on the right and choose the needed permission category. To enable or disable single permission, click on the checkbox in the corresponding column. Finally, assign the role to existing users. Hit the save button to finish the role creation or the update.

Within the right tab, you can add a user to the role. Use the selector for this.

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 to the group, click into the ‘Add User to Group’ Field and search for specific usernames. Mark (optional) several users and click OK to add them to the group.

QR Login-Generator

The QR Login-Generator lets you generate your individual QR code for login purposes especially for wearable devices without a keyboard. You don’t need to type in your credentials anymore, just scan the QR code and you are logged in on your instance. Especially when using smart glasses, this feature is comfortable as it takes just a quick scan to enter Server URL, username and password without typing.

To generate such a QR code, go to the tile Users on the Simplifier dashboard and switch then to the tab QR Generator in the user overview.

You have to enter the required user with password and the Server URL. By default, this is already filled in. Generate the login code and now you can log in to other devices easily and quickly by scanning the QR code.

Applications

Simplifier transforms your business process into a configured business application for

• Web Portals for Desktop-Browsers 
• Mobile Phones and Tablets
• Wearables Devices like Smartwatches and Glasses

Applications run on any device because it is generated on common open standard technology leveraging OpenUI5 / SAPUI5 

Overview

By clicking on the Applications tile, you will be lead to the overview. At default, there you will see a table with all the 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.

App	It’s the name of the application.
Created	The name of the person who has created the application (with date and time).
Last Edited	The name of the person who last edited the application (with date and time).
Version	It’s the version number of the releases.
Customization Ratio	After deploying an application, a code metric is available in the overview. It shows the generated lines of code and a comparison to the lines of code written by the customizer in events and script activities.
Framework	The framework – OpenUI5.
Actions	Edit application, copy application, show releases, edit meta-resources, preview and delete the application.

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

Read how to create a new application.

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

Create your first Application

To create a new application, click on the Applications tile.

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.

Widgets

A widget represents a specific element in the user interface (e.g. checkbox, button or login screen, etc).

To customize a widget, click on the Applications tile in the Simplifier dashboard and choose the Widgets tab.

Within the overview, you can edit, take a look at the details, delete or copy a widget or take a look at the description, category, tags, and set it to deprecated or not.

Press the ‘+’ button on the right to add a new one.

Add a name and select the OpenUI5 version.

By clicking OK you will be forwarded to the Widget Customizer.  On the left side are three different tabs: General, Template and Script.

General

In the tab General, you find the general information like Name, Version, Category, and Description. You can add tags or set the widget to deprecated. Deprecated widgets are no longer displayed in the UI Designer. Deprecated widgets that were used before they were marked as deprecated are still displayed within the application content. The application will continue to be saved and deployed without issues or warnings and runs as before. Add an icon to the widget by uploading it. You can delete it at any time.

Template

Enter the widget type in the tab Template – take a look at the constructor details in its API reference. It must match the name of the UI5 control. Use the wizard to automatically extract the widget data.
Choose a framework – OpenUI5 or SapUI5
By clicking on Next, the template for the widget is generated as well as the properties, events, and aggregations.

Script

The script of the widget is generated automatically if you use the widget assistant.

After hitting the Save button, you’ve successfully created or edited a widget.

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

UI Designer

Create and design the user interface of an application with the UI Designer. The interface of the UI Designer is divided into four sections:

Screens & Widgets

You have several options in the upper menu bar to navigate to specific features:

On the right you have the following options: 

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.

By clicking on Open, it opens a new browser tab. Every time you deploy your application, the browser tab reloads automatically.

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.

Assets

Use Assets to upload files like documents, images, videos, 3D models or office documents to an application. It can be found under the tab Other.

It is possible to upload the following file types:

• Images like .PNG, .TIFF, .JPEG or .BMP files
• JavaScript for extending an 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 Browse button. You can reference to the path in the properties of a widget.

In the following screenshot, the path of the image logo.png is img/logo.png.

To insert e.g. an uploaded image into the user interface of your application, copy the path of it and paste it into the source field (src) in the properties of a widget.

CSS Editor

Please keep in mind that CSS statements are mainly used for design purposes, not for the basic layout to maintain the responsiveness of UI5.

If you want to learn more about CSS, check out the tutorials of the w3 schools or Codecademy.

Language

Applications can be localized easily by adding language files (.po-format) to the application.

By default, the language depends on the user environment, browser or device language, however, a fallback language should still be defined.

For the translation of the individual applications, .po files are used in Simplifier. These can be viewed, up- and downloaded via Language under the Other tab.

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

It’s the best way to edit the downloaded file in a POEditor.

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

To upload the file to the application, add it via the plus. Select the language and upload the PO-File.

In order to avoid cache problems, rename the file before uploading.

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

To change the language of an application at runtime, the following script can be inserted in the Process Designer or browser console:

Sap.ui.getCore().getConfiguration().setLanguage(“en”)

Note: “en” can be replaced by the desired abbreviation.

To start an application with a specific language, add the query parameter sap-language=en to the application URL, e.g.

https://<simplifierBaseUrl>/appDirect/<appName>/index.html?sap-language=en

Libraries

Within the Libraries you get an overview of all assigned libraries that are currently used in your application.

You can assign libraries to your application in the UI Designer. With the “+” you can add an existing library to your application. The icon left computes all dependent libraries of the application itself and its widgets as well as all transitive dependent libraries. Take a look at Integration of external Libraries for more information.

Theming

To create themes for Simplifier applications, we recommend using the UI5 Theme Designer.

Export the theme and make sure that in the dialog, you set the checkbox beside Source files + CSS Resources.

You can then upload the theme to your application to give it a specific look corresponding to your corporate design.

To activate the theme, you have to select the Instances.

Then you can switch in the UI Designer between the themes to select the one you need.

Manage Screens

A screen represents one single user interface page and can contain several widgets.

When you create a new application, it does not have a screen yet. Add a screen by clicking Add Screen.

To rename screens change the ID within the properties section on the right. Use the Description field to comment on the screen. This helps to identify the purpose of the screen later.

Widget Usage

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, select the OpenUI5 version. Via the filter, only the compatible widgets matching the stored UI5 version of the application are displayed. 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 selected screen.

Sort Widgets in the right order

Use the arrow keys to structure the widgets in the screen content tree into a hierarchy, or alternatively use WASD on your keyboard.

You can also use the arrow keys to structure the widgets in the screen content tree into a hierarchy, or alternatively use WASD on your keyboard (the widget needs to be selected).

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 screen content tree 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.

Every widget has properties to configure how the widget behaves. On the left are an example of the properties of a button widget.

Icon Explorer

	Use the icon explorer to add icons to widgets that have an image or icon as property.
	You can also add a font to an application that contains icons to use in the icon explorer. Images uploaded under Assets can also be selected.

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.

Process Dashboard and Designer

Process Dashboard | Process Designer

The Process Designer enables defining process flows as the result of an event in an intuitive, graphical way.

The tab for it is located next to the (UI) Designer.

By that, it follows the classic workflow of creating an application: First, you design the user interface for the application, followed by the definition of the workflow between these elements in the Process Designer.

Process Dashboard

By clicking on the tab Process, you get to the Process Dashboard.

The Process Dashboard is divided into different user stories that can be saved individually, so it is possible to work on it simultaneously with several people.

After deploying the entire application in the UI Designer or Process Designer, all user stories are merged into one.

To add a new user story, drag Story (on the left) into the middle. It opens a pop-up to define the Story Name (mandatory), set an External link with the Link text and define a Story Description.

Edit or delete an existing user story with the equivalent icons. The user stories are ordered alphabetically (or by number – if used). You can sort the user stories in ascending or descending order with the icons on the right.

By double clicking on the whole tile of a user story or clicking on the edit icon, you are forwarded to the Process Designer to work on the currently user story.

If another user is editing the user story, it is displayed by a small avatar image of the user in the user story tile. By mouse over such an avatar image, a tooltip with the user’s login name is displayed.

Similarly, a small button in the upper left corner in the Process Designer itself displays users who are editing the same user story. The color of the button turns to red when another user starts editing the same user story. To view all editors, click on the button to open a pop-up. It displays the avatar screen and the user’s login name. The colors depend on the user’s login name, so each user is given an individual color. The list of editors will always be up to date so you will get an instant response when someone starts editing the same user story.

 Deep Search

It is possible to search within the Process Dashboard for elements.

You can search for General, Activities and elements In Mappings.

Note: Auto Fields cannot be found by name, only by the expression they represent.

Live search for user story names
Search for activities

As result, all activities that match the search term are highlighted in green within the Process Designer.

Process Designer

The main view of the Process Designer is split into three main sections:

1. The selection of the building blocks on the left: Event, Logic, Action, Data Object and Module. The activities are subdivided again. Take a look at the subitems of this page for more details.
2. The drawing area in the center.
3. On the right side, you can see the current user story, edit and save it. In addition, you can configure the current selected shape.

Process Documentation

For a better understanding of the application creation, use the Process Documentation. You can open it in the Process Dashboard as well as in the Process Designer itself.
It opens a dialog, that displays a textual documentation of the application process in Markdown format. The description of the user stories as well as of the shapes are added into the documentation automatically. So make sure to use the description whereever possible.

Dynamic Process Settings

The toolbar within the Process Designer gives you control of the appearance of your process.

Cut, Copy, Paste and Delete Shapes

You can cut, copy, paste and delete shapes within the Process Designer. Therefore you have to click on the appropriate icons on the top right of the canvas.

Cut	With the left icon, you can cut your selected shapes from the canvas. So the shapes including connections and mappings of the configured shapes were copied and dropped.
Copy	With the second icon from the left, you can copy the selected shapes including the connections and mappings from the canvas.
Paste	With the third icon from the left, you can paste your copied (or cut) shapes including all connections and mappings. They appear slightly offset from the copied or cut shapes.
Delete	With the right icon, you can delete your selected shapes. You can also do this with the delete key on your keyboard.

Visual Feedback for Process Errors

If you have any errors in your process, you will receive feedback about that. Every error will be displayed within the process. The corresponding activity will be highlighted in red and a tooltip will be shown by hovering over it.

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 side and drag & drop it into the drawing area in the center.
By double-clicking on the shape, the event selection assistant opens. You can also open it by clicking on the right side 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 current user story, select one of the Events under the tab Subscribe Event.

Publish Custom Events

To use an event in other user stories, create a new Custom Event on the Publish Event tab.
A shortcut for creating Custom Events is located in the upper right corner.

Subscribe to Custom Events

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.

Logic

Condition | Iterator | Script

Condition

Conditions allow you to define the process flow dependent on the evaluation of certain expressions.

In such an expression, you can compare auto fields, variables, a current value of a widget, or a given constant with each other and use the result to decide whether the process continues in one direction or the other.

Alternatively, you may decide to continue the process only if a condition is true and decide to leave out the alternative, which will stop the process at that point.

Double-clicking on the shape adds a new condition. Alternatively, click on the plus icon on the right.

An AND condition is created by default.

Toggle between AND
and OR (not XOR) condition using the toggle switch.

Select the operator of the condition by the drop-down.
==	value1  is equal to value2 (not checking the data type, only the value)
!=	value1 is not equal to value2
<	value1 is less value2
>	value1 is greater than value2
<=	value1 is less or equal to value2
>=	value1 is greater or equal to value2
isSet	variable has a value
isNotSet	variable has not a value

Iterator

The iterator selection helper can be called by opening the mapping dialog on the right side. The mapping dialog can also be opened by double-clicking the shape.

Drag and drop the parameter to the drawing area in the center. You can select the collection to be iterated by double-clicking on the parameter.

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

Script

The Script element allows you to integrate your own JavaScript snippet. It is activated by the previous event.

It shows a preview of the JavaScript full screen and its (optional) description on the right side. You can also enter code in this area, the changes will be saved and also transferred in full screen.

The full screen view is opened by double-clicking on the shape or by clicking on the corresponding icon .

Pretty Print

You can prettify JavaScript code with just one click.

By clicking on the corresponding symbol (Format Code) your code will be simply prettified.

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. Set that the navigation should navigate back, or choose between several transitions: Slide, None, Fade or Flip.

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 to the Event (subscribe).
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.

Mobile Action

Behaviour

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

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

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.

This mobile action will trigger a native notification.
The notification will be displayed on your mobile device.

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

Define how many milliseconds the mobile device should vibrate.

Connectivity

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.

Information

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. Connect it with the appropriate widget.

Media

Determine how many pictures should be taken.

Determine how many videos should be taken and set the duration (default 60 seconds).

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

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

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

Parameter	Data Type	Valid Values
Meter appearance	String	see table below
Number of counts	Integer	1, 2 (from the dropdown)
Integer digits	Integer/String	AUTO, 1-n
Fraction digits	Integer/String	AUTO, 1-n

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

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.

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.

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 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 that 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 default value, 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.

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.

Security

Assignment

You can assign roles to apps, which is the first step in order to have anonymous logins.

All assigned roles to the app are imported and exported by the transport system. By default, it is not allowed for anonymous users to execute data operations in the app.

Allowing anonymous users must be allowed with explicit approval. For this you have to activate the checkbox next to “Allow anonymous users”. The plus icon will then be available.
To assign a role, click the plus icon. A pop-up appears in which you can select a role. Click on it to assign it directly.
After assigning a role, your changes are automatically saved.

You can also remove roles. All you have to do is click on the corresponding icon.

Runtime

When you navigate to an application, an authentication of the app for accessing an application token is triggered. All roles assigned to the app are linked to the application token. This feature allows anonymous users to e.g. execute connectors.

As a further security aspect, the app needs to provide security functionality in order to obtain an application token.

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 “Libraries”

Standard Equipment

Simplifier provides the following library by default:

Add a new Library

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

Now you can fill in the following parameter:

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

Integration of Libraries – addBeforeInitHandler

addBeforeInitHandler

Integration of Libraries – addAfterInitHandler

addAfterInitHandler

Offline Applications

You can react on losing the connection of your application/device in the Process Designer. There are two default events added in every application: onDeviceGoesOnline and onDeviceGoesOffline.

The auto field type “Device” holds the current connection state – characteristic: online. How to create a new auto field, you can see here.
It can be used in every mapping and also in conditions.

Application Properties and Releases

Application Properties

Open Application Properties and Releases by clicking on the application name in the upper left corner.

Application Properties

This opens a new dialog box in which you can see the application properties directly.

Application Name	The name of the application.
sap.m.App	The specified expression is used as ID for the application envelope.
Description	The description is displayed in the application overview list.
Splash-Logo	The selected image is used as logo for the initial loading of the application.
Busy-Logo	The selected image is used as a logo for asynchronous calls within the application (e.g. for connector calls or methods of business objects).
Author	Creator of the application.
Date	Creation date of the application.

Deploy Configuration

In the lower part of the window, you can activate the following deployment parameters for production environments:

ECMA 5	Transforms source code to ECMA5 standard.
Minify	Minifies source code to reduce download time.
Polyfill	Adds additional polyfill functions to reach full ECMA5 compatibility

Releases

By switching to the tab Release, you see an overview of all created releases of this application.

Use the button to the right of the entry to display the full release notes.

Create new Release

At the bottom right you can create a new release by clicking on New.
There you can add the Release Notes. By clicking on Create, a new transport for this application is generated.

Business Objects

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

Create server-side Business Objects

Business objects are managed in the tile ‘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 and define 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 and Manage Functions

The logic of a business object is implemented via script functions. Each business object can hold as many functions as wanted. Click on the ‘Edit functions’ icon. 

You are forwarded to the overview of the functions of the business object. There you can go to the function details, edit a function, test it, copy or delete it. 

To add a new function, click on the ‘+’.

Creating a function 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 (ctrl+z)
• redo (ctrl+y)
• search (ctrl+f)
• search and replace
• format code
• validate code
• settings (ctrl+,)
• fullscreen

This example reads a name that 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 function 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 corresponding 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.

Server-Side – Access Connectors

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

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

Example:

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

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

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

Example:

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

Server-Side – Access Plugins

In order to call a plugin from your business object you need to add the plugin to your business object first (see Create Server Side Business Objects) and afterwards access it within a Business Object Function using this syntax:

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

Example:

var repos = Simplifier.Plugin.contentRepoPlugin.listRepos(); 
var newRepo = Simplifier.Plugin.contentRepoPlugin.createRepo({name: "MyRepo"}); 
Simplifier.Plugin.contentRepoPlugin.updateRepo("{\"id\": 15}");

Server-Side – Access other Business Objects

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

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

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

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

Example:

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

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

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

var noArgsResult = Simplifier.CurrentBusinessObject.methodWithoutArgs();

Test Business Object Functions

You can test the function by clicking on the ‘Test Function’ icon in the functions overview of a business object or click on ‘Save & Test’ within the creation of a function.

The upcoming dialog provides an input field for all input parameters, that do not have a constant value.

After entering the test values, click on the ‘Test’ button. It runs the template and displays the result in JSON format.

A history entry is created for each test and displayed in a closable panel on the left side of the dialog. Parameters from a current template can be imported into the next test by clicking the corresponding icon of the history entry.

History entries can be deleted by pressing the trash icon. The history entries also display detailed error messages if a call was unsuccessful (hover over the info symbol).

Generate Data Type

You can automatically create simple or complex data types in the test dialog by pressing the button Generate data type after a successful test.

Access Business Object via Script

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

Connectors

Connectors are the interface between a backend system and Simplifier to communicate with each other. They consist of at least one connector call.

Connector	Addresses a specific backend system (like SAP, or Database, etc.)
Connector Call	Leads a connector into action and contains input and output parameters

---

Standardized Connectors in Simplifier

Connector Type	Description
SOAP	Use the SOAP connector to access a Simple Object Access Protocol based on HTTP and XML Format.
REST	The REST (REpresentational State Transfer) connector is used for HTTP REST Services. The architecture uses standardized operations (GET, PUT, POST, DELETE) on web services. REST API is an alternative to other interfaces like SOAP. However, REST itself is neither protocol nor standard.
SQL	With the SQL (Structured Query Language) connector, SQL statements are executed in a database schema, to request or edit based databases.
OPC/UA	The OPC/UA (Open Platform Communications Unified Architecture) connector accesses to an OPC-UA server and performs READ/WRITE/SUBSCRIBE operations.
SAP RFC	The SAP RFC (SAP Remote Function Call) connector is based on standard JCo SAP RFC to call functions in remote systems.
MQTT	MQTT (Message Queuing Telemetry Transport) is an open message protocol for machine-to-machine communication (M2M) that allows telemetry data to be transmitted as messages between devices, despite high delays or limited networks. This connector acts as a client and can publish or subscribe messages from an MQTT server (broker).
Push	The Push connector sends push notifications over WebSockets directly to Simplifier Clients or Simplifier Browser Apps without using Google or Apple’s Cloud Services to support data protection and privacy.
CSV	Use the CSV (Comma-separated values) connector to read and/or write comma-separated files on a local file store.
OData V2	OData (Open Data Protocol) is an open protocol based on HTTP for data access to enable CRUD operations. It enables the creation of REST-based data services to be published and edited by Web clients using simple HTTP messages.
Email	Use the Email connector to send emails over SMTP (Simple Mail Transfer Protocol) with or without SSL Encryption.
Logging	The Logging connector transfers the Simplifier application logs to a central monitoring tool/logwatch.
Proxy	The Proxy Connector allows the usage of any HTTP services that are not based on specific protocol architectures such as REST, SOAP or OData.

Create and Manage Connectors

Connector Type | LoginMethod | 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

Endpoints

After you have created the connector information, add your endpoints by clicking the plus icon.

You can set several, but at least one is required.

You can switch between endpoints and customize the Specific Parameters. Each connector has specific parameters that depend on the properties of the communication protocol. Read more on the following pages.

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 Username/Password, Single-Sign-On, OAuth2 and SAML2.0.

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

Edit Calls

By clicking on Edit calls, you directly jump to the overview of connector calls.

Copy a Connector

You can copy an existing connector by clicking on Copy connector.

Usage of Connector

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

It opens a pop-up that displays all artifacts that use the connector:

By clicking on an entry, you jump directly into the item.

REST Connector

Connector endpoint

The URL defines the REST endpoint.

Take a look at REST Connector Calls to define the connector calls for the connector.

Push Notification Connector

With the Push Notification Connector, you are able to send a notification to all logged in users who have the selected role or are in the selected group on the Simplifier instance.

Select via the value helper the roles and/or the groups to which you want to send a message in the connector configuration mask. Unfortunately, a multi-select is not yet possible and you have to select several roles in succession.

To create the connector calls for this connector, take a look at Push Notification Connector Calls.

How to use a Push Connector in a REST-Client (e.g. the Advanced Rest-Client)

Step 1: You need a Token

Request Type: POST
Content Type: application/json
Payload:
{"user":"<username>", "pass": "<password>"}

Returns:
{
"result": "someprettylongtoken",
"success": true
}

XHR Type: POST
Content Type: application/json
Header: SimplifierToken
Payload:
{
 "connectorName" : "<connector_name>",
 "json": {
 "msg" : "<some_string>"
 }
}

Sample:

{
 "connectorName" : "Push",
 "json": {
 "msg" : "test"
 }
}

• Example 2: Send an order as push notification

XHR Type: POST 
Content Type: application/json 
Header: SimplifierToken 
Payload: 
{  
  "connectorName" : "<connector_name>",  
  "json": {  
  "msg": "{"order_id":"<NotificationMessage> <header> <message_id>  
1234567890</message_id><created>date_time</created> <request> <site>9999</site> // Asset Nr.<resource>Station_1</resource> // Ressource/ Workplace<order>variant_123</order> // Order-/ SFC Nr.<variant>variant_123</variant> // Variant Nr.<assy>assembly_123</assy> // Assembly Group Nr. <time>180</time> // Time allowance </request> </header> </NotificationMessage>"}"
}
}

 

Take a look at Push Notification Connector Calls.

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>"
]
}

Send message via Script

An object can be passed as a message by converting it into a JSON string:

JSON.stringify({propertyOne: 'abc', propertyTwo: 5})

var lo_payload = {
'msg:'<requested message>'
};

function successCallback(po_result) {
//Enter any code that will be executed in case of success
}

function errorCallback(po_result) {
//Enter any code that will be executed in case of error
}

this.callConnector("<connector-name>", lo_payload, successCallback, true, true, errorCallback);

Send message via Process Dashboard

To send messages via the Process Dashboard, you need to take the following steps:

1. Drag the Asynchronous Data Object activity into the drawing area.
2. Select the appropriate connector and the connector call for sending the message.
3. Fill the parameters in the input mapping.

Receive message via Process Dashboard

To receive messages via the Process Dashboard, you need to perform the following steps:

1. Drag the Asynchronous Data Object into the drawing area.
2. Select the appropriate connector and the connector call for receiving the message.
3. You can continue with or without script.

Continue with script:

var lv_msg = data.data.msg;

data.data.msg must eventually be adapted to the output parameter specified in the connector call. lv_msg is the received message (type String, can be e.g. a JSON string, then parse to get object:

JSON.parse(data.data.msg)

It returns the object:

{propertyOne: 'abc', propertyTwo: 5}

Continue without script:

Use the output mapping to map received messages, e. g. to a widget or to save it in a variable.

SOAP Connector

WSDL URL

The URL to the Web Service Description Language Document (WSDL) of the SOAP Service. Please don’t mix up with the SOAP Service Endpoint.

You can refresh the WSDL, show parsed bindings or download the WSDL with the according buttons.

Take a look at SOAP Connector Calls.

CSV Connector

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

If you want to provide the files by the Html5 uploader you have to specify the path to the uploads directory. By default the path to the upload directory is

Delimiter

Delimiter of the columns that separate 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

The 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 that contain the delimiter are put in quotes. This setting is ignored when reading.

Go to CSV Connector Calls to configure the corresponding Calls.

MQTT Connector

How to use a MQTT Connector in a REST-Client

You can choose between 2 operations: PUBLISH and SUBSCRIBE.

Build the payload like this: