Web config - used by web, remote web services, service
The web.config file is an XML file that can be changed as needed, but we recommend running the SuperOffice Web Configurator which is installed by the web client. Administrators can use configuration files to set policies that affect how applications run on their computers. Read more on MSDN.
There are some SuperOffice specific sections, sections defined under the SuperOffice sectionGroup include:
Do not change these values unless absolutely sure
||TrustedDomains(String) Check if a domain name is trusted. Note - separate section within the SuperOffice Security group section, it needs to be declared before it can be defined.
||Cryptographic options, see table below. Note: change any of these keys at your own peril
Ignore the Sentry mechanism, everything will be allowed (default 'False')
Relates to the Sentry system in SuperOffice. The sentry system can be thought of as the traffic cop, controlling access to the data in the database. Each object in Netserver has an associated sentry which is responsible for enforcing rules such as "private appointments are visible only to its owner". Sentry rules focus on ownership, group membership and user-level access.
The Cryptography section is used for encrypting and decrypting user credentials.
||Base64 encoded key-string as documented by System.Security.Cryptography.RijndaelManaged.
||String value representing the user-defined secret, used when creating a hash (signature) to verify that the encrypted-decrypted value has not been tampered with.
In order to find and import Active Directory users NetServer WebServices need to be in the Active Directory domain. This is why we recommend scenario 2 with reverse proxy so you do not expose it to the DMZ.
|| ActiveDirectory domain to use when looking up users
|| Container within the domain, use blank if you do not know
|| Domain user to log on to the domain - needs to be able to list and view users
|| Password of the domain user
Single Sign on (SSO) if you mean that the user should not be presented with the SuperOffice login dialog will not work when using the recommended installation scenario, but the user may still authenticate with his AD username and password. Also note that using Remote webservices for Web (where web and netserver are on different servers) is not supported due to Kerberos double-hop issues
Configuration of mail parameters when using the SuperOffice Inbox. This is also the one used by Pocket CRM.
The Key used for mail reader - default MailKit from 8.1, used to be EasyMail
The Key used for mail sender - default MailKit from 8.1, used to be EasyMail
Change how many days to past we should download and store emails. Defaults to 180 day
SuperOffice Inbox downloads emails from your mail box and stores them in the SuperOffice database.
If you want to change how many days to past we should download and store emails, you can add the following key <add key="NumberOfDaysToDownload" value="XX" /> in Mail section:
<add key="Reader" value="MailKit" />
<add key="Sender" value="MailKit" />
<add key="NumberOfDaysToDownload" value="30" />
Now the Inbox will download emails younger than 30 days only. If no value is set, it defaults to 180 days.
The Factory is part of a NetServer extension mechanism to support plug-ins. To utilize the methods you must develop your own method and configure it in a specific way in the configuration file to identify that you are enhancing a provided method.
For more information, please check Developer club
Settings related to logging.
||Boolean value determines whether to log verbose, detailed, information. Default off, only turn on for extended debugging and do turn this off later.
Should stack traces be collected by various events
||Boolean value determines whether to log all error messages. Default = True
||Boolean value determines whether to log when an access failure occurs / failed authentications (default 'True')
Folder (e.g. UNC path) where the logfile is to reside. Note that the owner of the process needs to have access to manipulate files in this folder
||List of services to be logged; default blank means all, otherwise comma-separated list of service names (without the Agent suffix, for instance: BLOB, Appointment)
Log general information. This includes successful SQL's passed to the database. Only permit this option while debugging a bug. This will be a severe performance hit! (default 'False')
||Should long-running queries be logged in textual form to a special file? default false
Should long-running queries be logged to a special file (Query_year.month.day.log) in XML serialized format, for later analysis and reruns using the QueryWorkbench tool
||Log mail server communication
||Folder to output mail logs. Note that the owner of the process needs to have access to manipulate files in this folder
||Should calls to the service layer be logged
||Boolean value determines whether to log when access is granted / successful authentications (default 'False')
||Log time it takes
||Boolean value determines whether to write message to OS Event Log. (Information Level Ignored)
||Boolean value determines whether to log all Log-Levels to a file. (default 'False')
||Boolean value. Log to SuperOffice Research and Product Development (Online through a WebService). If you experience poor performance during login, set this to False.
||Boolean value determines whether to log all Log-Levels to trace output. Log to a Trace that can be listened to by TraceListener. (default 'False')
Log warnings (default 'False')
Threshold for logging a long-running query, in milliseconds. Queries that execute in less than this time are not logged as long-running. The time is from the moment the SQL text is sent to the database, until the first row (for a select) or the 'nn rows affected' return value is received.
Data / Database
The Data section group contains three sections, Database, Explicit and ImplicitAnonymous. Combined, these sections define which server and database the caller will connect, as well as what state settings to use. Which state settings take affect are determined by how the caller decides to connect, Explicit or ImplicitAnonymous.
The Session section relates to the lifetime of a Netserver communication session, such as the duration of a transaction, or group of transactions, and maintains the credentials defined in one of the following sections.
||String value representing the mode of the session object. Permitted values: Thread, Process and Context
-Thread: Session is stored in a thread static manner. Each executing thread has a separate instance of session. If the session is accessed on a different thread, it will contain a different value. For further reference, see System.ThreadStaticAttribute.
- Process: Session is stored in a process static manner. This is the normal option for windows applications.
- HttpContext: Recommended in ASP.NET applications. Added to prevent ASP.NET thread switches from changing identities in the middle of an ASP.net request.
- Context: Session is stored in a context static manner. For further reference, see System.ContextStaticAttribute.
- PartnerHttpContext: Helperclass for SuperOffice.DevNet.Online.Login
The Database section relates to location and database-vendor specific settings. Supported database servers include SQL Server and Oracle
||Integer value representing the command timeout in seconds.
||String value representing the connection string .
||String value representing the database. MSSQL and Oracle
||Integer value representing the version number of Database
||String value representing the name of the database. Also used for distinct service name.
||String value representing the computer or server name where the database resides.
||String value representing the prefix of the SuperOffice CRM tables in the database.
Sybase Specific Settings
||String representing the location of the driver file.
||String representing the location of the policy file.
||String representing the connection type.
The Explicit section relates to employee and partner access to the SuperOffice database.
||Boolean value determining what authentication mechanism to use when authenticating a user.
If this value is “True”, DBUser and DBPassword are used in the database connection. Otherwise, the credentials provided in the authentication (e.g. SoSession class) will be used. “True” is default for server (e.g. like web) applications and “False” is default for client (e.g. like Windows forms) applications.
||String value representing the DBUser database password.
||String value representing a database username with access privileges.
||Boolean value determining whether an employee is permitted access.
||Boolean value determining whether an external person is permitted access.
||Boolean value determining whether a system user is permitted access.
The ImplicitAnonymous section relates to anonymous access to the SuperOffice database. Implicit Anonymous is what you get when you do not explicitly authenticate as a user. Usually disabled in SO.web, which uses explicit users.
||Boolean value determining whether anonymous access is permitted.
||String value representing the database password used to connect to the database.
||String value representing the database user (not the CRM5 user) used to connect to the database.
||String value representing the SuperOffice CRM5 user password
||String value representing the SuperOffice CRM5 username of the Anonymous user
The Documents section exposes seven settings related to SuperOffice documents. It is used as a way for NetServer to know where the document archive is, what temporary directory to use, as well as exposes a way to allow NetServer to impersonate a user with read and write access to those directories if that is required. See Table Four for complete setting property definitions.
||String value representing the ArchiveUsers domain name.
||String value representing the password of the ImpersonateUser.
||String value representing the path to the SO_ARC directory. The default template path is calculated from this folder if not set.
||String value representing the ArchiveUsers domain name.
||String value representing the domain of the user to impersonate with
||Integer value representing the internal buffer size in KB. Default buffer size is 32KB.
||True if impersonate is turned on. If So_arc is located on a different server in the domain you need to turn this on. The impersonate user will also be used to write filestreams to the temp area during document
||String value representing the UNC path of template folder. (Optional) - if not set defaults to archivepath + \Template
Temporary folder for working with documents. String value representing the temp directory for streaming files (must resolve to the same location for farms/clusters).
You can have more than one ArchivePath in your Web installation. You need to edit Web.config and add more Archive Paths under the Documents section:
<!-- Location of SO_ARC -->
<add key="ArchivePath" value="E:\SuperOffice\SO_ARC" />
<add key="ArchivePath2" value="E:\SuperOffice\SO_ARC2" />
You can add more alternative archive paths, like ArchivePath3, ArchivePath4,...
The Globalization section exposes two settings related to user origin values. This section allows an applications country code and whether to use the country code for all employees and external people.
Complete setting property definitions.
||String value representing the country id for associates that are not persons (e.g. anonymous and system users). Default is GBR (England).
||String value representing the country for associates that are persons (e.g. employees and external users). Default is GBR (England).
||Boolean value determines whether to use the applications country for all persons (e.g. employees and external users).
This section is used to specify whether an application is working locally or remotely.
||String value representing the default operational mode, Local, Remote, or Switch.
||String value representing the base url and filename of the NetServer web services application file, SuperOffice.Services.Stub.
||String value representing the default mode for the switch. Can be Local or Remote. Default = Remote
||Integer value representing the timeout before failover in seconds. Default = 60
Read more on developer club: https://community.superoffice.com/en/content/content/webclient/scripting-in-the-netserver-world/
||Turn on or off the use of scripts
||Path to the scripts. Defaults to \script if not set.
||Time in milliseconds allowed for the script to use. Default 20 sec.
||Integer value representing the number of timeouts the script are allowed before it is disabled. Default 5. Default = 5
||Default = SuperOffice Batch Service
||Default = 16
||Default = 100
||Default = 2
||Default = http://localhost:8002
||Boolean value to start by IIS in the same process.
Defaults to true
In this section you add the Reverse proxy override, if you want to export larger selections (Task-Export to Excel) from the webclient.
http or https
80 or 443
In our examples this would be the external site; socrm.myorganization.com
Export large selections from the webclient has a default value of 10000 rows.
PS! preference has to be added in Web.config
Change the title shown to the user, like My customized site name
String value representing the URL to helpfiles. E.g. in large server farm environments you may point to one helpfile location.
||Our SuperOffice helpfiles, showing correct help file language to the user.
||Permit requests to web services. Default True from 8.1
||Check if NetServer shall wrap and serialize exceptions, or leave it up to communication carrier (i.e. WCF)
|| If we should remove UTF-8 characters that are not valid XML. The Text table is the only place where this filter is active.
Settings for the RESTapi: https://community.superoffice.com/webapi/rest