| Agile Product Lifecycle Management Administrator Guide Release 9.3.6 E71145-18 |
|
 Previous |
 Next |
| Agile Product Lifecycle Management Administrator Guide Release 9.3.6 E71145-18 |
|
Previous |
Next |
This chapter discusses how you can modify system-wide preferences in Agile PLM.
The Preferences node lets you view and configure Agile PLM's system-wide preferences and Languages.
|
Note: There is no connection between the Preferences node, which are systemwide server settings, and User Preferences, which are found on every user object (User Settings > Users node > [any user] > Preferences tab). However, a subset of the User Preferences are "system-related"; again, these do not pertain to settings in Preferences. |
To modify Preference settings:
Under Server Settings, double-click Preferences. The Preferences window appears.
In any editable field, enter a new value or select from the drop-down list.
When you have finished, click Save.
The following topics and describe the Agile PLM Preferences. They are listed in alphabetical order.
Default: No
For enterprises that utilize "Sites" information, this Preference can be set so the Default Site of a user is automatically added when the user creates an item.
Default: Disabled
Controls the user created Agile Drive access to Agile objects and documents outside of Agile.
Enabling the Agile Drive preference permits the administrator to access the Agile Drive system of managing the file attachments of Agile objects in the form of files and folders from your computer system, without requiring you to invoke the Agile application. It connects Agile's Distributed File Manager as a Network Place on your system, thus enabling Explorer-like operations, such as copy or delete, on file attachments of Agile objects. See "Administering Agile Drive" and Agile PLM Agile Drive User Guide for more information.
Default: Off
Sets "level" of logging on an Agile system. A production system might be set to a lower level, such as Off, Error, or Warn. A development system would likely be set to a higher level, such as All, Debug, or Fatal.
Settings are All, Debug, Error, Fatal, Info, Off, or Warn.
Default: No
Controls whether your users will have access to the Java applets that permit the use of an Open File plugin in Web Client and the use of a Microsoft Excel-based Client that is integrated with Agile PG&C.
Settings are No and Yes.
This preference controls whether your users — specifically Web Client users — will have access to Java applets that permit advanced features.
When this preference is set to Yes:
Allows the Microsoft Excel-based Client to be integrated with Agile PG&C, which allows supplier users to provide compliance information to buyers while using Microsoft Excel.
In Web Client, allows the use of an Open Plugin that opens an attached file in its native application. This plugin is used when:
The user selects one or more file rows and then clicks the Open button.
The user clicks the filename link in the attachment table, and the file extension has not been defined as a viewable file. See "Specifying Supported File Types for AutoVue for Agile."
When this preference is set to No, the Web Client file Open action is the same as the file Get action.
Default: No
The Allow Password Reset preference lets you choose whether Web Client users who forget their password can automatically receive a new one by clicking a link on login screen.
The default setting is No, which forces a user to contact the administrator to reset the password. Java Client users who forget their password must contact the administrator for a new one.
When Allow Password Reset is set to Yes, the Forgot your password? link appears on Web Client's login screen. Since Preferences are systemwide settings, every Web Client user sees the link. If a user clicks the Forget your password? link, he can enter his username and email address to receive a new random seven-character password. When the user logs into Web Client again, he is prompted to choose a new password.
Default: Yes
Allows Agile PLM to manage pointers to unsecured URLs, that is, it allows attachments to be URLs (as opposed to files). If you select Yes, pointers to URLs are stored on the Agile Application Server computer, although Checkin and Checkout are disabled for referenced URLs.
Default: Yes
Allows Agile PLM to manage pointers to unsecured URLs, that is, it allows attachments to be URLs (as opposed to files). If you select Yes, pointers to URLs are stored on the Agile Application Server computer, although Checkin and Checkout are disabled for referenced URLs.
Default: 60
This preference specifies the delay time, in seconds, before the system assumes that the start up of the AutoVue client has failed.
The AutoVue client start-up process can take some time to complete because Java classes must be downloaded to the client machine and the browser may prompt the user before starting any download.
Specify the delay in seconds.
Default: Disabled
Sets whether to enable or disable checksum computation for attachment files.
Settings are Enabled or Disabled.
Default: 5
The Content Service Maximum Retries preference controls how many times, after the initial attempt, a transfer order object will attempt to make delivery to a failing destination before further delivery attempts are blocked.
For example, if this setting is 5, the transfer order object will make one attempt at delivery. If that attempt fails, the transfer order object will make up to 5 more attempts. After the last attempt, further delivery attempts are blocked.
Default: 300
Determines how often the Content Server "wakes up" to check for transfer order objects to process.
The Content Service Wait Time preference controls how often the system processes transfer order objects. For example, if this setting is 300, every 300 seconds the system checks if there are any transfer order objects to process and begins to process them.
Default: FirstName LastName
Names of users appear with the first name appearing before the last name, or vice versa (with appropriate comma).
If you change the Default User Name preference setting, then you must restart the server for the change to take effect.
Default: No
Determines whether the change number associated with the selected revision is displayed beside the revision in the Revision attribute drop-down list on the Relationships table.
Default: Yes
Determines whether or not to display PPM Content Objects in the Navigator pane.
Default: Yes
Text and Multitext fields enable typed URLs to automatically convert to hyperlinks. Setting this to No will display URLs typed in Text and Multitext fields as plain text.
Note that certain "URL" and "mail" fields in Agile are not controlled by this preference; they will always convert typed URLs to hyperlinks.
Default: No
Determines whether or not User IDs (usernames) appear.
If you change the Display User ID preference setting, then you must restart the server for the change to take effect.
Default: 1048576
Maximum size, in bytes, of each chunk or portion of files that are downloaded during the file download process. If the file download is stopped or paused, when the file download is resumed, Agile PLM resumes downloading with the last chunk that had not been completely downloaded when the file upload process was paused.
Valid settings 1 - unlimited (0).
Maximum specified setting: 9999999999 (9,999,999,999)
See also "Download Max Chunk Size."
Default: 5
Number of concurrent download transfers that one user is allowed.
This limit is applied per user, regardless of how many browser sessions the user has pen.
Valid settings 1 - 20.
See also "Download Max Concurrent Transfers."
Default: 10
Maximum number of times a user may resume a download transfer.
Valid settings from 0 - no upper limit.
Default: 1440
Duration of the time period (in minutes) during which the user may resume a download transfer.
Valid settings from 0 - no upper limit.
See also "Download Token Use Duration."
Default: No
Determines whether or not BI Publisher is used to generate reports in multiple output formats.
Setting this preference to Yes generates reports in multiple output formats using BI Publisher. Setting this preference to No means that reports continue using existing reporting layout.
Default: 10
Determines how many times any script will run. If you intend that scripts run multiple times to complete their designed operation, adjust this setting to the desired maximum times allowed. But other scripts will also run multiple times, with possible unintended effects.
Default: All
Sets the level of logging in Event Handler Monitor (System Settings > Event Management).
Settings are All (logs all invoked Subscribers), Error (logs only errors), or Off (does not display log information).
Default: agile
Agile File Manager uses a prefix that is attached to each file that is stored in the file vault. Type in the identifier that will be automatically added to every attachment file. The default is "agile".
|
Caution: This effects of this systemwide preference are far-reaching and the value should not be changed without good reason. |
Default: 300
The "garbage collection" is a thread for cleaning out idle threads in the cache. After "cleaning," garbage collection is put to "sleep" for the number of seconds in this setting. 300 seconds (5 minutes) is a reasonable value.
Default: No
When set to No (default) then mobile streaming files are not generated and file rows sent to the Agile PLM mobile client are not marked for viewing.
When set to Yes, then Agile PLM generates mobile streaming files in the same configuration as for other streaming file generation.
To properly generate mobile streaming files, the Thumbnail and Streaming File Pre-Generation system preference must be enabled and the File Manager advanced setting (Enable Pre-Generation by Vue Server) for Thumbnail and Streaming File Generation must be selected. See "Advanced File Manager Fields."
|
Note: When changing this preference from No to Yes, consider bulk generation of all streaming files to prepare the Agile system. |
When changing this preference from Yes to No, pre-existing mobile Viewing Files are not automatically removed. They remain in the system, unused, until you purge all streaming files.
|
Note: When changing this preference from No to Yes, then the Application Server and the File Server must be restarted. |
Default: (Randomly generated)
In Agile PLM 9.3.2 a keystore has been introduced into the Agile PLM system to improve system security and support new encryption algorithms. The keystore password is the password used to access keystore and retrieve keys in the keystore.
The keystore password is randomly generated by the Agile PLM installer when the Agile PLM server is installed.
Default: Disabled
Pertains to the Engineering Collaboration solution. When set to Enabled, a Load to CAD button appears and is functional in Web Client. Design objects can then be uploaded to your designers' CAD system.
Default: 250
Maximum number of historical file transfers displayed in the in the file upload manager.
Valid range is 0 - 500Valid range is 0 - 500.
Default: 5000000
Maximum number of nodes that can be processed in the BOM Comparison report.
Valid range is 1 - 5000000.
Default: 50,000
The default Maximum BOM Report Results preference is set to 50,000 rows. The upper limit to this field has been increased to 500,000 (a comma is not needed in the field).
The Maximum BOM Report Results preference determines maximum number of objects displayed in Agile PLM BOM reports.
If the limit is reached when a report is requested, then the report will not execute and the user is notified with an error message.
The value of this preference setting is applied to the following Standard Reports:
Assembly Cost (Item Master)
BOM Comparison Report
BOM Explosion Report
Effective BOM Explosion Report
Manufacturer BOM Report
BOM Compliance Report
|
Note: This setting does not apply to the Product Where Used Report, Sourcing Project Assembly Cost Report, or Supplier Response Assembly Cost Report from the PCM standard reports. |
|
Caution: This preference is overridden by the Full Search Display (FSD) privilege. Users with the FSD privilege see all results of reports; also, all privilege checking is bypassed on users with this privilege when they view report results. Users without the FSD privilege see the maximum number of report results specified in this property. |
Default: 0
Determines the maximum number of records for Agile to process to reach the Maximum Query Results Displayed value.
When the value is set to 0, users who have very restricted Discover privileges can run a search, which checks every object in the system in order to reach the Maximum Query Results Displayed limit. This Maximum Database Records to Process for Searches limit is used to cap how many objects are checked in order to limit the impact to the server and reduce risk of performance problems.
If there are performance problems with restricted user searches, a reasonable number like 50,000 should be used to improve performance.
The range for this preference is 0 or 1000-99999999. 0 signifies that the entire database is searched. (1-999 is not a valid setting.)
Default: 250
Determines the maximum number of list values that can be displayed in a list widget.
This value cannot be higher than 2500.
0 and negative numbers are not valid.
When the list widget is displayed, if the number of rows exceeds this setting, a message is displayed indicating that the number of results rows is limited to this setting.
|
Note: If a list's Display Type sets to List, searching a value will only be executed within the displayed values.If a list's Display Type sets to Search, searching a value will be executed among all values even if some values are not displayed.For more information about Display Type, see "Display Type for Lists in Web Client" in Agile Product Lifecycle Management Product Collaboration User Guide. |
Default: 50,000
The Maximum Non-BOM Report Results preference determines maximum number of objects displayed in Attachment History report and Where Used Report.
The upper limit to this field has been increased to 500,000 (a comma is not needed in the field).
Maximum Non-BOM Report Results cannot be used to retrieve BOM-related reports. For BOM reports limits, see "Maximum BOM Reports Results."
|
Caution: This preference is overridden by the Full Search Display (FSD) privilege. Users with the FSD privilege see all results of reports; also, all privilege checking is bypassed on users with this privilege when they view report results. Users without the FSD privilege see the maximum number of reports specified in this property. |
|
Note: The "Export to Excel" feature of search results (in Java Client, from page of Search Results: Export Search Result menu icon > Excel or CSV) regards this Preference: the number in this field limits the maximum number of results exported to Excel or CSV files. (This is not to be confused with this sequence accessed from Business Object: Actions > Microsoft Excel > Export to Excel, which does not use this setting.) |
Default: 1000
Sets a maximum number of search results that can be displayed (advanced or quick searches); can be any positive integer less than 5000, but 1000 is recommended.
If a user's Max Rows Displayed user preference is set to fewer rows than this systemwide preference, the former value will override the latter value.
Caution: The Full Search Display privilege applies to results of report queries, not to ordinary searches. All users, whether or not they have the Full Search Display privilege, will see the maximum number of search results specified in this property.
Default: 10 (in a single-node PLM system or per-node in a clustered system)
Defines maximum number of reports that the application server will run simultaneously.
|
Note: This setting is enforced per node in a cluster environment. A cluster of 4 nodes would allow 40 simultaneous reports run. |
Default: 500000
This setting is used during Calculate Compliance for an item.
Valid range for this setting is 0 - 1000000.
When the item's BOM exceeds this preference setting, a message is displayed that informs the user that the BOM exceeds the limit for PG&C rollup, and to try again with a smaller sample size.
Default: 0
Determines the maximum number of BOM rows allowed to be displayed in the Web Client. This setting prevents very large BOMs overloading the system.
Default: 40
The maximum number of columns that can be displayed in the search results table or the custom report results table.
Valid range for this setting is 1 - 100.
Default: 0
Represents the maximum number of objects that should be allowed on an export. A zero value means there is no limit.
If you are exporting from ACS or the SDK, then the value in this field is ignored.
Default: One Column
Defines the layout display for Web Client form tabs.
Web Client form tab display can be set to One Column or Two Columns.
Default: Same Only
Restricts a single user from running the same report again until the first request has been completed.
No = user can run any report multiple times.
Same Only = user can only run one of the same report at a time, or run different reports at the same time.
Yes = user can run only one report at a time, of any type.
When user is running the same report, error message "You are already running an instance of this report. Please wait for that report to complete before running the report again" is displayed.
When user is already running a report, error message "You are already running a report. Please wait for that report to complete before running another report" is displayed.
Default: 1800
This setting is the timeout time for the user transaction in the notification thread. Valid setting is 30 to 3600 seconds.
Default: 600
Determines how often the system "wakes up" to check for email and inbox notifications to send. Default is 600.
Valid setting is 30 to 3600 seconds.
Default: 5
Upon the creation of a new external composition, the oldest archived composition is deleted if the number of archived compositions exceeds the number of this preference setting.
You cannot choose a number less than 0 (zero).
Default: Medium Table
Sets the relative size of the object cache table (Hashtable), which helps determine how objects are distributed in cache (smaller means more objects per row, larger means fewer objects per row).
You can choose Small, Medium, or Large Table (default is Medium Table), but it is an internally used attribute used in server implementation; therefore, no recommendation regarding performance is offered for this setting.
Default: Enabled
When there are more than two File Managers, allows the PLM system to keep track of the File Managers that contain each file. During replication, the requesting FM only contacts other FMs that contain the file, and downloads a given file from the nearest FM (shortest 'ping').
Settings are Enabled or Disabled. Disabled can be set to troubleshoot problems with the optimizations.
Default: SHA-256
To improve the system security, the Agile PLM system switches to SHA-2 cryptographic hash functions (SHA-256, SHA-384, SHA-512) when generating an Agile PLM user's password hash.
Default: 0
The default value of 0 means the system behaves with the error message: "This object has been modified, please refresh and try again."
If the value is set to an integer other than 0, a warning message displays: "This will introduce a XX minute delay in synching the pending Where Used table."
Default: 6
Valid entry = 0 – 9
The Price Scale preference defines the number of decimal values (decimal places) used in Agile PCM (Product Cost Management) Money attributes.
The Price Scale preference value is copied to the Scale property of all PCM Money attributes. The Scale attribute property cannot be changed on the Money attribute itself.
|
Note: When the Price Scale preference is modified, then you must restart the server for the new Price Scale value to take effect. |
The Agile PCM (Product Cost Management) Money attributes that are affected by the Price Scale preference are listed in the following table.
In Web Client, these Money attributes use the number of decimal values specified in the Price Scale preference.
In Java Client, PCM Money attributes use 6 decimal values, the default, regardless of the Price Scale value.
Non-PCM Money attributes also use 6 decimal values, the default. The Price Scale preference does not affect non-PCM Money attributes.
The following table lists the PCM Money attributes that are affected by the Price Scale value.
Table 34-1 Agile PCM Money attributes
| PCM object tables | Money attributes affected by Price Scale |
|---|---|
|
Sourcing Project - Price Details |
Material Price Addr 1 – Material Price Addr 7 Non-Material Price 1 – Non Material Price 25 Non-Material Total NRE Total Material Total Material(s) Total Price Total Price(s) Extended Price Extended Standard Cost Material Price Target Cost |
|
Sourcing Project - Analysis - Rollup Price Entry |
Total Unit Cost Total Materials Price Total Non-Materials Price Total Extended Cost |
|
Sourcing Project - Analysis - Analysis |
Standard Cost ipnMoney1 – ipnMoney5 mpnMoney1 – mpnMoney5 respMoney1 – respMoney5 |
|
Sourcing Project - Analysis - Costed BOM Analysis |
Standard Cost |
|
Sourcing Project - Analysis - Non Material Price Entry |
Total Non-Materials nonMaterialModifier1 – nonMaterialModifier25 |
|
Sourcing Project - Items |
Standard Cost money01 – money05 |
|
Sourcing Project - AML - Items |
money01 – money05 |
|
Sourcing Project - AML - AML |
money01 – money05 |
|
Prices - Price Lines |
Material Price Material Price 1 – Material Price 7 money01 – money05 Non Material Price 1 – Non Material Price 25 Non Recurring Cost Total Material Price Total Non Material Price Total Price |
|
Request for Quote - Responses |
ipnMoney1 – ipnMoney5 mpnMoney1 – mpnMoney5 respMoney1 – respMoney5 |
Default: 10
Controls the maximum number of objects that each user can store.
The list selection allows these values: 10, 25, 50, 100.
Default: No
When enabled, Agile PLM logs, in the database, the user's complete Recently Visited history for each login session.
For more information, see "Recording User Actions in the Database."
Default: Disabled
Enables the tracking of simple searches. Agile PLM records, in the database, basic information about the simple searches that have been run.
For more information see "Recording User Actions in the Database."
Default: Hyphen (-)
The symbol that appears between lower and upper range values in reference designator statements.
Available symbols are asterisk (*), at (@), caret (^), plus (+), hyphen (-), colon (:), semicolon (;), tilde (~), or None.
Default: Collapse
Allows reference designators to be described as a range instead of a sequence.
The Reference Designators Allow Range Expand Collapse preference (RDAREC) determines how reference designators are displayed in the BOM table when not in edit mode. This preference affects only the end user display of the reference designator data stored in the Agile database.
Expand – Displays ranges of reference designators in expanded format; each reference designator is listed and the range is not collapsed. For example, the range of reference designators beginning with R1 and ending with R5 is displayed as:
R1, R2, R3, R4, R5
Collapse – Displays ranges of reference designators in collapse or concatenated format. Ranges of reference designators (3 or more reference designators in a sequence) are indicated by the first reference designator in the sequence, the reference designator range indicator character, and the last reference designator in the sequence. For example, the range of reference designators beginning with R1 and ending with R5 is displayed as:
R1-R5
Default: Don't skip
In escalation and reminder periods of changes, determines how the system will count weekend days (Skip Saturday or Sunday, Skip Saturday and Sunday, or Don't Skip [= count both weekend days]). This preference is not part of Product Portfolio Management scheduling.
Default: Warning
Settings are Delete, Retain, and Warning.
When adding an attachment to a business object or checking it in, determines whether local files (on user's computer) will be deleted or retained, or whether the user is prompted to choose to delete it (Yes) or not (No).
|
Note: This preference is applicable only in Advanced uploader, and is not applicable in Standard uploader: Standard uploader does not delete files automatically when this preference is set to Delete. |
Default: Reference existing file(s)
Permits one of two ways to replicate a file, or allows each user to be prompted to choose the method. Settings are Prompt, Create new copy of file(s), Do not copy file(s), and Reference existing file(s). For more information, see "Save As Attachments."
Default: Values Copied
Indicates whether or not to copy BOM tab values when copying from one item to another.
|
Caution: There are exceptions to copying values during Save As operations. If an attribute in the source object does not exist or is not used in the target object, it is not copied even if the Save As preference is set to Values Copied. Also, if an attribute is a list value and the list ID of the source attribute is not the same as the list ID of the target attribute, the value is not copied even if the Save As preference is set to Values Copied. |
Default: Values Copied
Indicates whether or not to copy Manufacturers tab values when copying from one item to another.
|
Caution: There are exceptions to copying values during Save As operations. If an attribute in the source object does not exist or is not used in the target object, it is not copied even if the Save As preference is set to Values Copied. Also, if an attribute is a list value and the list ID of the source attribute is not the same as the list ID of the target attribute, the value is not copied even if the Save As preference is set to Values Copied. |
Default: Values Copied
Indicates whether or not to copy Page Two tab values when copying from one class to another.
|
Caution: There are exceptions to copying values during Save As operations. If an attribute in the source object does not exist or is not used in the target object, it is not copied even if the Save As preference is set to Values Copied. Also, if an attribute is a list value and the list ID of the source attribute is not the same as the list ID of the target attribute, the value is not copied even if the Save As preference is set to Values Copied. |
Default: Values Copied
Indicates whether or not to copy Page Three tab values when copying from one class to another.
|
Caution: There are exceptions to copying values during Save As operations. If an attribute in the source object does not exist or is not used in the target object, it is not copied even if the Save As preference is set to Values Copied. Also, if an attribute is a list value and the list ID of the source attribute is not the same as the list ID of the target attribute, the value is not copied even if the Save As preference is set to Values Copied. |
Default: Values Copied
Indicates whether or not to copy Page Three tab values when copying from one subclass to another.
Default: No
When set to No, Agile PLM checks for duplicates in the search results only in adjacent rows.
When set to Yes, Agile PLM retrieves the search results and then checks for duplicates regardless of row order.
Default: Row
Settings are Row (default) or Table. If set to Table, Search Based On applies to the following 5 tables only:
All Attachment tables
Item.BOM table
Item.Manufacturer table
Item.Compliance table
MPN.Compliance table
Search Based On set to Table allows the user to use the And search operator for table attributes. For example:
Item.Manufacturer Name is equal to ABC And DEF
returns items with both ABC and DEF manufacturers on the Manufacturers table.
In contrast, when Search Based On is set to Row, the above search returns no results because a row cannot have a manufacturer name that is both ABC and DEF.
Default: N/A
The Signoff User Dual Identification Type preference controls whether approve/reject signoff (including a user signing off for "self" or for another user due to Escalation or Transfer Authority) requires a dual identification, or "second signoff."
The settings are:
N/A (Not Applicable, the default)
User ID
Login Password.
Selecting N/A means that these situations will not require a dual ID; selecting either User ID or Login Password means a dual ID is always required to sign off.
FDA-regulated or other companies may have a corporate policy that requires double authentication of user identify in approving or rejecting change orders. The Signoff User Dual Identification preference controls whether approve/reject signoff requires a dual identification, or "second signoff."
This setting is applied to the Review and Released statuses of all default and custom workflows, that is, when the Signoff dialog is filled in by a user, the system verifies the electronic signatures before advancing the workflow to the Review or Released status. The preference comprises all situations when the user is signing off for himself, signing off as a member of a user group, signing off for another user due to Escalation or Transfer Authority, or a combination of signoff responsibilities. (The Signoff UI options are detailed in Getting Started with Agile PLM, the chapter about Workflow.)
The administrator must attend to a combination of settings to properly realize the "second signoff" functionality.
Setting this preference to N/A (Not Applicable, which is the default) means that signoffs require only a single signoff from any user in any capacity. The password already required to sign off is the Approval Password; this represents the first level of security in the signoff protocol.
The other two settings, User ID and Login Password, effectively enable the dual ID requirement for any user in any signoff capacity. They dictate that users also be required to enter their User ID (also called username), or the Login Password.
If you set this preference to Login Password, then it is imperative to ensure that every user's Use Login Password for Approval property is set to No; once you change all users' Use Login Password for Approval property to No, only then can you set the Login Password. (For bulk settings, contact your Agile representative for a script called SecondSignature.Zip.)
If you set this preference to User ID, then you should set Display User ID preference to No.
Default: 300
Valid setting is 30 - 3600 seconds.
One of the settings that determines when certain system actions, such as cleanup and reset tasks, are performed on any object that is idle in the logged-in user session longer than the value of the setting.
Default: Disabled
Enables the system to present thumbnail representations (small bitmap icons) for Agile object attachment files in Web Client.
See Chapter 45, "Administering Thumbnails."
For more information about how thumbnails are displayed in Web Client, see Getting Started with Agile PLM, chapter "Working with Thumbnails."
Default: Disabled
Determines whether thumbnails and streaming files are pre-generated by AutoVue by each file manager.
Default: 10485760
Valid settings 1 - unlimited (0).
Maximum specified setting: 9999999999 (9,999,999,999)
Maximum size, in bytes, of each chunk or portion of files that are uploaded during the file upload process. If the file upload is stopped or paused, when the file upload is resumed, Agile PLM resumes uploading with the last chunk that had not been completely uploaded when the file upload process was paused.
See also "Upload Max Chunk Size."
Default: 5
Valid settings 1 - 20.
Determines the maximum number of parallel concurrent file transfers of multiple files to one client.
This limit is applied per user, regardless of how many browser sessions the user has open.
See also "Upload Max Concurrent Transfers."
Default: 25
This setting dictates the number of minutes corporate users can be idle in Web Client before Agile terminates the session.
|
Note: The proxy server for your Agile PLM system has a default connection timeout of 1500 seconds, or 25 minutes. For information on how to change the proxy timeout setting, see the chapter "Installing and Configuring Agile Web Components" in the Agile PLM Installation Guide for Windows. |
Default: 25
This setting dictates the number of minutes supplier users can be idle in Web Client before Agile terminates the session.
|
Note: The proxy server for your Agile PLM system has a default connection timeout of 1500 seconds, or 25 minutes. For information on how to change the proxy timeout setting, see the chapter "Installing and Configuring Agile Web Components" in the Agile PLM Installation Guide for Windows. |
The Languages tab lists the available languages for the Agile system. The administrator can select one or more languages at a time and enable or disable them using the Enable/Disable buttons.
By default, English is enabled and you cannot disable English.
You will be able to see in two columns the name of the language and whether or not the language is currently enabled or disabled with a setting of Yes or No.
This list of supported languages is current as of May, 2011 and is subject to change. See the languages tab found in the Preferences node for your current installation supported languages.
Once you are finished with applying the settings you desire then click Save. At this point there will be a message alerting you that you must restart the server to apply the changes.
The Agile PLM server will successfully load translated labels and fields for languages that are enabled. The Administrator history is only generated for enabled languages.
User preferences for languages are limited to the enabled system languages.
For more information about Agile PLM Language settings, see "Administrator Nodes in Java Client."
