In NSP SQL Server database there is a table containing global settings for the NSP installation: app.GlobalSettings.
Some of those settings you can change and then affect the behavior in your NSP system.
Note: Those settings control basic functions in NSP. Changes of the values affect system behavior. Do not insert changes if you are not sure of the consequences. Please contact Nilex NSP Support if you need more information regarding those settings.
Following is a list of keys in table app.GlobalSettings:
DefaultLanguage
Language Id for NSP Standard Language. Defined when installing NSP.
DefaultCurrency
Currency Id for default Currency. Defined when installing NSP.
SocialNetworkServerUrl
URL to NSP Social Network Server. Example:
exec app.spSetGlobalSetting 'SocialNetworkServerUrl', 'http://nspsupport.nspnilex.com:1703'
NSPWebAddress
URL to NSP Web. Example:
exec app.spSetGlobalSetting 'NSPWebAddress', 'http://nspsupport.nspnilex.com:90'
NSPSelfServicePortalAddress
URL to NSP Self Service Portal. Example:
exec app.spSetGlobalSetting 'NSPSelfServicePortalAddress', 'http://nspsupport-ssp.nspnilex.com:90'
MaxAttachmentFileSizeInMb
This setting can be changed in NSP User interface:
Configurations > Settings > Extension Management
Setting defines the maximum size of attached files. File size in Mb (Megabytes).
update app.GlobalSettings
set Value = N
where [Key] = 'MaxAttachmentFileSizeInMb'
AllowedAttachmentTypes
This setting can be changed in NSP User interface:
Configurations > Settings> Extension Management
The setting defines which types of files you can attach to e g tickets, comments, articles, CIs and contracts. The allowed file extensions shall be listed in a comma separated string.
Example:
exec app.spSetGlobalSetting 'AllowedAttachmentTypes',
'jpg,jpeg,png,bmp,tif,tiff,doc,docx,xls,xlsx,ppt,pptx,txt,pdf,zip,rar,wmv,mp4,mp3,mov,csv,odt,tsv,xml,eml '
Note: All allowed file extension have to be included in the string. It is not possible to add more extension by running the script with only the new ones.
DefaultCalendarView
This setting can be changed in NSP User interface:
Configurations > Manage > Calendar
Default view when user opens calendar. Can be set to Day, Week, Work week, Month or Agenda.
exec app.spSetGlobalSetting 'DefaultCalendarView', 'Value'
DefaultCalendarFirstDayOfWeek
This setting can be changed in NSP User interface:
Configurations > Manage > Calendar
AllowKBSearchWidgetOnSubmitFormForAnnonymous
When user submit a ticket there could be a search performed in Knowledge base. The search is normally automatically started when user enters a ticket Subject. This setting controls if search shall be done or not when an anonymous user submits a ticket. This setting is valid only if AllowSubmitTicketForAnnonymous is True, se above.
update app.GlobalSettings
set Value = '' --- 'True' or 'False'
where [Key] = ' AllowKBSearchWidgetOnSubmitFormForAnnonymous'
AllowRegisterForAnonymous
This setting controls if anonymous, not logged in users shall be able to register, create a user in NSP on Self Service Portal. If it is set to False Register link on SSP start page and Register button in NSP login form are not available. Run this script to update the value:
update app.GlobalSettings
set Value = '' --- 'True' or 'False'
where [Key] = 'AllowRegisterForAnonymous'
GoogleMapsApiKey
To be able to use Google Maps for showing locations in map in NSP for tickets, users or CIs you must have a Google API key. See Google Maps API Key for more information how to get an API key from Google. To enter the key into the database, run script:
exec app.spSetGlobalSetting 'GoogleMapsApiKey', '[Your_Google_API_Key]'
EnableTriggerForClosedTicket
Normally scheduled triggers are executed only for open tickets. If you need scheduled triggers to execute also for closed tickets you can use this setting. In the setting you can specify time period (time from current time) for tickets to be executed.
Note: Enabling scheduled triggers for closed tickets for long time period could affect system performance. System have to regularly scan large amounts of tickets. Please contact Nilex NSP Support if you need to insert this setting
NSPMobileAddress
URL to NSP Mobile. Example:
exec app.spSetGlobalSetting 'NSPMobileAddress', 'http://nspsupport-mobile.nspnilex.com:90/'
LuceneFullTextSearchDir
File path to folder used for full text search indexes.
Note: If more than one NSP installation are running on same server the installations must have different folders for full text search indexes.
Example:
exec app.spSetGlobalSetting 'LuceneFullTextSearchDir ', 'C:\NSP\NSPSupport\NSPSearchIndex'
CiSelectedFields
If CMDB setting Read all fields, change only selected fields in CI is in use user has permission to change only fields that have been defined in this setting. Selected fields is possible to specify only via DB store procedure. Example:
exec [app].[AddCiSelectedFields] @staticFields = 'Name,Description,ThirdFields' , @dynamicFields = 'CustomFieldName1,CustomFieldName2,CustomFiledName3'
In this script staticFields are properties on root level (common for all CI Types) and dynamicFields are all other properties (in CI subtypes, both standard and custom properties).
Names of staticFields you find in database in app.Columns table, column Name. For dynamicFields you find names in table cmdb.CiTypeProperties, column Name.
Ticket Reminder
Here you can create reminders, notification emails to be sent a specific time defined in a ticket field. You can add more than one reminder, you enter a key name starting with “TicketReminder-“, followed by a unique name.
You must create a Date field (date+time) and a Flag field for the ticket. Date field shall be included in a ticket form, Flag field should not be visible in form. You can use same Date field for several reminders, but every reminder must have its own Flag field. Templateid is an id to a Text Template. Recipient defines which user that receives the email notification, e g BaseAgent or BaseEnduser.
Get Datefield id from table xxx.
Get Flagfield id from table xxx.
Get Template id from table SYS_DEF_TEMPLATES.
Create the reminder:
exec app.spSetGlobalSetting 'TicketReminder-Name1', 'datefieldid:5160;flagfieldid:5161;templateid:78;recipient:BaseAgent'
EnableDynamicScItemApprover
It is possible to specify dynamic approver when defining a service item. If this function is enabled system will get user´s manager as approver of a service order. Manager is a property on user entity that can be imported from AD.
When you configure a service item, on tab Approver you should specify a default approver (same as before), but if checkbox Use Manager as approver is enabled the default approver is used only if no user´s manager is defined.
To enable the dynamic approver function a setting in database has to be activated:
declare @value int
begin
select top 1 @value = c.Id from SYS_DEF_COLUMN c where c.TableId = 111 and c.PropertyName = 'u_Supervisor'
exec app.spSetGlobalSetting 'EnableDynamicScItemApprover', @value
end
In this command you should replace 'u_Supervisor' with property name of Manager field in your system.
EnableAutoReplayEmailFilter
NSP has a function to filter auto reply emails, to stop auto-replys to reach the system. Filter is used for e g prevent auto-reply emails to create new tickets and avoiding mail loops.
Note: Auto reply filtering is by default disabled from Urgent HF 10.7.3.422.1.
In database there is a global setting to enable/disable the filter. Filter is default disabled (If key doesn´t exists in app.GlobalSetting table function is disabled).
To change the setting, run one of those database scripts:
exec app.spSetGlobalSetting 'EnableAutoReplayEmailFilter', 'false'
•Incoming mails with autoreply tag in email header will be inserted as tickets or comments in system. You have possibility to block incoming mails by roles in Email configuration instead, but if a mail loop occurs due to autoreply emails, it's recommended to enable the auto reply email filter in database.
exec app.spSetGlobalSetting 'EnableAutoReplayEmailFilter', 'true'
•Incoming mails with autoreply tag will be ignored and will not be inserted as ticket or comment in system
•Autoreply mails will be transferred to table ehistory.AutoReplayEmail. In future NSP version a feature to show table content in NSP user interface will be developed.
Note that Email Rules has priority for email filtering. If you have activated rule to block auto reply emails, they will be blocked before they enter NSP and will not be inserted in the database.
Note: After change of setting, recycle the application pool!
CountryCallingCode
This setting can be changed in NSP User interface:
Configurations > Settings > Configurations > Agent Portal Configuration
PhoneNumbersCheckFinished
ReCaptchaSiteKey
IsDemoEnv
FullTextSearchServerType
FullTextSearchServerUrlWithPort
ElasticSearchEnabled
ExtensionManagementSetAsAllowed
DisallowedAttachmentTypes