Configuration settings take priority over the default settings. When a non-administrator user starts AutoPilot Toolkit for an Automation or Comparison run, the available settings are governed by the configuration settings and the default settings. This file can be selected in AutoPilot Toolkit’s General tab.
The file content is altered using the Administrator Module. The settings are stored in an XML file that can easily be transferred from one computer to another, or made part of an internal distribution for consistent implementation across an organization. The administrator-defined settings, or configuration settings, define the default options available to users for automation and comparison projects. Designated AutoPilot Toolkit administrators (authenticated by user name and password) can modify these settings and adjust them to meet a company's or working group's SOPs. If English is not selected for non-Unicode programs, then the PK_Stats.xls and Summary_PK_Text.doc files are not created.ĪutoPilot Toolkit comes pre-configured and ready to use “out-of-the-box” with default settings. In Chinese and Kanji (Japanese) versions of Windows, the language setting for non-Unicode programs must be set to English (United States). This ensures that the template settings will refresh and the columns in the input source will be accessible through the template. Save the project, close it, and load it again. In the special situation where a custom XML settings file is used and saved with an AutoPilot Toolkit object as part of a template in a workflow, it is recommended that the AutoPilot object be disconnected, the custom settings file selected again, and the input reconnected. Note: This checkbox does not control an AutoPilot Toolkit object that is in a nested sub-workflow. Users can change this default behavior through a preferences option available in the Phoenix Preferences dialog ( Edit > Preferences, select AutoPilot in the list).Ĭheck the Execute as Part of Workflow checkbox to include AutoPilot Toolkit objects in workflow execution. This is done to avoid very long run times. However, when a Workflow object is selected and is clicked, all operational objects in that workflow, except AutoPilot Toolkit objects, are run. This application is not intended to provide the technical controls required for a 21 CFR Part 11 compliant implementation.Īn AutoPilot Toolkit object can be incorporated into Phoenix workflows as with other Phoenix objects. The Phoenix desktop icon should be replace with one that references the Phoenix32 executable as well.
Note: AutoPilot Toolkit users should run Phoenix32 as opposed to Phoenix when running on 64-bit operating systems.
Language settings for non-unicode programs This section contains the following topics:
0 kommentar(er)
