xAPPnow LOW CODE PLATFORM - User Manual 

Still no account yet?
×

Backend Service Model Elements

 
 
The Backend Service Model of the xAPPnow Low Code platform provides the following elements.
 
  • Server Script - A script element provides the possibility to structure implementation scripts visually.
  • Submodel - Use this element to reference a submodel of a Backend Service Model.
  • DB Connector - Use this element to execute DB queries by no-code.
  • DB Transaction Connector - Use this element to handle multiple queries in a single transaction.
  • REST API Connector - Use this REST API Connector element to integrate with external systems by no-code.
  • CMIS Connector - Use this connector to manage documents.
  • CIFS Connector - This element provides file and directory handling by no-code.
  • Process Connector - This element easily handles the integration with business processes, like start a process instance and send or receive messages.
  • Word Connector - This element allows to generate a word document or PDF based on placeholders.
  • Excel Connector - Use this element to manage Excel files by no-code.
  • PDF Connector - Use this element to manage PDF files by no-code.
  • Email Connector - Use this connector to send email and fetch emails.
  • Push Notification - Use this connector to push notifications.
  • ESB Connector - Use this connector to integrate different systems using message queues.
  • Kafka Connector - Use this connector to connect to an Apache Server.
  • Exclusive Gateway - Use an exclusive gateway element to structure implementation scripts.
  • Start Event - A service model must contain one start event element.
  • Link Events - Use Link Event elements as an alternative to a sequence flow to enhance the model structure and to avoid crossing flows for a better readability of complex flows.
  • End Events - A server service model can be terminated by a normal end event or by a business error end event or technical error end event
     
Backend Service Model Elements
 
 
Additionally, the Service model contains the standard General Elements (Link, Image and Comment Elements).
 
1

Server Script

1. Server Script
A server script element provides the possibility to structure implementation scripts visually.
2

Submodel

2. Submodel
Use this element to reference a submodel of a Server Service Model.
3

DB Connector

3. DB Connector
Use this element to execute DB queries by no-code.
4

DB Transaction Connector

4. DB Transaction Connector
Use this element to handle multiple queries in a single transaction.
5

REST API Connector

5. REST API Connector
Use this REST API Connector element to integrate with external systems by no-code.
A REST API Connector references the service method specification of a Service Integration Model.
6

CMIS Connector

6. CMIS Connector
Use this connector to manage documents.
7

CIFS Connector

7. CIFS Connector
This element provides file and directory handling by no-code.
8

Process Connector

8. Process Connector
This element easily handles the integration with business processes, like start a process instance and send or receive messages by no-code.
9

Word Connector

9. Word Connector
This element allows to generate a word document or PDF based on placeholders.
10

Excel Connector

10. Excel Connector
Use this element to manage Excel files by no-code.
11

PDF Connector

11. PDF Connector
Use this element to manage PDF files by no-code.
12

Email Connector

12. Email Connector
Use this connector to send email and fetch emails.
13

Push Notification

13. Push Notification
Use this connector to push notifications.
14

ESB Connector

14. ESB Connector
Use this connector to integrate different systems using message queues.
15

Kafka Connector

15. Kafka Connector
Use this connector to connect to Kafka Server and subscribe to topics to get messages.
16

Exclusive Gateway

16. Exclusive Gateway
Use a gateway element to structure implementation scripts by low-code.
17

Start Event

17. Start Event
A service model must contain one start event element.
18

Link Events

18. Link Events
Use Link Event elements as an alternative to a sequence flow to enhance the model structure and to avoid crossing flows for a better readability of complex flows.
19

End Events

19. End Events
A service model contains one or multiple end events.
A server service model can be terminated by a normal end event or by a business error end event or technical error end event (see Connector - Error handling).