Dell Statistica Web Data Entry

Transcription

1 Dell Statistica Web Data Entry for Release 13.0 September 2015 This administrator guide provides information about Dell Statistica Web Data Entry for release Topics: Overview Definitions Unique Values, Labels System Users System Groups (Permissions) System Options Audit Log System Options Data Entry System Options IIS, Application Settings System Options IIS, Session State System Options Sample Comment Troubleshooting Slow To Load Work Flow Examples Deprecated features Installation Notes About Dell

2 Overview Statistica Web Data Entry makes it possible for companies to configure data entry scenarios and to administer data entry via web browsers, as well as analyze the data using all the graphical data analysis, statistical analysis, and data mining capabilities of the Statistica Enterprise software platform. Manual data entry administrators create fields (Characteristics and Labels) and add them to the web forms (Data Entry Setups) with the Statistica Enterprise Manager application. The Data Entry Setup is saved in a folder (System View), and users are granted access to enter data and approve entered data. The manual data entry employee opens a browser and visits to enter data. The administrator creates additional objects in Statistica Enterprise Manager to retrieve the data (Data Configurations) and to analyze the data (Analysis Configurations and Reports). The image below shows the relationships between the Statistica Enterprise Manager objects. Statistica Web Data Entry objects in the diagram above are: Characteristics: Numeric fields for a web form (e.g., ph) Labels: Text or date data for a web form (e.g., Lot Number) Data Entry Setups (DES): Groups of Characteristics and Labels configured with specific User/Group permissions to collect the appropriate data via a web form System View: Folder structure that is used to organize the objects. The names of the folders are metadata and are used to communicate to manual data entry employees. Optionally, multiple Data Entry Setups can be grouped together and ordered within the Data Entry Setup Sequence. The Data Entry Setup Sequence is not listed in the diagram above because it only influences the display of web forms. The individual entering data will be guided from one form to the next form. A Data Entry Setup can only be added to one Sequence object. Definitions Functionality in Statistica Web Data Entry: Term Analysis Configuration Definition Settings within Statistica Enterprise Manager that control the analysis of data. There are IQC, SVB, Ad hoc, and R configurations. Typical work flow: An analyst creates the configuration. A group of people will execute the configuration when the information is needed. These configurations can also be executed to generate reports. The Database Connection and Data Configuration must be created before the Analysis Configuration can be created. Analysis Admin (AADM) permission must be granted to users who will create Analysis Configurations.

3 Term Data Sample Data Verification and Approval Double Blind Data Entry Characteristic Concurrent License Manager Configuration or Object Constraints Database Connections Data Configuration Data Entry Setup (DES) Data Entry Setup Sequence (Sequence) Data Entry (DE) Data Entry Approver (DEAPPRV) Data Entry Admin (EDE) Historical Edit (HEDIT) IQC Label Definition After data is entered into a web form, this data is a sample or record. Referred to as data sample or data record. There are three methods for reviewing, approving, and electronically signing approval of data that has been entered correctly. 1. Approval of sample: One person enters data. Second person manually reviews entered data and approves or rejects data. 2. Blind data entry, manual approval: Two people enter the same data. The system compares the two samples. Third person logs on to system and reads report about the differences between the two samples. Third person approves or rejects the data. 3. Blind data entry, automatic approval: Two people enter the same data. The system compares the data. The system approves or rejects the data. Also known as blind data entry, two people enter the same data. The accuracy of the data entry is verified by comparing the two different records. Numeric data to be collected for analysis (e.g., ph). The numeric data can also be verified during data entry. A reasonable low and high number can be set to help improve the accuracy of data entry. Other verification rules can be set on this option such as the maximum number of decimal places or a calculated value. They are fields on a Data Entry Setup (web form). Create a characteristic once, and use many times on different Data Entry Setups. An application that is part of the Statistica Enterprise suite of products produced by StatSoft. It provides administrators with the ability to identify who is using the analytical or data entry components, and the number of licenses currently in use. These are objects managed with Statistica Enterprise Manager such as Data Configurations. The Constraints options are set on Data Entry Setups. Constraints are rules that restrict the values that can be entered for the different characteristics and labels in a Data Entry Setup. Settings (OLEDB or ODBC provider, login name, password) that control the connection to the database. Database Admin (EXTDB_ADM) permission must be granted to users who create these connections. Some companies may limit this ability to information technology employees. Settings (SQL and filtering criteria) that control querying data. This configuration must be created prior to creating an Analysis Configuration. The Database Connection must be created before the Data Configuration can be created. Data Admin (DADM) permission must be granted to users who will create data configurations. Users who need access to raw data can be granted access to run this configuration. Groups of Characteristics and Labels configured with specific User/Group permissions to collect the appropriate data for particular scenarios. This creates and controls the web forms that manual data entry staff will use. A configuration that provides the means for an administrator to sequence the order of web forms. For example, data must be entered on the Monday form before data is entered on the Tuesday form. Data entry user permission. This user can open with Internet Explorer and start entering data. Data entry approver user permission. This user can open with Internet Explorer and start approving data or request data revisions. Data entry administrator user permission. This user can create characteristics, labels, and data entry setups. Historical edit user permission. This user can edit data after it has been marked Complete. Interactive quality control is a type of Analysis Configuration. Text or date data for traceability (e.g., Lot Number). They are field definitions for a Data Entry Setup (web form). Create a label once and use many times on different Data Entry Setups.

4 Term Metadata Override (OVR) Piece QC Statistica Statistica Enterprise Statistica Enterprise Manager Statistica Enterprise/QC Statistica Query or Statistica Advanced Query Builder SVB System View URL Definition The Statistica Enterprise Manager application manages metadata for analytic projects. There are two types of metadata. 1. Metadata can be used to describe or classify data. For example, a process can be upstream or downstream. This type of metadata can be captured with a Label on a web form, or be a Data Entry Setup name or a System View Folder name. 2. Metadata is also used to describe information saved within the configurations. For example, a Database Connection contains metadata on how to connect database type (Oracle, SQL Server, Access, and flat file), login account, and password. Override user permission. This user can override the reasonable values that are defined on a Characteristic. This permission is typically provided to expert users only. A type of characteristic or label that can have multiple entries per sample (batch). Quality Control Application that is part of the Statistica Enterprise suite of products. This application can be installed on a server and client computer. It contains the statistical analysis and data visualization functionality. The product name for a suite of applications for Enterprise wide analytics. Application that is part of the Statistica Enterprise suite of products. This application can be installed on a server and client computer. It provides the means for controlled creating, editing, and sharing of labels, characteristics, Data Entry Setups, database connections, data configurations, analysis configurations, and reports. This application manages metadata about analyses. Quality Control functionality that is provided via IQC Analysis Configuration. Applications are installed on the server and client computer. These utility applications are used to easily access data via SQL from a wide variety of databases (including many large system databases such as Oracle, MS SQL Server, Sybase, etc.) using Microsoft OLE DB or ODBC conventions. Statistica Query can also run MDX queries. Statistica Advanced Query Builder has a drag-and-drop user interface to build queries. Statistica Visual Basic (script language). SVB is a super set of the industry-standard Visual Basic language. Folder structure defined in the Statistica Enterprise Manager application to organize the storage of configurable objects. A Data Entry Setup object would be saved in a folder in the System View. Uniform Resource Locator. The address of a web page. Manual data entry employees use the URL name]/dataentry to log into the system and enter data.

5 Unique values, labels If a label will contain a unique value, it must be a sample label. Examples of unique values are batch ID, lot ID, locator record, customer frequent buyer number, and transaction number. Configuring a label object to contain a unique value is the method for preventing duplicate data entry. For example, suppose you manufacture a drug in three batches; A, B, C. The data has been entered for all three batches. If someone tries to enter data for batch A again, you want the system to display an error and prevent the duplicate data. A unique value is also needed with double-blind data entry. Blind data entry requires two people to enter the same data record. The system needs to know that two specific records should be compared. There are four different methods for identifying a label as unique. 1. System Option for all Data Entry Setups: Select Require approval of samples as the approval type on the Data Entry Setup. The value must be unique across data samples in a Data Entry Setup. For configuration details, read about UniqueLabels in the System Options, IIS section. This option works well if the number of unique labels is small. 2. Option for specific Data Entry Setup: Add sample label to the Input s property page for a Data Entry Setup. Double-click on the label or select the Edit option. Then select the option Verify label value is unique for the Data Entry Setup on sample save. 3. Option for blind data entry: Select Blind data entry for the approval type on the Data Entry Setup. The value must be unique across samples in a Data Entry Setup. While creating the object, the user will be prompted to declare a Blind ID. 4. Option for product Statistica Product Traceability: Configure a label for Statistica Product Traceability and add it to a Data Entry Setup. The value must be unique for all data that is entered in to the system. The Product traceability options must be selected on the Label and the Data Entry Setup. System users The Statistica Enterprise Manager application is used for maintaining users and groups. There are two types of users: Native Statistica Enterprise users Imported Windows domain users Native Statistica Enterprise users exist only within Statistica Enterprise and Web Data Entry. They are created by clicking the New User button in the Enterprise Manager application. Domain integrated log on is possible when you import existing Windows domain users. NOTE: The SYSTEM user was added to Statistica Enterprise Manager to support the blind data entry process. The system records that the SYSTEM user last modified a web form to either approve or require revision. This user cannot be deleted or modified. Dell Statistica Web Data Entry 5

6 System groups (permissions) We recommend structuring groups with the Enterprise Manager application for: System Level: Groups are created to contain users who should have access to the system. These groups define what applications or areas of the system can be used. These groups are typically named Statistica User, Folder Admin, Analysis Admin, Analysis User, Data Entry Admin, Data Entry Approver, and Data Entry User. These groups can be linked to Domain groups. A daily job can be set up to refresh (add and delete) the user accounts from domain groups. With this type of configuration, IT will not need to add or delete new users. Object Level: Groups are created to grant edit and read permission to configurations. This makes it easier for Team North to share configurations with the entire team. These groups typically do not contain any system permissions. Following is a list of system permissions that can be applied to users or groups. NOTE: System Admin (SADM) has all of the permissions listed below. Typically, IT has this permission in a production environment. And the business lead has this permission in the test and development environments. Occasionally because of a customer s process, this permission will be issued to a technical business lead so that they can migrate/promote objects from development to production. Alarm Admin (ALRMADM). This user can acknowledge alerting tasksets and alarm dashboards (green, yellow, red) that are displayed with the Statistica Monitoring and Alerting Server product. When this product is owned with Statistica Web Data Entry, customers can set up alarms based on quality control charts for the manually entered data. Analysis Admin (AADM). This user can create Analysis Configurations. Data entry administrators may need this if they are creating a New Analysis Configuration off a Data Entry Setup. This permission also grants the right to start and use Statistica Enterprise Manager. Automated Collection (ADC). Deprecated starting with Statistica 13.1 Dashboard User (DUSR). This user can display alarm dashboards on the Statistica Monitoring and Alerting Server. Dashboards are typically displayed via a web browser. Data Admin (DADM). This user creates Data Configurations. Data entry administrators may need this if they are creating a New Data Configuration off a Data Entry Setup. This permission also grants the right to start and use Statistica Enterprise Manager. Data Entry (DE). This user enters data via a web browser. Data Entry Admin (EDE). This user creates Characteristics, Labels, and Data Entry Setups (i.e., sets up the data entry form). This permission also grants the right to start and use Statistica Enterprise Manager. Data Entry Approver (DEAPPRV). This user approves or requests revisions to the entered data via a web browser. Folder Admin (FADM). This user can create, delete, rename, or move folders in Statistica Enterprise Manager. This permission also grants the right to start and use Statistica Enterprise Manager. Historical Edit (HEDIT). This user can edit mark data as Complete. Think of this user as a super user for data entry. Override (OVR). This user can enter data that is outside of the low and high range for numeric values. This option is used in complex processes where there is subject matter expertise. Report Admin (RADM). This user can create Report objects to format the results of an Analysis Configuration. This permission also grants the right to start and use Statistica Enterprise Manager. Server Task Admin (STADM). Required to configure Server Tasks for use by the Statistica Monitoring and Alerting Server. This permission also grants the right to start and use Statistica Enterprise Manager. System Admin (SADM). The system super-user, which enables the user to review/edit/delete any system configuration and is a super set of all of the other system permissions. Dell Statistica Web Data Entry 6

7 User (USR). This user can run Statistica. This base permission is needed for users who will be creating any configuration. They will create an Analysis Configuration in Statistica Enterprise Manager and then test the configuration in Statistica. User Admin (ADM). This user permission is typically granted to IT to manage system users and groups. This user also has the right to create, rename, move, or delete folders. This permission also grants the right to start and use Statistica Enterprise Manager. Web User (WUSR). This user can log into name]/webstatistica to use the system via a web browser. Typically this person reads reports or schedules jobs to run. Web Viewer (WVWR). This user can review reports via the Statistica Enterprise Server Knowledge Portal. System options audit log All data entry activities can be recorded in the audit log, which is controlled and displayed in Statistica Enterprise Manager. Under System Options, select Audit Log. In the properties page, select Data Entry Operation to log data entry activities. If you need to track the create/edit/delete activities for Data Entry Setups, select Data Configuration/Data Entry Setup. Select Data Entry Setup Sequence to log activities related to this object. NOTE: The Data Entry Input Method option is not used with the Statistica Web Data Entry product. System options data entry In Statistica Enterprise Manager, expand the System Options node and select Data Entry. These settings apply to all Data Entry Setups. The first option is self-explanatory. Select this check box to automatically add All to the criteria for all Labels in the Data Entry Setup when creating a new Analysis Configuration based on a Data Entry Setup. URL for Sample Editing is used by the system in outbound notifications on data entry tasks. It can typically be set to The example in the next image uses a URL. Dell Statistica Web Data Entry 7

8 Retrieve all data for characteristics, independent of Data Entry setup is not a common use case. Typically, you will create one Characteristic and use it across many Data Entry Setups. And you will analysis the Characteristic data based on the Data Entry Setup (form). Therefore, this option is not selected by default. Only select this check box if you are interested in analyzing Characteristics across all the Data Entry Setups. Regulated customers typically select Prompt for electronic signature on sample completion and Prompt for electronic signature on sample approval. These options prompt for an electronic signature when: 1. Data entry person clicks the Complete button 2. Approver clicks the Approve button The Allow users to approve their own samples option is typically turned off in validated environments if using the Require approval of samples option on Data Entry Setups. Regulated industries typically do not allow the same person to enter data and approve the data. This option can be useful for testing new Data Entry Setups in development or nonvalidated environments. The Allow users to approve their own samples option and Blind Data Entry, user making last change can also approve option may be turned on when using Blind Data Manual Approval on Data Entry Setups. Two people will enter the data. The second person will also approve the data. If these options are turned off, then you will need three people to perform data entry and approval. NOTE: Blind Data Automatic Approval uses the SYSTEM user to approve samples shortly after the matching data sample is entered. So there is no value in turning this option on for this workflow. The Default database connection for creating Data Configurations off Data Entry Setups option is a Database Connection that points to the Statistica Enterprise configuration database. This database is where data entered via Web Data Entry is stored. All Labels, Characteristics, Data Entry Setups, Database Connections, Data Configurations, and Analysis Configurations are also stored in this database. After installation, this database connection must be created and then used on this properties page. Dell Statistica Web Data Entry 8

9 System options IIS, application settings Other options are configured via IIS. On Windows Server 2008 R2, select the Start menu, Administrative Tools, Internet Information Services (IIS) Manager. On Windows Server 2012, start the Server Manager application, Tools menu, Internet Information Services (IIS) Manager. In the Connections section, open your [server name] and then Sites. Select and open Default Web Site. Select Data Entry. Double-click the Application Settings icon to display the list of application settings. Aspnet:MaxHttpCollectionKeys. This setting defines the maximum number of form elements that can exist on an ASP.NET page. We explicitly define this setting because some versions of ASP.NET default to 1000 form elements, which can cause problems saving large data entry forms. BlindDataEntryHideMatchingValue. Set this option to true to avoid displaying the Matching Value column on the Recent Samples list. This list is displayed after login into name]/dataentry. The Matching Value column displays the unique value (sample label) such as LOT123. Blind data entry requires that two people enter the same data. If this option is set to false, the second person can locate data entered by the first person on the Recent Samples list. The second person sees a blue icon next to LOT123. The user clicks on the icon to automatically create a new form and populates the label with LOT123. If this option is set to true, the second data entry user has to type LOT123 into the label field. BlindDataEntryMakePrimaryOnSave. Do not change this option without discussing with [email protected]. It should be false for most customers. BlindDataEntryPrepopulateMatchingSample. When a user is entering a matching sample for a Data Entry Setup that is configured with Blind Data Entry, if this option is set to true it will pre-fill all sample label values from the initial sample. BlindDataEntryShowUnmatchedValues. After the users have created the initial and matching sample for a Data Entry Setup configured with Blind Data Entry using automatic approval, if this option is set to true, when the users are accessing the samples it will highlight in red the input boxes with unmatched values and show the unmatched values. NOTE: If automatic approval is enabled, it highlights the differences between samples even if the samples aren t completed. ByColumnsFirstColumnWidth. The width of the first column displayed when a data entry form is configured to display the inputs by columns. ByColumnsWidth. Set the column width for fields on the Web Data Entry pages. ByRowsFirstColumnWidth. The width of the first column displayed when a data entry form is configured to display the inputs by rows. Dell Statistica Web Data Entry 9

10 ByRowsWidth. Set the width of the rows for the Web Data Entry pages. CommentNotRequiredOnApprove. When a user is approving a Data Entry Setup, if this option is set to true, it will not require a comment from the approver. The approver can optionally enter a comment. CompareSamplesCaseSensitive. When a Data Entry Setup configured with Blind Data Entry has both samples complete, if this option is set to true it will compare text labels using case sensitive value comparison. DateFormat. Controls the format of the date/times that are retrieved from the database. Dates could be entered as 10/1/2010 but displayed as ddmmmyy. DefaultDomainName. Most frequently used domain name used for integrated login. EditMaskChar. Value displayed by masked edit when nothing has been entered for a character. EditMaskInteger. When the option UseEditMaskToEnforcePrecision is set, this defines the string to display when nothing has been entered for an integer. FromAddress. Used for from address when sending validation status. GlobalRecentSamplesMaxNumber. This setting limits samples in addition to GlobalRecentSamplesNumberOfDays. This setting applies to the global listing across all Data Entry Setups. Blank causes the number of samples not to be limited and could cause performance issues. GlobalRecentSamplesNumberOfDays. After signing into Statistica Web Data Entry, the first page will display the recent samples. This variable controls the number of days of data that is retrieved regardless of the Data Entry Setup. Blank causes the samples not to be filtered and could cause a performance issue. LogAllSampleChanges. By default only changes made to a completed sample are logged. If this option is set to true, then even saving a change to a sample (not completing it, but saving it) will also be logged to the audit trail. LoginMessage. This HTML message is displayed prior to logging on to Web Data Entry. Copy your HTML code into the variable. Ensure that the HTML is all on one line. New lines are not acceptable. MainMenuMessage. This is deprecated and has no impact on the display. MasterPageLogo. File name of the image that is displayed in the upper-right corner. PromptForSampleSave. If set to true, an electronic signature is prompted even when the user saves the sample. If set to false, it will only prompt for the electronic signature when completing the sample. This allows for multiple user electronic signature confirmations for entering data on one sample. QueryLabelMaxEntries. This controls the maximum number of values to display in a query label combo box. RecentSamplesLabels. After signing into Statistica Web Data Entry, the first page display the recent samples. You can modify what labels are displayed for the recent samples. The label names are pipe delimited. For example, Batch Number ID Product Name RecentSamplesMaxNumber. If left blank causes the number of samples not to be limited (could cause performance issues). RecentSamplesNumberofDays. This variable controls the number of days of data that is retrieved after selecting a specific Data Entry Setup. If left blank, it causes the samples not to be filtered and could cause a performance issue. RecentSamplesPageSize. After signing into Statistica Web Data Entry, the first page will display the recent samples. This variable controls how many rows are displayed before paging in enabled. Send OnSampleApproval. If notifications should be sent when the Approve button is clicked by the approver, set this to true. Send OnSampleCompletion. If notifications should be sent when the Complete button is clicked by the data entry person, set this to true. SortSystemView. When selecting a web form (Data Entry Setup) to use in a browser, the folder structure and Data Entry Setups are in alphabetical order. Set this option to false to see objects sorted by their modification date. UniqueLabels. Labels that must be unique across samples in a Data Entry Setup. You can have multiple unique labels on a Data Entry Setup. The label names are pipe delimited. For example, Batch Number Batch ID ID. This is mainly used when the Require approval of samples option is turned on for Data Entry Setups. See the Label, Unique Values section. Dell Statistica Web Data Entry 10

11 UserEditMaskToEnforcePrecision. There are two types of precision enforcement. 1. Display ToolTips about the precision, and only enforce it once data entry is completed on the Characteristic. This is the more flexible option and is on by default. 2. Only allow the user to type the precise amount of numbers. Set this option to true if you need this type of enforcement. WebSTATHost. Name of server where WebStatistica is installed. System 0ptions IIS, session state By default, cookie based sessions are enabled. This prevents using multiple browser tabs (sessions) within one browser. To turn off cookies, start IIS. Double-click the Session State icon. Select Use URI from Cookie Settings. System options sample comment Data entered into the Sample Comments box is only visible via name]/dataentry. This field is used to communicate important information about data entry or approval. These comments are not retrieved with other form data by a Data Configuration or Analysis Configuration. If you need to include comments with the data that will be analyzed, create a Label and add it to Data Entry Setup. To increase the size of the comment box, you need to edit a file on the server: File path/name: C\WebSTATISTICAPub\DataEntry\StyleSheet1.css Modify the height and width fields in the.commentseditor section. Dell Statistica Web Data Entry 11

12 Troubleshooting slow to load If the Web Data Entry User Interface is slow to load after logging in, it is often because the list of recent samples is long; therefore, populating that list is time-consuming. You can shorten that list of recent samples by changing the follow IIS, Application Settings: GlobalRecentSamplesMaxNumber GlobalRecentSamplesNumberOfDays RecentSamplesMaxNumber RecentSamplesNumberOfDays Workflow examples There are different levels of data entry user permissions to ensure that users follow a specific workflow that protects against missing or incorrect data. The workflow requires that data be complete and then approved. Following is an example work flow from data entry to data analysis with the Require approval of samples option. The workflow assumes that characteristics and labels were already created. 1. An administrator creates a Data Entry Setup in Statistica Enterprise Manager and selects the Require approval of samples approval option. This user is on a production server and tests the Data Entry Setup in production. Permissions on the Data Entry Setup prevent anyone from seeing this webform. NOTE: This workflow example does not require using a unique value in a sample label field, but one can be used. 2. A user with Data Entry (DE) permissions opens a web browser and logs on to name]dataentry. The user enters data. The data can be saved and the form can be completed after lunch. 3. Later, the user logs on to the website again to enter more data and select the Complete option. The data must be complete before it can be approved. Once a sample is complete, it cannot be edited by a user with Data Entry (DE) permissions unless it is marked as Requires Revisions. Only a user with Historical Edit (HEDIT) permission can edit a complete data record. 4. A user with Data Entry Approver (DEAPPRV) permissions opens a web browser and logs on to name]dataentry. The user reviews the data, and marks it as either Approved or Requires Revisions. The user who does this must be different from the user who entered the data, except when otherwise allowed in Statistica Enterprise Manager, System Options, Data Entry. 5. If the data requires revisions, the DE user will be notified via . They must review the data, correct any issues and mark it complete again before it is eligible for approval. The DEAPPRV is notified via about the status of the data. NOTE: notification can be sent to additional users whenever a sample is marked as Complete, Approved, and/or Requiring Revision. This is a configuration option of the Data Entry Setup. 6. The system records Data entry activities in an audit log. 7. An administrator in Statistica Enterprise Manager creates a Data Configuration off the Data Entry Setup to set up the data source for analysis. The administrator may also create an Ad hoc Analysis Configuration with filtering turned on. Dell Statistica Web Data Entry 12

13 NOTE: Data Configurations and Analysis Configurations are created off Data Entry Setups for analysis. They can be configured to only include completed data and/or approved data. 8. An analyst in Statistica creates a Workspace that uses the Data Configuration as a data source, adds nodes to merge in additional metadata or limits/specifications for a quality control chart, and adds a node to generate the quality control chart. 9. An analyst saves the Workspace into Enterprise Manager as an Analysis Configuration. 10. A business user in Statistica runs the Analysis Configuration to look at charts based on the current data. This user may also run the Ad hoc Analysis Configuration to perform other analyses on the data. Following is an example workflow for Blind Data Entry. This is only for data entry. The workflow assumes that characteristics and labels were already created. 1. The administrator creates a Data Entry Setup in Statistica Enterprise Manager and selects the Blind Data Entry approval option. A decision was made to use the Manual approval option because the company wants to collect an electronic signature for approval from a human. Selecting Automatic approval means the system electronically signs the approval. 2. The administrator reviews the Inputs properties page on the Data Entry Setup. 3. The administrator selects the sample label that will contain a unique value: LOT123. This is the Blind ID. 4. The administrator decides what other fields (characteristics and labels) will be compared by the system. Two people will enter data, but they don t have to enter exactly the same data. Maybe a comment field should be different between the two data entry employees. 5. The administrator decides if a specific field will be allowed to not match and the data record still be approved. This may be needed in a complex manufacturing environment. 6. The administrator reviews the notification options on the Data Entry Setup and adds the address for the data approver, who will receive an when the data is complete, requires revision, or approved. 7. The administrator grants permission to use the Data Entry Setup to data entry staff and data approvers. 8. A user with Data Entry (DE) permissions opens a web browser and logs into name]dataentry. The user enters the data. This is the primary data sample. 9. A second user with Data Entry (DE) permissions opens a web browser and logs on to name]dataentry. This user views the primary data sample and sees a Copy Sample button. The system displays an error and says this is not allowed. This user is allowed to see the sample because they have not started entering the matching data sample. After the user enters the matching sample, the user is prevented from viewing the primary sample. The user enters the matching data sample. 10. The system sees that the values in the Blind ID label match and starts comparing the other fields. 11. The system sends an to the data approver (DEAPPRV permission) that the data is complete or requires revision. 12. The system sends an that the data requires revision to both data entry users if the data records do not match. The system provides the user with visual feedback on which fields did not match, but they cannot see the other sample s values. Both users review and if necessary, correct data. After this review, the user will complete the data again. NOTE: If the two users are having difficulty in matching their data records, a third user with permission on the Data Entry Setup can log into name]/dataentry. They can review a report on the differences. 13. Both data records are complete. 14. The approver logs into name]/dataentry, reviews the difference report on the data, clicks the Approve button, and electronically signs approval. Dell Statistica Web Data Entry 13

14 Deprecated features Following is a list of features that are no longer supported starting with Statistica Desktop Data Entry: If you start Statistica to enter data, you are using this functionality. Also the Stations in Enterprise Manager will be deprecated. Automated Data Collection (ADC) Installation notes Statistica Web Data Entry comprises three parts: 1. Statistica Enterprise Manager and Statistica, applications 2. flexlm License Manager service 3. Web Data Entry, web service Typically, the applications and services are installed on the same server. Prior to installing the Statistica software, the following must be in place: 1. Client computers must have IE, Chrome, or Firefox installed. The compatibility view settings must be used with IE10, IE11 and IE The server computer must have IIS with ASP.NET configured for ISAPI and CGI. Also,.Net 3.5, and.net 4.5 must be enabled. 3. A new database will be created during installation, or an existing Enterprise database may be used. Typically Statistica Enterprise Server and Statistica Web Data Entry use the same database. a. Administrator login account/password for the database server must be available. NOTE: Access database is not supported for Statistica Web Data Entry. The server will run a flexlm license service after the software installation is completed. About Dell Dell listens to customers and delivers worldwide innovative technology, business solutions and services they trust and value. For more information, visit Contacting Dell For sales or other inquiries, visit or call Technical support resources Technical support is available to customers who have purchased Dell software with a valid maintenance contract and to customers who have trial versions. To access the Support Portal, go to Dell Statistica Web Data Entry 14

15 The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. In addition, the Support Portal provides direct access to product support engineers through an online Service Request system. The Support Portal enables you to: Create, update, and manage Service Requests (cases) View Knowledge Base articles Obtain product notifications Download software. For trial software, go to View how-to videos Engage in community discussions Chat with a support engineer Dell Statistica Web Data Entry 15

16 Copyright 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other marks and names mentioned herein may be trademarks of their respective companies. Legend CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed. WARNING: A WARNING icon indicates a potential for property damage, personal injury, or death. IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information. Dell Statistica Web Data Entry 16