On the general tab, ITP Model settings are configured that don't belong to a specific connection. These general settings can be configured on global level (for all environment) or for a specific environment. The following settings can be set:
Setting |
Description |
PostIncludePath |
ITP/Server can use post included subdocuments as a method to include external documents in ITP result documents. These subdocuments are called post includes and will be included in the result document right after the document has actually been generated. The default folder were ITP/Server searches for the result documents is the 'Models/PostIncludes' folder in the ITPWORK folder of the ITP/Server installation. This default can be changed with this setting. The folders in the search path are separated by semi-colons (;). |
OutputLanguage
|
This setting is the language code for running ITP Models. This setting determines the way certain standard functions operate (such as the function amount_in_words). |
ModelLanguage |
Here you can specify the language used for the ITP language keywords and standard functions. You can choose between ENG (English), DEU (German) and NLD (Dutch). |
SmartCodePage |
At this moment, this setting is AS/400 only. Checking the setting allows the translation from AS/400 data to unicode. This setting has been introduces to support non-latin languages (such as Greek). Refer to AS/400 Connection for more AS/400 Connection settings. |
MultiByteCodePage |
At this moment this setting is AS/400 only. If SmartCodePage is checked, this codepage is used for translation if the AS/400 data contains multi-byte characters. This setting has been introduced to support far-east languages (such as Thai). Refer to AS/400 Connection for more AS/400 Connection settings. |
RepositoryServer |
The IP address and port of the ITP/MDK Repository. This ITP/MDK Repository is used to retrieve the model's runtime objects (text blocks, views, forms and field sets). |
RepositoryObjectStatus |
The required status of the runtime objects that are retrieved from the ITP/MDK Repository. Only revisions having this status (or higher) are used. If this setting is set to a value other than Development, testing from the ITP/MDK Repository (or other applications) will ignore the 'in development' revisions locked by the user profile and only return revisions that match the specified status.' Note If this setting is configured on the revision status 'published', it will be overruled when the compatibility option "Handle accepted revisions as published" is enabled. Refer to chapter General use, section Handle revisions in runtime objects for more information on the compatibility option. The option Autodetect implements the behavior of older ITP/Server versions. If the client specifies a user, the 'in development' revisions of that user are retrieved. Otherwise the 'published' revisions are used. |
RepositoryDevelopmentUser |
The default user profile that should be used to retrieve 'in development' revisions from the ITP/MDK Repository. This profile is used if the calling application (or the ITP/MDK Repository) does not provide a specific user account. If the name of the user profile can be interpreted as a number e.g., all digits, it must be prefixed with a ':' to avoid being interpreted as an internal user-id. |
FormAcceptHTML |
This setting is by default activated. When set, HTML instruction added to texts in a FORM is passed to ITP/OnLine. This allows for example for parts of the table title text to be put in bold or to insert a linefeed. |
OracleClient |
Here you can specify the version of the Oracle OCI client installed on the server. By default this setting is set to version 8i. Models depending on the 8i behaviour can be broken if this setting is changed. |
CacheData |
This setting controls caching and capturing of data retrieved from external data sources and offers the following 3 options:
This option prescribes that identical requests will return identical results. If data retrieval has any side effects, such as updating tables or retrieving data based on factors other than the retrieval keys, this option should not be used. Note This option is only supported for ITP/OnLine models. |
CacheDynamicData |
This setting controls the caching of dynamic objects retrieved from the ITP/MDK Repository. If this setting is enabled all dynamic objects retrieved from the ITP/MDK Repository are saved in the session and retrieved when the ITP Model continues after an interactive screen. If this setting is disabled all dynamic objects are retrieved every time the model continues after an interactive screen. Note Because the cached objects are saved in the session, they are also saved when the session is suspended and resumed at a later time. Note This option is only supported for ITP/OnLine models.
|
ConvertUnicodeData |
If a W_CHAR (Unicode) field contains only characters that are in the ISO-8859-1 code page its content can be represented in the same format that would be used for C_CHAR fields. Converting this content to the C_CHAR format does allow it to be compared directly against fixed text in the model without having to resort to Unicode-aware functions such as compare_characters. This setting controls whether or not such conversions are being made. By default this setting is disabled for backward compatibility. Note If a W_CHAR field contains any content that cannot be represented in ISO-8859-1 the whole field is passed without conversion.
|
LabelDocuments |
This option configures the directory where ITP/Server will search for multi-labeling resources. This setting is used by the model language functions stylesheet() and pagestyle().
|
QFormsShowAllUsed |
QForms are triggered by Text Blocks that use Fields that have not been assigned a value. Such a QForm only displays questions for those Fields that have an empty value. This setting causes the QForm to display questions for all Fields that are used in the Text Block, even those with a non-empty value. By default this setting is disabled for backwards compatibility. Note This option is only supported for ITP/OnLine models.
|
XMLWebImplementation |
This option selects which XMLWeb implementation to use to connect to a Web Service for data retrieval. The following options are supported:
By default ITP/Server will use the WinHTTP implementation.
|
DisableValidation |
This option disables all server-side validation of answers provided to ITP/OnLine forms. This option is provided for backward compatibility. Disabling this option can cause problems with the ITP/OnLine Suspend and Resume functionality and it will allow users to bypass the security of the ITP/OnLine Secure Mode.
|
EnhancedUnicodeSupport |
This option maps all byte-based comparison operations and text manipulation functions in ITP mMdels automatically to their character-based (Unicode aware) equivalents. Note Enabling this option affects all ITP Models at runtime. Recompilation is not necessary.
|
EnhancedUnicodeMaps |
This option enables the use of character-based (Unicode aware) keys in MAPs. Note Enabling this option affects all ITP Models at run-time. Recompilation is not necessary.
|
IgnoreUnseenGroups |
This option suppresses validation and assignment of questions on Forms in groups that are not shown, due to a Note It is also possible for model developers to enable this feature on selected Forms.
|
LibrarySearchPath |
This option specifies a list of folders that is searched for deployed Data Backbone (.ITPLIB) objects. The folders in the list are separated by semi-colons (;).
|
TranslateOnLineResources |
This option controls whether or not ITP/Server will generate localized messages in interactive forms, or emit a message identifier as a placeholder. Disabling this feature enables ITP/OnLine Server or another calling application to perform its own customized localizations.
|