Flylib.com
List of Figures
Previous page
Table of content
Next page
Chapter 1: Anatomy of the Microsoft Office System 2003
Figure 1.1: The .NET Framework consists of various layers .
Figure 1.2: Web Services are a stack of technology that enables the creation of a service.
Figure 1.3: Within Visual Studio.NET, select the type of project that you want to create.
Figure 1.4: Visual Studio.NET provides both a design palette and code window.
Figure 1.5: The code window within Visual Studio.NET 2003.
Figure 1.6: The compiled Web Service running in a browser.
Figure 1.7: The auto-generated WSDL for the Web Service.
Figure 1.8: The compiled Web Service running in a browser.
Figure 1.9: The returned XML message from the Web Service.
Figure 1.10: An overview of how InfoPath works.
Figure 1.11: The Create Page allows document and form libraries.
Figure 1.12: The VSTO project as it appears in Visual Studio.NET 2003.
Chapter 2: Understanding the InfoPath IDE
Figure 2.1: The InfoPath interface is divided into two sections.
Figure 2.2: The installed location of the template as seen in InfoPath.
Figure 2.3: A field that has failed data validation.
Figure 2.4: A drop-down indicator within a form.
Figure 2.5: The task pane title area.
Figure 2.6: The task pane navigation buttons .
Figure 2.7: The task pane showing fields and groups.
Figure 2.8: Viewing details for the current data source object.
Figure 2.9: Adding a new schema object to the data source.
Figure 2.10: Viewing the Employee Contact schema.
Figure 2.11: The layout task pane within InfoPath.
Figure 2.12: Validating that a field is bound correctly.
Figure 2.13: The Views task pane.
Figure 2.14: Defining a print view.
Figure 2.15: The Publishing Wizard for distributing InfoPath forms.
Chapter 3: Generating XML Forms
Figure 3.1: The Data Source Setup Wizard screen.
Figure 3.2: Defining a set of global defaults.
Figure 3.3: The data source of an InfoPath form using the constrained schema.
Figure 3.4: Fully qualifying the XML schema and target namespace.
Figure 3.5: Defining a default schema.
Figure 3.6: An XML schema with no qualification.
Figure 3.7: A schema showing as locked.
Figure 3.8: The structure of the timesheet.xsd.
Figure 3.9: Field properties showing an enumeration.
Figure 3.10: An imported schema showing a repeating section.
Figure 3.11: The company name default value.
Figure 3.12: View of a layout table.
Figure 3.13: Defining a custom table.
Figure 3.14: Setting the width of a field.
Figure 3.15: Changing the color scheme.
Figure 3.16: Adding the conditional formatting.
Figure 3.17: Defining the employee absence requirement.
Figure 3.18: Making a field read only.
Figure 3.19: Accessing the
OnAfterChange
event.
Chapter 4: Generating Web Service Forms
Figure 4.1: The IIS Management Console.
Figure 4.2: Enabling edit-while-running within IIS 6.
Figure 4.3: Using InfoPath to read the IIS metabase.
Figure 4.4: An executable file association as seen in IIS.
Figure 4.5: Architecture view of the Interview Feedback sample application.
Figure 4.6: The database structure of the Interview Feedback sample application.
Figure 4.7: The Documentation Handler displays a default page.
Figure 4.8: The default Windows Server 2003 UDDI screen.
Figure 4.9: The UDDI provider registration screen.
Figure 4.10: The UDDI service registration screen.
Figure 4.11: The UDDI binding screen.
Figure 4.12: The UDDI instance entry screen.
Figure 4.13: The UDDI tModel entry screen.
Figure 4.14: The WSDL for the Interview Feedback Web Service.
Figure 4.15: Defining the connection type for the Web Service.
Figure 4.16: Providing the Web Service parameters.
Figure 4.17: Defining the connection type for the Web Service.
Figure 4.18: Designing the Interview Feedback form.
Figure 4.19: Reviewing the default namespace assignment.
Figure 4.20: Defining the selection items for a drop-down control.
Figure 4.21: Selecting Receive Data for the Web Service.
Figure 4.22: Defining sample data for the data source.
Figure 4.23: Enabling a custom submit function.
Figure 4.24: Defining an HTTP request.
Chapter 5: Generating Database Forms
Figure 5.1: The SQL Server 2000 architecture.
Figure 5.2: The ODC viewed through a Web browser.
Figure 5.3: The tables available for query are shown.
Figure 5.4: Defining a read-only field.
Figure 5.5: Turning off the ability to add or delete table rows.
Figure 5.6: Assigning a secondary data source to a drop-down list box.
Figure 5.7: Running the sp_who system stored procedure.
Figure 5.8: Updating the SQL statement field in InfoPath.
Figure 5.9: Ignore this error message when using a stored procedure.
Figure 5.10: Database relationships stored in the Inventory.mdb file.
Figure 5.11: The listing of tables as seen in InfoPath.
Figure 5.12: Using InfoPath to add additional tables to the data source.
Figure 5.13: Selecting the related tables using InfoPath.
Figure 5.14: Reviewing the defined relationships within InfoPath.
Figure 5.15: Finalizing the Data Source Wizard.
Chapter 6: Building Workflow-Enabled Applications
Figure 6.1: A similar model exists between human- and computer-based workflow.
Figure 6.2: Select Documents and Lists to start creating a Form Library.
Figure 6.3: Select the Create option.
Figure 6.4: The WSS Create Page.
Figure 6.5: Page creation properties.
Figure 6.6: The new Form Library.
Figure 6.7: The Sales Contact form that we created based on an XSD.
Figure 6.8: Selecting fields for display in a WSS Form Library.
Figure 6.9: The InfoPath Publishing Wizard.
Figure 6.10: Selecting the Form Library to modify.
Figure 6.11: Selecting the available Form Libraries.
Figure 6.12: Selecting the properties to expose in the column list.
Figure 6.13: Completing the Publishing Wizard and notifying users.
Figure 6.14: The notification e-mail that invites users to use the Form Library.
Figure 6.15: Saving an InfoPath form to the library.
Figure 6.16: Reviewing the saved items.
Figure 6.17: Defining a WSS alert.
Figure 6.18: Using the
MailEnvelope
object to route a form.
Figure 6.19: Sending an approval request form using the
ShowMailItem
method.
Figure 6.20: Displaying the Sales Call form.
Figure 6.21: Displaying the Help Desk form.
Figure 6.22: Displaying the Help Desk Scorecard.
Chapter 7: Integrating with BizTalk Server 2004
Figure 7.1: The BizTalk Server 2004 architecture.
Figure 7.2: Managing the native adapters through the BizTalk Administration Console.
Figure 7.3: BizTalk Explorer, which is part of Visual Studio.NET 2003.
Figure 7.4: The BizTalk Business Rules Composer.
Figure 7.5: A defined rule set within the Business Rules Composer.
Figure 7.6: The XLANG components available within Visual Studio.NET 2003.
Figure 7.7: Available BizTalk project types within Visual Studio.NET.
Figure 7.8: Adding a new schema item.
Figure 7.9: The InfoPath inbound schema definition.
Figure 7.10: The mainframe-required schema definition.
Figure 7.11: The BizTalk Orchestration palette.
Figure 7.12: The transformation object for the
NewPatientOrchestration
.
Figure 7.13: Functoids and mapping within BizTalk.
Figure 7.14: Publishing the completed BizTalk orchestration.
Figure 7.15: Binding the InfoPath form to the Web Service.
Chapter 8: Building Smart Client Applications
Figure 8.1: XML that contains a dataset returned from the Catalog Web Service.
Figure 8.2: An InfoPath form that shows the catalog information.
Figure 8.3: When users cant connect to the Web Service, InfoPath displays this message.
Figure 8.4: Exported lists of files that make up an InfoPath solution.
Figure 8.5: A sample XML file entered using Visual Studio.NET.
Figure 8.6: View of the transformed customer data.
Figure 8.7: A developers view of the Tablet PC platform.
Figure 8.8: InfoPath form with the Ink Picture control.
Figure 8.9: A completed ink form.
Figure 8.10: Notepad view of the Base 64 encoded form.
Figure 8.11: Base 64 converted to a bitmap in a reusable client.
Chapter 9: Securing Solutions
Figure 9.1: An URL-based form that contains sandboxed permissions.
Figure 9.2: List of fully trusted forms available within InfoPath.
Figure 9.3: InfoPath enabled to use trusted forms.
Figure 9.4: Building the trusted form using Visual Studio.NET.
Figure 9.5: A completed trusted form that uses the
/MSI
solution.
Figure 9.6: Viewing the installation program in Visual Studio.NET.
Figure 9.7: Configuration file that determines .NET-available languages.
Figure 9.8: Basics of role-based security.
Figure 9.9: The XML returned showing the current user identity.
Figure 9.10: Selecting the Internet Options within InfoPath.
Figure 9.11: Accessing IE zones settings.
Chapter 10: Deployment Strategies
Figure 10.1: An InfoPath design pattern.
Figure 10.2: The files and directory structure of a deployed Web Service.
Figure 10.3: The error returned when youre trying to browse a web.config file.
Figure 10.4: The Setup and Deployment projects available within Visual Studio.NET.
Figure 10.5: The completed Web Service.
Figure 10.6: Adding a Web Setup Project.
Figure 10.7: Adding the compiled output to the installer.
Figure 10.8: Rebuilding the project.
Figure 10.9: The newly created MSI file.
Figure 10.10: The New Candidate Questionnaire.
Figure 10.11: Entering the shared folder location.
Figure 10.12: Defining an alternate network point.
Figure 10.13: E-mail notification that a form has been deployed.
Figure 10.14: XML files saved on a file share.
Figure 10.15: Starting the Virtual Directory Creation Wizard.
Figure 10.16: Defining the Virtual Directory alias.
Figure 10.17: Defining the content directory.
Figure 10.18: Defining the directory security.
Figure 10.19: Defining the InfoPath HTTP path for form publishing.
Figure 10.20: The local Internet cache, showing saved InfoPath forms.
Figure 10.21: Creating the Sharepoint Forms Library.
Figure 10.22: Entering the URL path for the new library.
Figure 10.23: Providing a description for the forms library.
Figure 10.24: Defining the promotion fields.
Figure 10.25: Defining view filters.
Figure 10.26: Defining the template upgrade options.
Previous page
Table of content
Next page
Programming Microsoft Infopath: A Developers Guide
ISBN: 1584504536
EAN: 2147483647
Year: 2006
Pages: 111
Authors:
Thom Robbins
BUY ON AMAZON
ERP and Data Warehousing in Organizations: Issues and Challenges
ERP Systems Impact on Organizations
The Second Wave ERP Market: An Australian Viewpoint
The Effects of an Enterprise Resource Planning System (ERP) Implementation on Job Characteristics – A Study using the Hackman and Oldham Job Characteristics Model
Distributed Data Warehouse for Geo-spatial Services
Healthcare Information: From Administrative to Practice Databases
Cisco IP Communications Express: CallManager Express with Cisco Unity Express
Understanding Cisco IPC Express Deployment Models
Summary
Digit Manipulation
Setting Up a Cisco UE Automated Attendant
Troubleshooting Cisco UE Startup
MySQL Cookbook
Specifying Which Columns to Display
Selecting Records from the Beginning or End of a Result Set
Writing Date-Processing Utilities
Creating a Navigation Index from Database Content
Using MySQL-Based Storage with the PHP Session Manager
An Introduction to Design Patterns in C++ with Qt 4
A Brief History of C++
Destructors
Widget Categories
Dynamic Form Models
PlayListModel Serialization
Persuasive Technology: Using Computers to Change What We Think and Do (Interactive Technologies)
The Functional Triad Computers in Persuasive Roles
Computers as Persuasive Tools
Computers as Persuasive Media Simulation
Computers as Persuasive Social Actors
Captology Looking Forward
Professional Struts Applications: Building Web Sites with Struts ObjectRelational Bridge, Lucene, and Velocity (Experts Voice)
The Challenges of Web Application Development
Creating a Struts-based MVC Application
Building a Data Access Tier with ObjectRelationalBridge
Templates and Velocity
Building the JavaEdge Application with Ant and Anthill
flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net
Privacy policy
This website uses cookies. Click
here
to find out more.
Accept cookies