Data source configuration

The 446 Plattform provides a way to add different data sources to a ticket schema. Connect (external) databases and execute commands via regular expressions directly in an input field.

 

Add a new data source in Ticket Schemas by selecting the 'Data sources' tab and hitting the 'Add data source' label.

Chapters:

  1. Configuration of a Oledb data source

  2. Configuration of a User/group custom property data source

  3. Configuration of a SqlClient data source

  4. Configuration of a XML/HTTP data source

  5. Intended use of data sources

  6. Database queries at Plug-ins

 

  1. Configuration of a Oledb data source

ticket schema data source type oledb

Connection string: Enter the OLEDB connection credentials here.

Warning:

There will be an alert message displayed when using the deprecated providers 'SQLOLEDB' and 'SQLNCLI'.

Instead use 'MSOLEDBSQL' which is recommended by Microsoft. More information is to be found in Database server.

Query: In the ticket wizard, only one column can be displayed later on in the selection list resulting from this input window. The content of the first column is used for the text and the value of the underlying ticket field. For an example of the query, see Database query.

 

  1. Configuration of a User/group custom property data source

Custom property: Enter the property of a user or a group here.

User/Group: Here you can choose if the property should be applied to users or a group.

 

  1. Configuration of a SqlClient data source

Connection string: define the sql connection string here.

Tip:

Use the predefined Sharp-Expressions and enter the connection credentials in Master Data

Query: the same options like in OLEDB analogue.

 

  1. Configuration of a XML/HTTP data source

XML schema: A predefined XML In computing, Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable through use of tags that can be created and defined by users. template you can adjust at your will.

URL: The URL A Uniform Resource Locator, colloquially termed a web address, is a reference to a web resource that specifies its location on a computer network and a mechanism for retrieving it. A URL is a specific type of Uniform Resource Identifier, although many people use the two terms interchangeably. (Uniform Resource Locator) to be accessed to process the query can be specified.

Arguments: The arguments expected there can be entered in various forms.

XPath: The XML path for filtering the desired result has to be entered.

ID Element: Denotes a distinct ID that will be used as such in the resulting selection box.

Text element: Is the XML element containing the text to be displayed in the selection box.

Autocompletition: The option works analogously to the one in the OLEDB query.

In the arguments, a placeholder can be used as well, which will be replaced by the user’s input. This placeholder is {dynamic}.

 

  1. Intended use of data sources

For example by adding a data source to a ticket schema it is possible to define this source as connection type for the input field Data source query of the Ticket Wizard Designer.

 

  1. Database queries at Plug-ins

With data sources available you are able to configure the following Workflow A workflow is a defined sequence of activities that a workflow item must go through. Plug-ins In computing, a plug-in (or plugin, add-in, addin, add-on, addon, or extension) is a software component that adds a specific feature to an existing computer program. When a program supports plug-ins, it enables customization. Here: Plug-ins are special workflow activities that enable the user to display or model processes in the Workflow Designer and adapt these processes by configuring the plug-ins accordingly. for automatic SQL statements in a Workflow: