The following configuration parameters, configurable in "Configuration" -> "Seon Enterprise" influence the behaviour of Seon Webaccess, the end user web interface for using Seon Enterprise functionality.
Encrypt Webaccess session information?
| DB configuration name: |
webaccess_session_encrypt
|
If enabled, Seon Webaccess saves the session information for the logged in user in the database encrypted. This increases the CPU load of the webserver.
Compress Webaccess session information?
| DB configuration name: |
webaccess_session_compress
|
If enabled, Seon Webaccess saves the session information for the logged in user in the database compressed. This increases the CPU load of the webserver.
Don't show receive queue view?
| DB configuration name: |
webaccess_disable_recq
|
Seon Webaccess can show the receive queue (without administrative capabilities) to the end-user in a stripped view, containing company name, progress information etc. If you don't want this, you can disable the rendering of this overview for every user.
Don't show send queue view?
| DB configuration name: |
webaccess_disable_sendq
|
Seon Webaccess can show the send queue (without administrative capabilities) to the end-user in a stripped view, containing company name, progress information etc. If you don't want this, you can disable the rendering of this overview for every user.
Show incoming jobs without recipient?
| DB configuration name: |
webaccess_show_invalid_rec_jobs
|
Jobs without a valid recipient must normally be handled seperately, i.e. by routing them to a target destination. If you don't want to invest this administrative overhead, you can give users of Seon Webaccess the possibility to view incoming jobs without recipient. They can handle the job as a normal receive job, including fetching files, forward this job etc.
Session timeout
| DB configuration name: |
webaccess_session_timeout
|
After this configured timeout (in minutes) Seon Webaccess removes stale sessions of logged in users.
Highlight address code in ENGDAT filenames?
| DB configuration name: |
webaccess_highlight_addresscode
|
If a filename is not converted to a human-readable filename (i.e. if the sender didn't define it in an ENGDAT abstract file), the filename can be hard to read. In order to increase the readability of the address code of the file (which defined the recipient of the file), it can be highlighted in the following ways:
| DB configuration name: |
webaccess_highlight_addresscode_bold
|
| DB configuration name: |
webaccess_highlight_addresscode_underline
|
| DB configuration name: |
webaccess_highlight_addresscode_italic
|
