The configuration can be done by environment variables or by a yaml configuration file. For more complex scenario the yaml is recommended.
Global Environment Variables
Configuration | Required | Default | Description |
|---|---|---|---|
|
| Hostname of the server with the ContentServer | |
|
| Port of the ContentServer usually 80 or 443 | |
| https | Protocol of the contentserver http or https | |
| /contentserver | Context Path of the server usually /contentserver | |
| false | Default setting when the request for print does not contain any information whether to include the notes or not. | |
| false | Default setting when the request for print does not contain any information whether to include the annotations or not. | |
|
| This default is not intended for production use, please change this value | |
| Default stamps available to all instances, additional to the instance specific configured values. Support Stamps in the following formats: Configuration allows to enter a folder e.g.:
one or more files:
| ||
| 100 | Max size of cache entries, i.e. one stamp file is one entry. If more stamps are present, the oldest ones are removed from cache. | |
| 10 | Lifetime of unused entries in stamp cache in minutes. | |
| 10000000 | Max filesize in bytes of each stamp file. | |
| Popup | When sending mail, how the compose window should be displayed, Default is Popup, i.e. a new window/tab is opened. |
Global OPENID Configuration
This configuration is required, when the user should login to see the documents or when using the Outlook 365 E-Mail integration.
Configuration | Required | Description |
|---|---|---|
|
| Usually |
|
| Defines where in the token the username can be found that will be used in the notes, usually name |
|
| The provider that should be used. Should be |
|
| The public identification of the application, the ClientId |
|
| The client secret for the application |
|
| fixed value |
|
| fixed value |
|
| fixed value |
|
|
|
Instance Variables
All instance variables are optional and there is no configuration required. Use the default profile in this case. You can also override the default profile with your own configuration or create new instances. Only changed parameter should be in the configuration.
configurations are overritten in there levels:
global default
default instance configuration
specific instance configuration
Example:
Global inbuild default: documentNote is true. (notes can be created in documents.
default configuration override: tia.instances.default.documentNote is false. Inbuild default is overwritten and notes are global disabled
Finance configuration allows notes: tia.instances.finance.documentNote is true. When the instance finance is used the notes can be applied and displayed.
Configuration | Default | Description |
|---|---|---|
|
| When activated, the note button in the frontend is visible and can be used. |
|
| Default value for the modal print dialog. When Activated the checkbox is prefilled, otherwise checkbox is not selected. |
|
| This option control the note area opening behavior when opening a document:
|
|
| when active a user can reside the notes modal |
|
| Default width of the document notes modal dialog. |
|
| default high of the notes modal |
|
| If this option is activated, users can print the document note. |
|
| If this option is activated, edit mode is automatically entered when a document is opened. |
|
| Default font size for notes |
|
| Automatically turns of the Edit mode in case the document has been saved. |
|
| default size of the annotation lines |
|
| default high of the checkmark annotation |
|
| default color of the checkmark |
|
| If this option is activated (1), the thumbnail is automatically displayed when a document is opened. |
|
| If this option is activated, users can draw checkmarks |
|
| If this option is activated, users can download documents. |
|
| If this option is activated, users can add text to documents. |
|
| If this option is activated, users can draw freehand lines. |
|
| If this option is activated, users can select the doc structure. |
|
| When activated, new annotations can be edited (created). |
|
| The default width of a checkmark |
|
| Defines the amount of time in milliseconds to display the information, who and when an annotation was created, until this notification timeouts. |
|
| If this option is activated, users can draw highlights. |
|
| If this option is activated, users can draw arrows. |
|
| Default value for the modal print dialog. When Activated the checkbox is prefilled, otherwise checkbox is not selected. |
|
| Defines whether a user may edit annotations created by others or whether he may only edit annotations created by himself |
|
| If this option is activated, users can use stamps. |
|
| Defines the timespan in milliseconds until a notification timeouts. |
|
| When activated, the annotation history is accessable. |
|
| Size of a checkmark line |
|
| If this option is activated, users can draw redactions. |
|
| Size of the font in annotations. |
|
| If this option is activated, users can draw rectangles. |
|
| If this option is activated, users can print annotations. |
|
| Color of the line of a annotation as RGB value. |
|
| Default value for the modal download dialog. When Activated the checkbox is prefilled, otherwise checkbox is not selected. |
|
| show ole attachments when included |
|
| default height of the history list in the note model edit view |
|
| If this option is activated, sending the document via email is enabled (only if oauth is used). |
|
| Default font color for annotations as RGB value. |
|
| If this option is activated, users can draw circles. |
|
| If this option is activated, a watermark is set. |
|
| If this option is activated, users can print documents. |
|
| If this option is activated, users can draw lines. |
|
| Minimal allowed height of the edit note modal. User cannot make it smaller than this value |
|
| Default value for the modal download dialog. When Activated the checkbox is prefilled, otherwise checkbox is not selected. |
|
| Minimal height of the history list in the note model edit view. |
|
| Minimal allowed high of the edit note modal. User cannot make it smaller than this value |
|
| If this option is activated, users can draw sticky notes |
| For saving or creating annotations a secKey is required and can be created by sap. | |
| Username for the SAP connection | |
| Password for the SAP connection | |
| Text for the watermark in the background | |
| Support Stamps in the following formats: Configuration allows to enter a folder e.g.:
one or more files:
| |
|
| If active, a ArchiveLink get request for a component will return the viewer. This configuration allows to use the viewer without SAP Customizing (see https://kgs-software.atlassian.net/wiki/spaces/WIKI/pages/3246620679/Supported+Scenarios+Vc#tia-Viewer-CSV-Scenario* ) |
| "application/pdf", "image/tiff", "image/tif", "image/jpeg", "image/jp2", "image/png" | The viewer supports these types in default an convert the images to pdf. You reconfigure it and only use the viewer with pdfs with: |
|
| Change the behaviour of the Microsoft Graph Mail API. On Mail send following will happen: on "Popup":
on "Embedded":
|
How to configure
The viewer allows two different ways to apply configuration.
Configuration by environment variables is for configurations that are small and modify only a few variables. It is easy and fast to create and apply these configurations.
Configuration with yaml is for more complex configurations and different instances with complete different configurations. A yaml is prepared and then mapped in the container like as configmap or volume mapping.
Configuration by environment variables
Example for docker compose file
version: '3'
services:
tiaviewer:
container_name: tiaviewer
image: images.docker.kgs-cloud.de/tia-viewer/archivelink-oidc:latest
ports:
- "8080:8080"
environment:
tia.destinations.saphttp.host: contentservevr.kgs.local
tia.destinations.saphttp.port: 8090
tia.instances.default.watermark.text: copy
tia.instances.default.sap.url: https://sapServer:8400/tia/tia_viewer?sap-client=250
tia.instances.default.sap.username: secuser
tia.instances.default.sap.password: s3cret
tia.instances.default.mimetypes.0: application/pdf
Configuration with yaml
Example for docker compose file
viewer.yaml:
tia:
destinations:
saphttp:
host: contentservevr.kgs.local
port: 8090
instances:
default:
watermark:
text: "copy"
sap:
url: "https://sapServer:8400/tia/tia_viewer?sap-client=250"
username: secuser
password: s3cret
mimetypes:
- application/pdf
HR:
downloadDocument: false
FI:
text: "confidential"
FO:
printDocumentNote: false
mimetypes.0: application/pdf
load the viewer.yaml in the container:
version: '3'
services:
tiaviewer:
container_name: tiaviewer
image: images.docker.kgs-cloud.de/tia-viewer/archivelink-oidc:latest
ports:
- "8080:8080"
volumes:
./viewer.yml: /app/config/viewer.yml
environment:
spring.config.additional-location: /app/config/viewer.yml