Using Administration Utilities

Compose the signon message in this edit box. The system will display to the user all text entered into this edit box. When creating messages, consider:

• Message size limit is 32 KB.

• Only plain text is supported (not HTML, XML, Rich Text, or text including links, bold, underline, and so on).

• Translation of the message is the responsibility of the system administrator creating the message. The system does not translate the message depending on the language of the user. For example, in Quebec, Canada, you might consider displaying an English and French version of the message.

• The message will be seen by all users signing on to the database through a browser, regardless of role, department, time zone, and so on. As such, care should be taken to ensure the message has broad relevance.

  Note: The message will not be displayed to Windows Development Environment users.

Specify the duration for which the message will be active by setting a start time and date and an end time and date. The system only displays messages where the current time is after the start time and date and before the end time and date.

Identifies the database's base language.

The base language of an application is the application's primary language, normally the language that is used most commonly throughout the enterprise. A database can have only one base language. All other language translations that are stored in the database are referred to as nonbase languages (or sometimes as foreign languages).

You can't change the base language setting on this page. This field is for display purposes only. To change the base language, use the SWAP_BASE_LANGUAGE Data Mover command.

If you select the Translations Change Last Update check box, and you use the PeopleTools translate utilities to translate objects, the system updates the Last Updated information of the translated object to the date/time/userid of the translation. If it's turned off, then the date/time/userid of the object does not change when it's translated.

Select the sort order that is appropriate for the site.

See the Global Technology PeopleBook for descriptions of the options.

The value in seconds that you enter here acts as the default for Security Administrator profiles.

Turn on Multi-Company Organization if more than one company makes up the organization.

This option affects how Application Processor displays company-related fields in search dialogs and pages. See the HRMS documentation for more details.

The Multi-Currency setting is a systemwide switch that enables automatic formatting of currency amount fields that have associated currency control fields. Another function of this setting is to globally display currency control fields. If you turn off this option, automatic formatting based on currency control fields is no longer active and all currency control fields are thus hidden.

When the Multi-Currency setting is on, it also validates user-entered currency data against the currency's defined decimal precision. This validation causes the system to issue an error if a user attempts to enter a decimal precision that is greater than that which is allowed by the currency code definition.

Under most circumstances, leave Multi-Currency selected.

Deselect the Use Business Unit in nVision option if you're using an HRMS database. Otherwise, select it.

Select this check box if you want the report request in nVision to be secure. The default setting is selected.

Selecting Multiple Jobs Allowed enables HRMS systems to support employees holding concurrent jobs with more than one set of enrollments.

This option affects how Application Processor displays employee-record-number-related fields in search dialogs and pages. See the HRMS documentation for more details.

Typically, you turn on this trace only during periods in which you are collecting detailed performance metrics. When you are not tuning your performance, the DB Optimizer trace should be turned off.

When adding a new user by using PeopleTools Security, the system automatically grants the new user select-level access to a set of PeopleTools SQL tables used for security. If you are using a SQL security package and do not want PeopleTools Security to perform any SQL grants, turn off Grant Access.

Enables you to add the capability to set a database compatibility mode as an overall database setting, forcing developers to create applications by using all platforms as the least common denominator. This option enables developers, who create applications for multi-platform deployment, to catch platform-specific issues at design time rather than during testing.

If platform compatibility is enabled for a database, the system forces developers to enter a tablespace name when saving a record definition regardless of the current platform. If this option is disabled, you are only prompted for a tablespace name if you are developing on a platform that utilizes tablespaces. This prevents table record definitions being added to the database without a tablespace name.

Enables you to override non-z/OS COBOL batch restrictions. If the DB2 z/OS database's CCSID is NOT 37, PeopleSoft blocks batch COBOL from running against z/OS Databases on Windows unless you choose this override.

Select this option when you have non-repeatable PeopleCode logic in your application's SavePreChange or Workflow. In previous releases, PeopleSoft applications were coded to assume that errors during save are always fatal, but the current PeopleTools release no longer behaves this way. Use this option to ensure predictable behavior with your application without having to modify your older application code.

This check box is cleared by default. If you get an error during save processing, the transaction continues and you're allowed to attempt to save again. When this option is selected, if you get an error during save processing the transaction is aborted and all changes are lost. This applies to errors that occur between and including the SavePreChange event to the SavePostChange event. It also includes the component processor save processing. It doesn't include errors from the SaveEdit event.

For example, suppose you have some calculations that occur in SavePreChange which are based on the buffers and also modify the buffers. If there's an error during the save and you attempt to save again, the calculations are repeated, but this time based on the buffers that were already modified by the first time the calculations where done. Therefore the second time the calculations are done they will be incorrect, which could lead to incorrect data being saved to the database. In this case you would want to turn on the Save Error is Fatal option, because a fatal error on save is more desirable than incorrect data being put into the database.

If selected, focus is set on the Save button when a user saves a component. If not selected, focus is set on the first control on the page that can assume focus when a user saves a component. By default, the option is not selected.

The value that you specify in the Temp Table Instances (Total) edit box controls the total number of physical temporary table instances that Application Designer creates for a temporary table record definition when you perform the Build process.

This value indicates the total number of undedicated temporary table instances. The maximum number of temporary table instances that you can specify is 99.

Enter the available online instance values. When you invoke a process online, PeopleTools randomly allocates a single temporary table instance number to programX for all of its dedicated temp table needs. The higher the number of online instances that is defined, the less likely it is for two online processes to get the same value.

Use this parameter to set the maximum message size being handled by Integration Broker.

There is a practical limit to how large a message can be. This limit can be determined by a variety of factors, including network speed, available memory, processing load, and so on.

Although you can display time data a number of different ways, PeopleSoft databases store all times relative to a system-wide base time zone. You can adjust the display of the time that an end user sees using the Use Local Time Zone (LTZONE) setting in PeopleTools, Personalizations.

This base time zone is the one that the database server uses. In order for PeopleSoft to properly manage time data, the system needs to know which time zone that is. Set the Base Time Zone to the time zone that the database server's clock uses.

This field is no longer used.

Normally, field length validation is based on the number of characters that are allowed in a field. For example, a field defined as CHAR(10) in Application Designer holds ten characters, regardless of which characters you enter. In a Unicode database, double-byte characters, such as those found in Japanese, are counted the same as single-byte characters, such as those found in the Latin alphabet.

If you create a non-Unicode database, the field length in Application Designer represents the number of bytes that are permitted in the field, not the number of characters. When the non-Unicode database uses a single-byte character set (SBCS), you can only enter single-byte characters, so the number of characters and the number of bytes are the same. However, because double-byte character sets (DBCS) typically allow a mix of single- and double-byte characters, the number of characters that are allowed in a field in a non-Unicode DBCS database varies. This is true for both shifting and non-shifting double-byte character sets.

For example, a if a user enters ten Japanese characters into a field that is defined as CHAR(10) in Application Designer, this string needs 20 bytes of storage in a nonshifting double-byte character set and 22 bytes of storage in a shifting double-byte character set. This ten-character input fails insertion into both these databases.

Use the Data Field Length Checking option to ensure field length validation appropriate to the database's character set. Values are DB2 MBCS, MBCS, and Others.

Choose Others if you are using a Unicode-encoded database or a non-Unicode single-byte character set database. This prevents special field length checking. As discussed above, these types of databases do not require such checking.

Choose DB2 MBCS if you are running a Japanese database on the DB2 UDB for z/OS platform. This enables field length checking based on a shifting DBCS character set.

Choose MBCS if you are running a non-Unicode Japanese database on any other platform. This enables field length checking based on a nonshifting DBCS character set.

The non-Unicode DBCS settings are specifically oriented towards Japanese language installations, as Japanese is the only language that PeopleSoft supports in a non-Unicode DBCS encoding. All other languages requiring double-byte character sets are only supported by PeopleSoft by using Unicode encoded databases.

Controls the size of the file attachment chunks that are stored in the database. This allows you to upload a file attachment that is larger than could be stored in a single row of the database. The system divides the data into chunks to store in different rows of the database table.

The default is 28,000 bytes, and maximum attachment chunk size allowed by PeopleTools is 50 MB. Application Designer data types control how the system manages "long data."

If you want to store your files in the database in a form that allows for portability across the database platforms supported by PeopleTools, you must set the Maximum Attachment Chunk Size option to a value that would be permitted by all of the database platforms supported by PeopleTools — no more than 28,000 bytes.

However, if you do not want to consider the portability of files across database platforms supported by PeopleTools, you may set the Maximum Attachment Chunk Size option to the maximum value that your database supports. For example, if you are using the Oracle database, you can set the value to 2 GB.

See Specifying Long Character Field Attributes.

See Functions by Category.

See Understanding the File Attachment Functions.

Sets the limit on how many rows can be modified by an upgrade project before the system issues a COMMIT statement.

The Enable Switch User option enables you to limit the users who can change identities in a PeopleSoft system. The feature applies only when accessing PeopleSoft using a browser; it has no effect on two-tier or three-tier connections.

Most sites have no reason for individual users to change their PeopleSoft system identity during a session. For those sites that do require this capability, the number of users who need to switch to another user profile typically is fairly small. For example, the users who can switch identities are usually limited to the system's GUEST user (if the system has one) and, perhaps, a few system administrators or power users.

Options for Enable Switch User are:

• All: Use this value to indicate that all users are permitted to change their identities during their browser session. This is the default value.

• None: Use this value to indicate that no user is permitted to change identities during a browser session

• Some: Use this value to indicate that some, selected users are permitted to change their identities during a browser session. When you select this value, the Allow Switch User checkbox appears on the General page of the user profile definition in the PeopleTools Security interface. Select Allow Switch User to indicate that the individual user is permitted to change identities within a PeopleSoft session. User profiles that have the Allow Switch User option unselected will be immediately logged out when the system detects a change in the user's identity.

Once you specify which users can switch identities, if an identity change is attempted (switch user) by an unauthorized user, the system:

• Logs that user off the system, immediately.

• Displays the following message on the signout page: "Illegal Identity switch has been detected by the System. Please re-login."

• Writes an entry in the web server logs indicating that an illegal switch user was attempted.

See Setting General User Profile Attributes.

The MinHash option enables you to set the minimum hash algorithm that all sites participating in single signon (SSO) must use in order to talk to each other. The default value is SHA256.

Options for MinHash are:

• SHA1 - The site is hashed with the SHA1 algorithm.

• SHA256 - The site is hashed with the SHA256 algorithm.

During the PS_TOKEN validation at the Web tier, PeopleSoft uses the MinHash value to prevent Web sites with weaker hashing algorithm from talking to other sites participating in single signon. The MinHash option is not used for PS_TOKEN generation.

See Implementing PeopleSoft-Only Single Signon for more information on PS_TOKEN.

Enables you to provide case-insensitive searching for the PeopleSoft search records when searching for PeopleSoft definitions. The options are:

• Off : Enables case sensitive searching and sets it to "on"without displaying the Case Sensitive check box on the search page.

• On - Case Sensitive Default Off: (Default) Displays the Case Sensitive check box on the search page unselected, providing the user the option of enabling case-sensitive searching for a particular search by selecting the Case Sensitive check box.

• On - Case Sensitive Default On : Displays the Case Sensitive check box on the search page selected, providing the user the option of switching tocase-insensitive searching for a particular search bydeselecting the Case Sensitive check box.

Display the default, system-wide branding settings, which are defined on the Branding System Options page:

• The style sheet for classic components.

• The application package that contains the application class that defines system-wide branding functions.

• The application class that defines system-wide branding functions.

See Configuring Branding System Options for more information on setting these values.

Sets the absolute maximum number of rows, system-wide, an end user can specify to be returned on a standard search page. The default value is 0, which makes the Default rows in search results value the absolute maximum.

If this value is greater than 0 (enabled), then the following will appear at the top of the search page:

"Maximum number of rows to return (up to <Max rows in search results>):"

End users specify a custom number of rows on the search results page in the edit box appearing after this line.

When the user clicks Search, if the key values supplied retrieve more than the <Max rows in search results> value, then a message will appear above the search results similar to:

"Only the first 300 results of a possible 386 can be displayed."

In this case, 300 is the value of the Default rows in search results edit box, unless the user has changed it. The 386 is the actual number of results the search key values would have returned. The system runs a separate query to report this value.

This has performance implications, so system administrators should consider whether to enable this feature. To prevent end users from specifying any custom number of rows returned by the search, set Max rows in search results to 0. If disabled, the number of rows returned by a search is the value from the Default rows in search results setting, and cannot be modified by the end user.

Sets the default number of rows, system-wide, to be returned on a standard search page. The default value is 300.

If an end user needs to increase the number of rows returned on a search page, they can specify a number up to the maximum, specified by the Max rows in search results value.

Sets the default number of search results displayed by the Search Framework to an end user.

Sets the maximum number off rows displayed in a pivot grid.

The main branding application class that generates header, footer, and menu pagelet icons. The default is the standard PeopleTools branding, BrandingBase. For PeopleSoft Interaction Hub, a different branding application class from a different branding application package is used. It generates different header, footers , and menu pagelet icons dynamically, based on the user role or security.

Specify the URL that points to an installation of PeopleTools online help. When users press the F1 key in Application Designer or other Windows client applications, the appropriate context-sensitive PeopleTools documentation is displayed.

You can point to either a local installation of PeopleTools online help or to an installation on Oracle’s hosted documentation website:

• To point to a local installation of PeopleSoft online help, construct the URL similar to the following:

  http://webserver:port/help_folder/help.html?ContextID=%CONTEXT_ID%&LangCD=%LANG_CD%

  For example:

  http://myserver.example.com:8080/help-PB/help.html?ContextID=%CONTEXT_ID%&LangCD=%LANG_CD%

• To point to an installation on Oracle’s hosted documentation website, construct a URL similar to the following:

  http://www.oracle.com/pls/topic/lookup?id=%CONTEXT_ID%&ctx=library_cd

  For example:

  http://www.oracle.com/pls/topic/lookup?id=%CONTEXT_ID%&ctx=pt854pbh1

  Note: For more information on current library codes, see PeopleSoft Online Library and refer to the attachment in the section titled “Setting Up Context-Sensitive Help.”

This setting only applies to the Windows environment (such as Application Designer).

The Ctrl+F1 URL allows you to provide an alternate location for help. For example, you may set the main F1 Help URL to PeopleTools online help and the Ctrl+F1 for the company's help site.

This is the setID that the system uses as you add additional record definition groups to be shared within this tableset.

Although this database is set up to share only one accounting-related record group, you may have multiple record groups to which you assign default unique Set IDs.

The Default setID that you assign to this field value automatically appears. If you create another tableset for sharing trees, you can change this value.

Use the browse button to select from a list of only the tree definitions that are defined with the same Set Control Field.

Use the browse button to select the appropriate SetID.

Insert projects, containing panels that you want to convert, into this scroll. In addition, if you use the Apply Panel Group Defaults option, any panel group that is contained in projects in this scroll are processed. Note that exceptions may be defined see the task titled, Project Exceptions.

Insert panels that you want to convert to pages into this scroll.

If you want to ensure that a group of panels or panel groups is never processed for conversion, you can insert them into an application upgrade project and insert the project name in this scroll.

Panels that are inserted into this scroll are not be processed.

If you select this option, scroll-to-scroll area conversions take place for panels with scroll bars. If this is unchecked, no scroll-to-scroll area conversion takes place.

Some scroll bars may exist with scroll action buttons that are already defined. This option determines whether these scrolls should be converted or ignored. If they are converted, the scroll action buttons are removed before the scroll bar is converted to a scroll area.

If you select this option, scrolls with scroll action buttons are converted. If this options is not checked, scrolls with scroll action buttons are ignored.

If you select this option, panels with level 1 scrolls are processed for scroll conversion.

If you select this option, panels with level 2 scrolls are processed for scroll conversion.

If you select this option, panels with level 3 scrolls are processed for scroll conversion.

If you select this option, level 1 scrolls are converted to scroll areas.

If you select this option, level 2 scrolls are converted to scroll areas.

If you select this option, level 3 scrolls are converted to scroll areas.

This parameter is a general scroll count limit for scroll conversion processing. For example, if this is set to 5, any panel with more than five scrolls that are not invisible is ignored. This is a simple way of eliminating complex panels from automatic scroll conversion.

This option is used to define whether a specific size should be assigned to a panel. If you select this option, the panel size that is defined in the drop-down list box is applied to the panel. If this is unchecked, no changes are made to the panel size.

If you select this option, the style sheet that is associated with a panel is updated with a blank value, so that the panel's style sheet appears by default from PSOPTIONS.STYLESHEETNAME ('PSSTYLEDEF').

If you select this option, the conversion process looks for frames, group boxes, and horizontal rules that have no styles associated with them, and that appear to be associated with a specific scroll area by virtue of their position within a scroll area. It then assigns level-specific styles, based on the occurs level of the scroll area.

Horizontal lines were a new page object for PeopleSoft 8. This option applies only for applications upgraded from releases previous to PeopleSoft 8. If you select this option, the conversion process looks for frames on the panel with upper and lower coordinates less than nine grid units apart. These frames are then converted to horizonal lines.

If you select this option, the process removes all frames on the converted panel.

This applies to grids that are on a panel being converted. If you select this option, the conversion process determines if grids on the panel have their 'Odd/Even Style' turned on. If it is not turned on, the conversion process turns on this option.

This option applies to edit box fields that are not invisible and are not display-only. If you select this option, the conversion process turns on the Show Prompt Button option for edit box fields that have it turned off.

Used to apply standard defaults to component definitions. The defaults that are set are dependent on the Use characteristics of the component. See Application Designer, Component Properties/Use and Component Properties/Internet tabs.

Turns off the Show Grid Lines option for grids that have it checked on.

Enables you to convert panels whose language code differs from that in PSOPTIONS. Select a language code from the drop-down list box.

When set to Inactive, the system ignores the file extension list. Any file extension entries in the Contained Extensions grid are ignored at runtime for an Inactive list type. From a development perspective, it may be useful to keep a working list of file extensions, but keep the list itself inactive until it is fully tested.

With an Absolute file extension list, you can create a list in which all the acceptable filename extensions are explicitly enumerated and have a status ofAccept. That is,only the file extensions that appear in the Contained Extensions gridand have the Status set toAccept will be accepted for that file attachment operation at runtime. An Absolute file extension list is most appropriate for situations where you wish to accept a relatively small number of file types.

Any file extension set to Reject will not be accepted at runtime. However, not including such a file extension in your absolute list will have precisely the same effect.

The Relative file extension list type is based on the Standard Extensions list, and provides a flexible means to specify a finite number of files that are acceptable, as well as enabling you to extend the Standard Extensions list, if needed. A Relative file extension list is most appropriate for situations where you wish to reject a relatively small number of file types.

After reviewing the Standard Extensions list, add specific file extensions that you do not want to authorize for file attachment operations to the Contained Extensions grid, and set the Status value toReject. By doing so, you indicate to the system that you authorize all of the extensions on the Standard Extensions list,except for those you've added to the Contained Extensions grid and set toReject.

For a Relative file extension list type, you can use the Accept status value to effectively extend the current list of Standard Extensions for this specific relative file extension list. For example, assume that at your site you use a product that uses a file extension that does not appear in the Standard Extensions list. By adding that file extension to the Contained Extensions grid and setting its Status value toAccept, the PeopleSoft system will accept that file type for file attachment operations involving this specific relative file extension list.

Do not use the Unlimited extension list type in the current release. This type of list is intended for possible use with future functionality.

Enter the file extensions you want to accept or reject. Add one extension per row, with each extension not exceeding ten characters.

The system saves the value of an individual file extension as all upper case, regardless of the case you enter, and prepends a period ('.') to the file extension unless its first character is already a period.

For a specified file extension of type Absolute or Relative, you have these Status options:

• Accept: Indicates that the system will accept files having the specified extension.

• Reject: Indicates that the system will reject files having the specified extension.

Enter the URL that corresponds to the current (source) location of the file attachment archive to be copied.

Enter the URL that corresponds to the destination location of the file attachment archive to be copied.

Invokes the PeopleCode function (CopyAttachment) that copies the file attachment archive from the specified source storage location to the specified destination storage location. For example, you can copy from the FTP server to a database, a database to the FTP Server, and so on.

Prior to copying files to a database storage location, you must first prepare the target record to store the attachments, which is discussed in the PeopleCode Developer's Guide.

See Understanding the File Attachment Functions.

Displays the sample formats used for FTP, URL, or Record attachment transfers. These sample formats apply to both the Source and Destination edit boxes.