Page tree
Skip to end of metadata
Go to start of metadata

This article describes the available providers in Nexus Service Station along with their parameters.

Expand/Collapse All

 Standard provider

The Standard Provider is a local provider which persists data to file.

Parameter

Possible Values

Mandatory

Description

photo archive

An absolute path

No

An absolute path to the folder in which photos should be saved, defaults to “photos”

signature archive

An absolute path

No

An absolute path to the folder in which signatures should be saved, defaults to “signatures”

photo format

<file_name>.<file_extension>

No

The file name format which should be used to save photos. User model attributes can be used within curly brackets (e.g. {<person_attribute>}), defaults to “{person_ssn}.jpg”

signature format

<file_name>.<file_extension>

No

The file name format which should be used to save signatures. User model attributes can be used within curly brackets (e.g. {<person_attribute>}), defaults to “{person_ssn}.jpg”

ssn format

A valid SSN format

No

The SSN format to use, defaults to “SwedishLongWithDash”

 SSN formats
  • None
  • SwedishShort
  • SwedishShortWithDash
  • SwedishLong
  • SwedishLongWithDash
 IDC provider

The IDC provider requires, and persists data to, IDC.

 DB provider

The database provider persists data to an MS SQL database.

Parameter

Possible Values

Mandatory

Description

connection string

A valid connection string with DB server and DB name

Yes

Provides the connection string to the database server and database name which should be used by this provider

photo archive

An absolute path

Only if photos should be saved to file as well as DB

An absolute path to the folder in which photos should be saved

signature archive

An absolute path

Only if signatures should be saved to file as well as DB

An absolute path to the folder in which signatures should be saved

photo format

<file_name>.<file_extension>

Only if photos should be saved to file as well as DB

The file name format which should be used to save photos. User model attributes can be used within curly brackets (for example, {<person_attribute>})

signature format

<file_name>.<file_extension>

Only if signatures should be saved to file as well as DB

The file name format which should be used to save signatures. User model attributes can be used within curly brackets (for example, {<person_attribute>})

ssn format

A valid SSN format, see Standard provider.

No

The SSN format to use, defaults to “SwedishLongWithDash”

Database column parameters

In a separate configuration element named <userDatabaseTable> it is required to specify which user attributes should be mapped to which columns in what table. The element has one attribute called “name” which should represent the name of the database table to persist user data to.

Parameter

Possible Values

Mandatory

Description

name

A valid column name

Yes

The name of the database column

value

Free text, or a user attribute depending on the type parameter

Yes

If the type parameter is “Text”, this value can be any string.

If the type parameters is “Attribute”, this value must map to a user attribute

type

“Text” or “Attribute”

Yes

An absolute path to the folder in which signatures should be saved

isKey

true, false

No

“True” if this column should be considered (part of a composite) key for this table. Key columns determine whether a row should be updated or inserted. Defaults to “false”.