| User Data Template (ttams1110m000) |  |
| use.session.to define a template with the default settings and parameters that are valid for a group of ERP LN users. This template can be linked to a user in the User Data (ttams1100s000) session and the Roles and Templates by User (ttams1201m000) session. By using the specific menu, you can convert the changes in the user data template to the data dictionary. The user file u<user_name> in the directory $BSE/lib/user is (re)build for all users in the specified range in the Convert Changes to Runtime DD (ttams2200m000) session. You must restart Tools to make the changes active at runtime. Related topics To define templates for AMS
Fields | Description
Template Code | Specifies the code of the user data template.
Application Server | Specifies the server between the user interface and the application logic. The user interface connects to the application logic by using this server. The default server is bshell, which can be found in the ${BSE}/lib/ipc_info file. This field can be left empty if the application logic and user interface are located on the same system, and the application server in ipc_info is bshell. The user interface and application logic can also be located on different systems. In that case, you must specify the system on which the server can be found and the server as defined in the ${BSE}/lib/ipc_info file of that remote system. The system name is placed before the application server name, separated by an exclamation mark (!). If the application logic is placed on host2, you must enter: host2!<application_server>. Example
local |  | remote
host1 |  | host2
User Interface | ---> | Applic. Logic (bshell)
LOCAL (host1): Application Server: host2!bshell REMOTE (host2): ${BSE}/lib/ipc_info: bshell s 0 0 s ${BSE}/bin/bshell6.2 Result: The user interface of host1 will communicate with ${BSE}/bin/bshell6.2 on host2.
Startup System | Specifies the system from which the user starts the application. This is also the system to which the remote user file is dumped when this file is created on another system or workstation.
Startup System 2 | Specifies the second system from which the user, linked to the user data template, can start the application. For example, if the first startup system is down or temporarily not available. This is also a system on which the remote user file is dumped when this file is created on another system or workstation.
Help Server | Specifies the path to the virtual folder where the Infor ERP LN Web UI is installed. For example: "srv-nld-beem/webtop".
Print Delete Delay Time [hrs] | Specifies the time between handling a print request and deleting the temporary file. The temporary file stores the data for a period of time before the text is printed. The entered value is used by default when a print program is started.
Locale | Specifies the name of the Tools Super Set locale. A locale is a collection of the TSS character set definition, the NLS locale for the system and minimum and maximum values for form and database fields. Each locale uses a specific range of (multi-byte) characters of the Tools Super Set (TSS).
Refresh Interval [sec] | Specifies the period after which the data of a record is refreshed. If you enter the value 0 seconds, the data of the records will not be refreshed. Note You can also refresh the data on a form by using the Refresh command on the view menu.
History | If this check box is selected, Tools maintains a history log file. A history of session usage can be built up by user, linked to a user template. The history is stored in the file $BSE/lib/TIME.HIS. For each user, the history contains a list of the used sessions, with the execution and termination date and time. The history can be printed using the Print User History (ttaad2402m000) session. To delete the history, run the Delete User History (ttaad2202m000) session. Clear the history log file regularly, and select this field only if absolutely necessary.
Time Zone | Specifies the time zone in which the user, linked to the user data template, is located.
Start Time | Specifies the beginning of the time interval in which the users, that are linked to the user data template, are authorized to start Tools.
End Time | Specifies the end of the time interval in which the users, that are linked to the user data template, are authorized to start Tools.
Shell Command Type | Specifies if the ERP LN user, linked to the user data template, can branch to a session or a shell.
Shell Command | Specifies the shell that is used to start an external program. If the command type is UNIX, you can enter a UNIX program. For example, ksh. If the command type is Session, you can enter a session or menu code. For example, ttstpshell or mtttls1000m0001.
Call Session by Code | If this check box is selected, the user that is linked to the user data template can start a session or menu by using the Run Program command on the tools menu in Web UI or WorkTop.
Application Personalization | If this check box is selected, the users, which are linked to the user data template, are authorized to personalize the form layout of ERP LN sessions. In both the WorkTop and the Web UI, the users can customize the grid (columns) in overview sessions. In the Web UI, the users can also hide/unhide fields and change field labels in other session types. For more information, refer to: To personalize ERP LN in the Web Help Personalize ERP sessions in the Web UI online help If this check box is cleared, the users cannot personalize the form layout of ERP LN sessions.
Authorization for all devices | If this check box is selected, the user, linked to the user data template, is authorized to print reports on all devices. If this check box is cleared, the user is not authorized to print reports on devices unless they are defined in the Device Preference Template (ttams1140m000) session.
Switch Data Languages | If this check box is selected, the users, which are linked to the user data template, are authorized to switch to another data language. In this way, users can view and edit data in multiple languages in sessions that are multilanguage enabled. If this check box is cleared, the users can only view data in their default data language, which is defined in the Data Language field in the User Data (ttams1100s000) details session. For details, refer to Multilanguage Application Data.