Method and system for compiling and using placebot agents for automatically accessing, processing, and managing the data in a place

Abstract

Collaboration space object model provides for a place consisting of rooms created by users interacting with a client browser. A skin (i.e., theme) may be used as template for creating places. PlaceBots (i.e., agents) provide for accessing, processing and managing data in a place. HTML may be dragged and dropped into a place, where it is parsed and corresponding place fields created. MS Excel or Word documents may be dragged and dropped into a place, which creates a corresponding form, and users may create new documents using that form. A place type comprising a template of an entire place, or collaboration space, may be used to create new places. Changes made to a place may be reported, subject to security controls, by selecting what's new. Task fields are provided allowing web browser creation of forms for work flow. Place enabled objects are provided for synchronous communications. A quick browse feature provides a simplified format for browser windows based on selection of HTML links. MS Office documents may launched within a place for in place editing and importing the resulting document into the place.

Claims

We claim:

1. Method for managing objects in collaboration space, comprising the steps of:

creating placebot code by a user at a client browser including presenting to a user interface a form for describing said placebot code and selecting an agent trigger;

determining if said user has proper authorization, and if so uploading said placebot code to a collaboration space server by dragging said code into an upload control area of said user interface on said client browser;

at said collaboration space server, compiling said placebot code into a placebot agent.

2. The method of claim 1, further comprising the step of scheduling said placebot agent to run at specific times.

3. The method of claim 1, further comprising the steps of:

associated said placebot agent with a form; and

upon opening said form, executing said placebot agent.

4. The method of claim 1, further comprising the steps of:

implementing said collaboration space according to an object model comprising collaboration space objects selectively including place, room, folder, page, member, form, field, placetype, roomtype, skin, and placebot objects;

executing said placebot object to create or manipulate said collaboration space objects.

5. The method of claim 1, further comprising the steps of executing one or more said placebot agents selectively for:

sharing documents;

holding discussions with team members;

performing actions triggered as result of submission of a form object; and

performing actions scheduled to run a specified time.

6. The method of claim 1, further comprising the steps of:

executing said placebot object according to schedule or upon request;

when executing said placebot object according to schedule, controlling access to said placebot object and objects referenced by said placebot object by inheritance of access control from said collaboration space server; and

when executing said placebot object upon request of a user, controlling access to said placebot object and objects referenced by said placebot object according to

the access rights of said user.

7. Method for providing placebot code to a collaboration space, comprising the steps of:

operating a browser to create said placebot code;

presenting to a user interface a form for describing said placebot code and selecting an agent trigger;

dragging said placebot code into an upload control area of said user interface on said browser;

determining if said user has proper authorization, and if so uploading said placebot code and said agent trigger to a collaboration space server; and

operating said server to compile said placebot code into a placebot agent.

8. The method of claim 7, further comprising the step of implementing said collaboration space according to an object model selectively including place, room, folder, page, member, form, field, placetype, roomtype, skin, and placebot objects.

9. The method of claim 8, further comprising the step of:

maintaining for each said room, a list of all published objects in a place, including said room, page, placebot, field, skin and form objects; and

executing a view on said list to reference said published objects.

10. The method of claim 9, further comprising the step of:

using a placebot object associated with a form object to initiate processes outside of a page object.

11. The method of claim 8, said placebot code being uploaded to said server by dragging and dropping said placebot code into a form.

12. The method of claim 7, further comprising the steps of:

creating said placebot code in a legacy form; and

including in said legacy form a text field with indicia recognizable by said server as identifying said placebot code as a document to be rendered in said browser as a collaboration space form.

13. The method of claim 12, further comprising the steps of:

creating said placebot code as hypertext markup language code;

executing said hypertext markup language code selectively to define forms, execute backend logic, and define look and feel of said user interface to said collaboration space.

14. The method of claim 13, further comprising the steps of:

defining collaboration space members authorized to edit documents when creating a placebot object; and

responsive to execution of said placebot object, modifying access control to documents.

15. The method of claim 12, further comprising the steps of:

to import an image into said place, referencing said image within a placebot object for creating new pages.

16. The method of claim 7, further comprising the steps of:

executing procedures within said placebot agent to access collaboration space objects including said collaboration space server and room objects in said collaboration space.

17. The method of claim 16, said placebot agent accessing said server according to the steps of:

executing a get database server command; and

receiving a database having a path designation;

determining that said path designation starts with indicia identifying said collaboration space server.

18. The method of claim 17, said placebot agent accessing a room object within said collaboration space according to the step of:

searching in a main collaboration space server directory for said room object in a path designation starting with said indicia identifying said collaboration space server.

19. A system for managing collaboration space objects, comprising:

a text editor for creating custom logic;

a user interface including an upload control area for receiving said custom logic and a trigger selector for specifying that said custom logic is to be executed by a server responsive to submission of a form or at scheduled times;

at least one placebot serving as a primary repository for said custom logic and selectively assuming access rights of a user submitting said form;

said placebot providing links between and manipulating said objects in accordance with said access rights; and

responsive to said trigger selector, said placebot selectively executing said custom logic responsive to one of opening of the form with the access rights of said user submitting said form and at scheduled times with access rights being established by said server.

20. The system of claim 19, said collaboration space comprising an object model selectively including place, room, folder, page, member, form, field, placetype, roomtype, skin, and placebot objects.

21. The system of claim 20, further comprising:

a storage device for storing said placebot;

a code transfer facility responsive to request by a place manager irrespective of administrative access to a collaboration space server for installing said placebot to said collaboration space server.

22. A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps for managing objects in collaboration space, said method steps comprising:

creating placebot code by user at a client brower including presenting to a user interface a form for describing said placebot code and selecting an agent trigger;

determining if said user has proper authorization, and if so uploading said placebot code to a collaboration space server by dragging said code into an upload control area of said user interface on said client brower; at said collaboration space server, compiling said placebot code into a placebot agent.

23. A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps for providing placebot code to a collaboration space, said method steps comprising:

operating a browser to create said placebot code;

presenting to a user interface a form for describing said placebot code and selecting an agent trigger;

dragging said placebot code into an upload control area of said user interface on said browser;

determining if said user has proper authorization and if so uploading said placebot code and said agent trigger to a collaboration space server; and

operating said server to compile said placebot code into a placebot agent.

Description

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

This invention relates to web technology. More particularly, it relates to the creation and use of collaboration sites on the Internet or on an Intranet client/server system and to the graphical user interface used in Internet communications.

2. Background Art

The Internet and the World Wide Web (WWW) provide intra-enterprise connectivity, inter-enterprise connectivity and application hosting on a larger scale than ever before. By exploiting the broadly available and deployed standards of the Internet and the WWW, system users and designers can leverage a single architecture to build client/server applications for internal use that can reach outside to customers, business partners and suppliers.

Collaboration requires simultaneous communication between individuals on a project team. Typically, this has required that the team members work in the same location. Phone and video conferencing has enabled some remote work on the part of team members. Also, because of the growth of the Internet, collaboration using web technologies has been attempted, primarily using electronic mail (E-mail), Internet chat rooms, electronic whiteboards, and conferencing software. The most useful has been E-mail, but this approach results in a large trail or thread of notes as collaboration on a project advances, and these notes have no home or place to reside which is accessible by all team members substantially instantaneously and simultaneously. People often enter such a thread at different points, and such threads are not efficient in coordinating the work of many different people on a team which may include in-house developers and others, such as remote contractors, outside of an enterprise's firewall.

In order for such disperse teams to have the same, or substantially the same, collaboration environment as individuals working in the same physical office, a system is required which facilitates instant messaging, voice conferencing, electronic white boarding, and text and non-text file exchange. Such a system needs to provide a collaborative electronic room, or space, which is easily configured for use by team members without substantial administrative or application development support, and preferably include both groupware and project oriented applications such as shared folders, file exchange, workflow, group calendars, threaded conversations, version control, file locking, file merging, and security.

There is a need in the art for such a system which is easy to set up and which enables diverse and remote teams to become immediately productive in a secure environment. It would be, further, most desirable to allow such a collaborative environment to be set up without administrative support, that is by members of the team itself, using a familiar and easy to use browser user interface. Members of the team, acting with manager or author authority, and using such a browser interface without involving administrative or application development support, need to be able to set up a folder or room for each project element, such as a source code component, with version control, workflow elements, and group calendaring for tracking the project or project element with respect to approvals and deadlines. Such a room needs to receive from team members reports and have them routed to appropriate team members for review, resolution, and approval.

The WWW is a collection of servers on an IP (Internet Protocol) network, such as the Internet, an Intranet or an Extranet, that utilize the Hypertext Transfer Protocol (HTTP). Hereinafter, "Internet" 100 will be used to refer to any IP network.

HTTP is a known application protocol that provides users with access to files, which can be in different formats, such as text, graphics, images, sound, and video, using a standard page description language known as Hypertext Markup Language (HTML). Among a number of basic document formatting functions, HTML allows software developers to specify graphical pointers on displayed web pages, commonly referred to as "hyperlinks," that point to other web pages resident on remote servers. Hyperlinks commonly are displayed as highlighted text or other graphical image on the web page. Selection of a hyperlink with a pointing device, such as a computer mouse, causes the local computer to download the HTML associated with the web page from a remote server. The browser then renders the HTML into the displayed web page.

Web pages accessed over the Internet, whether by a hyperlink, opening directly via an "open" button in the browser, or some other means, are commonly downloaded into the volatile cache of a local computer system. In a computer system, for example, the volatile cache is a high-speed buffer that temporarily stores web pages from accessed remote web sites. The volatile cache thus enables a user to quickly review web pages that were already downloaded, thereby eliminating the need to repeat the relatively slow process of traversing the Internet to access previously viewed web pages. This is called local caching.

It is an object of the invention to provide a collaboration space application model for creating web applications that are aesthetically pleasing and present the user with a simple interface.

It is a further object of the invention to provide for creating web applications that are instantly created, instantly archived, team and project oriented, easy to use, created, accessed and administered via the Web, reusable, and extensible.

It is a further object of the invention to provide a method and system for building collaboration applications, by providing a repository for custom logic.

It is a further object of the invention to provide a method and system whereby an agent may be coded in any legacy editor and the resulting file uploaded into collaboration space to compiled into a placebot for automating tasks with respect to collaboration space objects.

SUMMARY OF THE INVENTION

In accordance with the invention, a method and system is provided for managing objects in collaboration space by receiving placebot code at a client browser; uploading the placebot code to a collaboration space server; and at the collaboration space server, compiling the placebot code into a placebot agent.

In accordance with an aspect of the invention, there is provided a computer program product or computer program element for managing objects in collaboration space by receiving placebot code at a client browser; uploading the placebot code to a collaboration space server; and at the collaboration space server, compiling the placebot code into a placebot agent.

Other features and advantages of this invention will become apparent from the following detailed description of the presently preferred embodiment of the invention, taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic representation of a typical server/client system implementing the collaboration space of the preferred embodiments of the invention.

FIG. 2 is a schematic representation of various server and client components implementing the collaboration space of the preferred embodiments of the invention.

FIG. 3 is a schematic map illustrating Domino objects relating to the object model of the collaboration space of the preferred embodiments of the invention.

FIG. 4 is a schematic map of the object model implementing the collaboration space of the preferred embodiments of the invention.

FIG. 5 illustrates the components of a collaboration space user interface.

FIG. 6 is a flow chart representation of generation of collaboration space data objects.

FIG. 7 illustrates a typical collaboration space user interface.

FIG. 8 is a schematic representation of a directory structure, along with the files in an exemplary collaboration space server.

FIG. 9 is a flow chart representing the method steps for creating a PlaceBot.

FIG. 10 is a schematic representation of a screen capture illustrating creation of a new page in accordance with a preferred embodiment of the invention.

FIG. 11 is a schematic representation of a screen capture illustrating the user interface for creating a new page in collaboration space.

FIG. 12 is a schematic representation of a screen capture illustrating the user interface for in Place editing of Microsoft documents.

FIG. 13 is a flow chart illustrating in-place editing in accordance with the preferred embodiment of the invention.

FIG. 14 is a schematic representation of a screen capture illustrating the user interface for in Place editing of Microsoft documents.

FIG. 15 is a schematic representation of a screen capture illustrating the user interface for attaching forms.

FIG. 16 is a system diagram illustrating importing interest content into collaboration space.

FIGS. 17-20 are schematic representations illustrating the user interface for editing a collaboration space file attachment and saving the changes back to collaboration space.

FIG. 21 is a flow chart illustrating the creation and importation into collaboration space of a form.

FIG. 22 is a schematic representation of a task page presented in list mode.

FIG. 23 is a schematic representation of a task page presented in time line mode.

FIG. 24 is a schematic representation of a read scene state display for tasks.

FIG. 25 is a schematic representation of a user interface for integrating a form into workflow.

FIG. 26 is a schematic representation of a user interface for adding events to a calendar page and for publishing it in a specific folder in collaboration space.

FIG. 27 is a schematic representation of a user interface including upload control.

BEST MODE FOR CARRYING OUT THE INVENTION

Architecture Overview

Referring to FIG. 1, a broad overview of a system implementing the collaboration space technology of an exemplary embodiment of the system of the invention is presented.

Server 100 includes a Domino server 104, HTTP server 106, QuickPlace extensions 108, and open storage 130. Client 102 includes a QuickPlace user interface 110 and browser 112.

QuickPlace open storage 130 includes all the databases and templates that implement the collaboration space. Domino 132 and active directory 134 define the collaboration process. The user interfaces with the system through browser 112. NSF agents 114, 116, Java 118 and LotusScript 120 represent components and templates downloaded from server 100 in support of collaboration space at client 102. All the extensions 108 are keyed off the URL, as will be further explained hereafter.

Notes API 136, Notes designer 138 and client 140, external applications 142, including Java agents 144 and LotusScript 146, are located off of open storage 130. Open storage 130 is storage where a document can be communicated, such that external applications 142 may manipulate it. QuickPlaces, pages, folders, can be created and changed, and data 148 can be imported and exported, using agents in Java 144 or LotusScript 146.

QuickPlace is primarily concerned with representing the collaboration space. Consequently, designers and consultants are able to integrate into that space custom features and data from other applications. HTML forms 122, written using an HTML editor 124, skins 248 (HTML 244 and QP tags), external files written using Java 118, and MS office documents 250 from MS office 228, may be imported to server 100 by dragging and dropping 111 from local storage 502 into an upload control panel 240 in browser 112.

An alternate client 126 and encapsulated place types 128 may be provided from which other spaces 129 can be created that take advantage of the QuickPlace storage model, providing functionality which can be manipulated using browser 112, including the integration of external technology providing opportunity for deep customization.

Server/Client Components

Referring to FIG. 2, in accordance with an exemplary embodiment of the invention, several components comprise QuickPlace server 100 and client 102.

QuickPlace is built on top of the Domino server 104. In the case of a stand alone installation, a subset of the Domino server is installed. Server 100 also includes HTTP server 106, or the optional MS IIS server 150. QuickPlace extension 108 is where we built most of the collaboration space implementing code exists the server 100. Server 100 also includes a spell checker 152 and a text to GIF converter (Limerick).

Client 102 includes rich text edit control 162, and applet 164 with which to apply various attributes and is a key component of the QuickPlace experience. Upload control 166 is used to attach and upload files, such as bringing in an agent and uploading it to a place. This is also used to bring in an imported HTML form or a different skin. Upload control is implemented to allow ease of use via drag and drop. Java script 118 includes code downloaded to the client to complete the generation of HTML pages.

Collaboration Space Object Model

Referring to FIG. 3, the collaboration space of the preferred embodiment of the invention, referred to as QuickPlace, is implemented with an object model which comprises very few objects, very few concepts in order to make it easy to build and manage. And the fewer concepts, the better.

Referring to FIG. 3, the object model is independent of its implementation. There exists a place 172 that has rooms 174, and there are pages 182 in those rooms. And then there are members 190 of the place. Those four objects 172, 174, 182 and 190 are the primary objects.

Folders 176 add more complexity to the model, but bring a lot of benefit as well. Pages 182 are organized within folders. Two further objects are primarily visible to the designer of the place. And these are forms 178 and fields 180.

Place type 196 is a more advanced object, and is an object from which a place 172 is created. Place type 196 represents the foundation for building true collaborative applications. Everything created in building collaboration space is done in a place 172. Once such a place is created, it can be made a template 266 (FIG. 6) and copied as a place type 196. Once it becomes a place type 196, it is available for use by others for building additional places 172 that include the format, look and feel, and other characteristics of the original place.

This is illustrated in FIG. 11, where a first place 360 is converted by QP extensions 108 into a place type, or template 364 from which additional places 366 may be created.

Room type 198 is an object provided for creating rooms 174 which are of a given type.

The last two objects illustrated in FIG. 3 are skins 200 and PlaceBots 184. Skins 200 control everything about the user interface, including layout and style. Layout defines the positioning of components on the screen. Style defines the form and colors of those components. A PlaceBot 184 is an enhanced agent, enhanced in the sense that it enables the use of Java or Lotus Notes or equivalent text editors. Once written using such an editor, and uploaded to a place 172, the server compiles the PlaceBot into an agent, reporting any errors. The agent resulting from a compiled PlaceBot can be scheduled to run at certain times, or upon opening a form. That is, the PlaceBot may be associated with a form, such as a sales order which, when opened, will cause the agent to execute. Thus, PlaceBots 184 are an essential part of building collaboration applications, for they are the primary repository for custom logic.

Referring further to FIG. 3, a preferred implementation of the object model heretofore described uses Lotus Notes/Domino concepts and objects. Thus, Notes/Domino file system directory 202 represents place 172; database 204 represents room 174; folder view 206 represents folder 176; pages 182, members 190, forms 178, fields 180 and skins 200 are represented by notes 208, 210, 212, 214, 220, respectively.

Place 172 is represented as a file system directory. So whenever a place called Acme is created, a file system directory 202 called Acme will be instantiated. Within that directory 202, there are a number of objects. Each room 174 is a Notes database 204. Folders 176 are implemented as Notes folders or views 206 depending on what's more convenient for the particular folder.

Pages 182 are a combination of data notes, forms and sub-forms 208. A member 190 is a data note 190 in a context room 174. Forms 178 and fields 180 are data notes. Place type 196 is a directory* 216 that contains all the rooms 174 that make up that place type. A room type 198 is a template 218. Skins 200 are a note 220 and PlaceBot 184 is an agent 222.

Notes/Domino Implementation of the Object Model

Developers familiar with the Domino Object Model (Domino OM) will be able to leverage their existing skills when developing on the QuickPlace platform. "PlaceBots" for example are implemented as Domino Agents, and it is possible to create and test them on Domino Databases. Within the QuickPlace object model (OM), however, there are some divergences from the Domino OM. For example, QuickPlace forms 178 are not the same as Domino Forms. QuickPlace forms more closely resemble Domino Documents, because they are created using a Domino form, and contain a Domino text field with a value of "h_Form". The value of "h_form" tells QuickPlace that this Domino document should be rendered in a browser as a QuickPlace form 178.

This structure provides flexibility for Web applications with less complexity than if Domino Forms were used. For example, in a default QuickPlace, a user can create a new QuickPlace form 178. The user chooses which fields to include in form 178, in what order they should appear and what text and or graphics should appear near them. To create this sort of instant structure on the Web using Domino Forms would be very complex indeed. QuickPlace has extended this concept of being able to use HTML to define forms 178 by enabling the creation of custom QuickPlace forms using imported HTML 122. These Forms not only make use of Web authoring technologies such as JavaScript, but also have the back end support of Domino. This back end logic is implemented via tools such as PlaceBots (Domino Agents) 184. This means that forms 178 have the ability to not only to define the look and feel of visible parts of an application, they also have the potential to initiate workflow and many other powerful automated features.

QuickPlace forms 178 have been optimized by stripping away many of the Notes features not required when used on the Web. A another advantage of this structure is that it enables the use of Web authoring tools to extend the objects. For example, with respect to QuickPlace forms, it is possible to modify forms using XML, JavaScript and HTML and any other Web tools. Knowledge of JavaScript and HTML are more common than Domino Designer skills, thus making the QuickPlace a very open platform. Some parts of the QuickPlace OM implement Domino/Notes functionality in different ways to a standard Domino application. For example, QuickPlace uses Domino's security and authentication model as a basis for its management of access to QuickPlaces. However, instead of primarily utilizing the Domino Directory, QuickPlace also uses a Contactsl.nsf database for each QuickPlace.

Containment and Association of Objects

Referring to FIG. 4, this object model is further described. FIG. 4 illustrates selected QuickPlace objects, the directory structure and how Objects relate to each other within the hierarchy. This model provides a visual representation of the containment and association between objects.

QuickPlace Server

The highest level of the model is the QuickPlace Server 170. Within server 170 are all of the QuickPlaces 172 as well as the resources they access to finally render Web applications.

This FIG. 4 displays the Model focusing on QuickPlaces. The following explanation, written from a programmers perspective, describes each of the objects of the model and they can be accessed in an application.

QuickPlace uses notes for many of its objects 182, 190, 178, 180 and 200, so that objects in the Place can be organized more easily. Table 1 sets forth the QP objects and their Notes/Domino equivalents. As an example of how design Notes are implemented consider the Table Of Contents (TOC). The Table Of Contents is a list of pages, folders and tools such as the Customize Area. Domino Folders may be listed using a link document, or Note.

                             TABLE 1
             QUICKPLACE OBJECTS AND DOMINO EQUIVALENT
          QuickPlace Object      Domino Equivalent
          QuickPlace Server      File Directory
          Place                  File Directory
          Page                   Data Note, Form & Subform
          PlaceBot               Domino Agent
          Theme                  Data Note
          Member                 Data Note in Contacts1.nsf
          Subroom *              NSF Database
          SubroomTheme           Data Note
          SubroomMember          Data Note in Contacts1.nsf
          Room                   NSF Database
          Folder / TOC           Folder or View
          Form                   Data Note
          Field                  Data Note
    * Subrooms contain their own set of Folder, Page, Form, Field, PlaceBot &
     Subroom Objects

                             TABLE 2
               SCRIPT PROCEDURE FOR FINDING A PLACE
          Dim ndbPlace As NotesDatabase
          Set dirPlace = New NotesDbDirectory( g_sServerName )
          Set ndbPlace = dirPlace.GetFirstDatabase( DATABASE )
          sNdbPlaceFilepath = ndbPlace.FilePath
          If Instr(1, Lcase( sNdbPlaceFilepath ),
          .vertline.quickplace.backslash.millennia.vertline. ) Then
          `//the Place is found

                             TABLE 3
              SCRIPT PROCEDURE TO FIND A ROOM OBJECT
          Set dirPlace = New NotesDbDirectory( g_sServerName )
          Set ndbPlace = dirPlace.GetFirstDatabase( DATABASE )
          sNdbPlaceFilepath = ndbPlace.FilePath
          If Instr(1, Lcase( sNdbPlaceFilepath ),
          .vertline.quickplace.backslash.millennia.backslash.main.nsf.vertline.
     ) Then
          `//the Room id found.

                             TABLE 4
                      FIELDS DEFINING ROOMS
        Field Name         Description
        h_HaikuName        The name of this Place
        h_AreaType         The name of the template used to create
                           this room.
        h_AreaParent       The name of the parent database
        h_ShowSecurity     If h_SetSecurity = 1, the QuickPlace
                           server sets h_ShowSecurity to 1.
        h_SetCalendar      Determines if the Calendar will be
                           visible in a Room. If the field has the
                           value of "1" a link to the Calendar will
                           be displayed in the sidebar
        h_SetSecurity      This field works in conjunction with the
                           h_ShowSecurity field. It is only valid
                           for Readers and Authors, because
                           Managers must always be able to edit
                           security of a Room. If the field is set
                           to "1" a link to the Security page will
                           be displayed in the sidebar for Readers
                           and Authors (if they select Security in
                           this case they will see only their own
                           information)
        h_MailDb           The name of the database that receives
                           email addressed to this Place.

                             TABLE 5
                 VIEWS USED TO REFERENCE OBJECTS
        View Name     Description
        h_Index       Provides a list of all published Pages
                      in a Room, listed by h_UNID, the unique
                      identifier for a Page. Lists all
                      published items in a Room, this not only
                      includes Pages but all of the Objects in
                      a Place. For example, Pages, PlaceBots,
                      Fields, Skins and Forms.
        h_QDK         Every Design Note in a Place. The h_QDK
                      view contains a form formula to open
                      different documents using different
                      forms. For example: If the field
                      "h_Type" is "0" then use the form named
                      "h_Page". The result of this form
                      formula is that the QDK view allows
                      developers to inspect the properties of
                      some Design Notes. The supported types
                      are: "h_Page", "h_Folder", "h_Room",
                      "h_SubRoom", "h_Error" and "h_RoomType".
        h_TOC         List of all items displayed in the Table
                      Of Contents. Items must have the
                      "h_IsInTOC" field with a value of "1"
                      and be published with no
                      replication-save conflict.
        (All)         Every item in the Room. Sorted by the
                      h_Name field: the readable name of the
                      item. For example "Welcome",
                      representing the default Welcome page.

                             TABLE 6
                  FIELDS USED TO DEFINE FOLDERS
        Field Name        Description
        h_FolderStyle     When creating a new folder, one is given
                          the choice to create a new folder based
                          on a number of templates. This field
                          denotes which type of folder has been
                          created.
                          "1" = Standard List
                          "3" = Headline
                          "4" = Slide Show
                          "5" = Response List
                          "7" = Ordered List
        h_FolderStorage   The "internal" name of the folder, in
                          other words, the name by which it is
                          known to the system. The value of this
                          field is used in documents to tell
                          QuickPlace in which folder it should be
                          used.
        h_CanAddPages     When creating a new folder, the manger
                          is presented with the options, to the
                          question "Who can add pages to this
                          folder?". If only managers is chosen
                          the value of "0" is written to this
                          field. The default is " " which means all
                          authors can add pages to this folder.

                             TABLE 7
                   FIELDS USED TO DEFINE FORMS
        Field Name           Description
        h_FormDescription    The content of this field appears
                             as the description of the form
                             appearing in the "New" page.
        h_WorkflowType       Allows 1-4 approvers and some other
        h_ApprovalCycle      options. This is normally set to
                             "h_Standard".
        h_EditorInChief      Allows 1 approver and fewer
                             options.
        h_MultipleEditors    By setting this field, all members
                             of QP to edit pages created with
                             this form.
        h_Standard           None of the above.
        h_SetPageComponent   sView Should = h_FieldDefinitions

                             TABLE 8
                   FIELDS USED TO DEFINE FIELDS
    Field Name               Description
    h_IsUser                 Defined h_True means this is a custom
                             form
    h_PublishlnFolder        UNID of the folder +".vertline." +
    h_FolderStorage          name of the folder
    h_Name                   "Import" and is related to the
                             h_SystemName field which often has a
                             similar value such as "h_Import".
    h_FieldLabel             Instructional information that might be
                             useful for someone editing this field.
                             Similar to the Static h_FieldType.
                             Containing information to help the user,
                             but only displayed in edit mode." For
                             example: <script>
                             (h_CurrentSkinType ==
                             `h_Edit`)?"": C(self, `Note: Clicking
                             on the title of this page in its folder
                             or in the sidebar will open the page
                             that it points to. To edit the page
                             again later, click its title in the
                             Index.`) ;</script>"
    h_ContainerUNlD          The UNID of the Form which contains
                             this field. QuickPlace uses a Design Note
                             to create forms, each of these having an
                             internal name. The h_ContainerUNID
                             contains the internal name of one of
                             these QuickPlace Forms.
    h_FieldType              There are many different types of
                             Fields. The following types are listed
                             as examples to help understand how
                             Fields work in general.
    "h_Attachments"=         Enables the attaching of files.
    "h_CalendarControl"=     Includes date and time controls and
                             a duration field
    "h_DateControl"=         Date field with date picker widget
    "h_DateTime"=            Contains Date and Time information.
    "h_DocAuthor"=           Contains a Domino Heirachical name of
                             the original Author of the Document.
    "h_DocCreated"=          Creation date of the page.
    "h_DocModified"=         Modified date of the page.
    "h_DocSize"=             Size of the page.
    "h_NamePopup"=           Select listing members of the QuickPlace
    "h_RichText"=            Rich text field. Allowing editing via
                             the rich text editor applet.
    "h_Serial"=              A unique number to identify the
                             document.
    "h_Static"=              Static text, used to provide information
                             about the accompanying field. May also
                             include link to an image.
    "h_Subject"=             The Documents subject.
    "h_TaskControl"=         Used in the Task form to insert the task
                             control tool.
    "h_TextInput"=           Simple text equating to the "<input>"
                             field in HTML.
    "h_TextPopup"=           Text select list, equating to the
                             "<select><option>" in HTML.
    "h_TimeControl"=         Select lists for hours, minutes, AM/PM.
    "h_CalendarControl"=     Field containing control tool used
                             in the calendar field.
    "h_CreateMSExcel"=       Field enabling the upload of Excel
                             documents.
    "h_CreateMSPowerPoint"=  Field enabling the upload of
                             PowerPoint documents.
    "h_CreateMSWord"=        Field enabling the upload of Word
                             documents.
    "h_Import"=              Field enabling the upload of imported
                             documents such as HTML.
    "h_MultipleImport"=      Field enabling the upload of multiple
                             documents, such as a series of HTML
                             documents.
    "h_NotifyIndicator"=     Field indicating if members should
                             be notified of the creation of
                             content or their inclusion in the
                             Contacts1.nsf.

                             TABLE 9
                   FIELDS DEFINING PAGE OBJECTS
        h_NotInSearch      Having the value of "1" will exclude the
                           field from being included in a full text
                           search. This allows functional content
                           in fields such as JavaScript or static
                           text to evade returning a hit during
                           searching.
        h_Position         Indicates the fields position of
                           appearance in a form. Typically numbers
                           such as 100 are used.
        h_FieldFormat      "h_FieldFormat" indicates formatting
                           options, "h_All" "h_BannerOptional"
                           "h_BannerRequired"
        h_BannerRequired   Always display subject as a banner at
                           top of page
        h_BannerOptional   Allow user to choose banner or not
        h_NoBanner         Do not display the subject on the page
        h_FieldIsRequired  1 = The field is required and the user
                           will be prompted if they do not fill it
                           out.

                             TABLE 10
              FIELDS USED TO DEFINE QUICKPLACE PAGES
    Field Name         Description
    h_Form             The QuickPlace form used to create this
                       page. This is not the Domino "Form"
                       field which denotes which form Domino
                       links the file to. The Domino "Form"
                       field will contain "h_PageUI" for
                       virtually all objects in a QuickPlace.
    h_PageType         This field is set to null when the
                       document is a visible document. Only
                       when the object is in design mode do the
                       other values appear:
                       "h_Response" the document is a response
                       to a topic document. This value is only
                       valid in response folders.
                       "h_Revision" this means that the
                       document is being revised, and is not
                       available for public access.
                       "h_Mail" means that the document is a
                       mail document, being either sent or
                       received by QuickPlace.
    h_Originator       The creator of this page. This field
                       contains a full hierarchical name, for
                       example: "CN=David Wyss/OU=
                       QuickPlaceName/OU= QP/O= ServerName".
                       All users have the second OU part of the
                       name set to QP. This is done so that
                       when QuickPlace is used on an Overlay
                       server (QuickPlace and Domino together)
                       QuickPlace can avoid conflicts between
                       Domino registered users and QuickPlace
                       users.
    h_NameIsBanner     Denotes if the page's name should be
                       displayed as a banner. If it is to be
                       displayed as a banner, this field
                       contains the value "1". Setting this
                       field is done when the user clicks on
                       the "Show the title, author and date on
                       page?" checkbox.

          <script language=JavaScript>
          if ( typeof( PageBody ) == "undefined" ) {
          var sPageBodyMessage = `Run the Mapperizer PlaceBot
                               to see a site map here...`;
          document.write( sPageBodyMessage )
          } else{
          document.write( PageBody )
          }
          </script>

                             TABLE 11
           COMMONLY USED JAVASCRIPT VARIABLES IN PAGES
    Field Name             Data Type, Description
    h_Name                 String, readable name of the Page
    PageBody               String, content of the page.
    h_SystemName           String, the internal name of a page. For
                           example, `h_Welcome`
    h_Originator           String, full Notes format name of the
                           document creator For example: `CN=Anna
                           Rath/OU=Millennia/OU=QP/O=Server`;
    h_IsPublished          String, number representing "1" for
                           published or "0" for not published.
    h_LastTimePutAway      String, representing the date and time
                           the Page was last saved `09/03/2000
                           07:54:08 PM`
    Form                   String, Domino Form name used to create
                           the Page. Most documents in a
                           QuickPlace are created with the
                           `h_PageUI` Form. The value that
                           differentiates fields is the h_Type
                           field.
    HTTP_COOKIE            String, all cookies available to that
                           Page.
    HTTP_HOST              String, name of the server. For example
                           `millennia.com`
    HTTP_REFERER           Page used to send the user to this page.
    HTTP_USER_AGENT        String, browser used to access the
                           current Page. For example: `Mozilla/4.0
                           (compatible; MSIE 5.0; Windows NT;
                           DigExt) `
    REMOTE_USER            String, full name of the person reading
                           the Page, for example: `CN=Doug
                           Mudge/OU=Millennia/OU=QP/O=Server`;
    Server_Name            String, the server name, for example:
                           `dwyss.lotus.com`
    h_DocSize              Integer, size of the page, for example:
                           4705
    h_ModifiedDate         String, date and time the page was last
                           saved, for example: `09/03/2000 07:54:05
                           PM`;

        function fnGetSimpleName(sTxt) {
        iTxtStart = sTxt.indexOf(`=`) ;
        iTxtStart++;
        iTxtEnd = sTxt.indexOf(`/`) ;
        if(iTxtEnd == -1) iTxtEnd = sTxt.length;
        sTxt = sTxt.substr(iTxtStart,iTxtEnd - iTxtStart) ;
        return sTxt;
        } ;
        return fnGetSimpleName (`CN=Doug Mudge/OU= Millennia/OU=
        QP/O=Server`)

                             TABLE 12
                  FIELDS USED TO DEFINE MEMBERS
        Field Name        Description
        h_Password        This member's password. Encrypted with
                          @Password
        h_FirstName       This member's first name
        h_LastName        This member's last name
        h_PhoneNumber     This member's phone number
        h_EmailAddress    This member's email address

                             TABLE 13
                   FIELDS USED TO DEFINE GROUPS
          Field Name      Description
          h_Members       The list of members who belong to this
                          group, listed in full heirachical
                          format.

                             TABLE 15
                 FIELDS USED TO DEFINE PUBLISHING
        Field Name               Description
        h_IsPublished            1 = This object is currently
                                 published
        h_IsHidden               1 = This object is not shown to the
                                 user
        h_SetReadScene           The name ot the default scene
                                 (subform) to use when viewing this
                                 object
        h_SetEditScene           The name of the default scene
                                 (subform) to use when editing this
                                 object
        h_PublishedVersionUNID   If this object is being edited and
                                 the current object is the draft
                                 version, the UNID of the published
                                 version of this object.
        h_DraftVersionUNID       If this object is being edited and
                                 the current object is the published
                                 version, the UNID of the draft
                                 version of this object.
        h_LastTimePutAway        The last time that this object was
                                 changed: Published or Saved under
                                 construction.


                         TABLE 16
              FIELDS USED TO DEFINE FOLDERS LOCATION
          Field Name           Description
          h_FolderUNID         The name or UNID of the Notes
                               Folder where this page resides.
          h_IsInToc            1 = This object is shown in the
                               Table of Contents (sidebar).
          h_CurrentPosition    The position of this object with
                               respect to other objects in the
                               collection.
          h_SetParentUNID      If this is a child or response
                               object, the UNID of the parent
                               object.


                         TABLE 17
                  FIELDS USED TO DEFINE SECURITY
          Field Name         Description
          h_Readers          If this object is protected from
                             readership, the list of names,
                             groups, and or roles that can read
                             this object.
          h_Authors          If this object is protected from
                             authorship, the list of names,
                             groups, and or roles that can
                             author this object.


                         TABLE 18
                  FIELDS USED TO DEFINE WORKFLOW
        Field Name             Description
        h_WorkflowStage        Indicates the status of the
                               document within the workflow.
              h_New = Created but not yet submitted for approval
              h_Submitted = Has been submitted and it is being
              reviewed
              h_Published = Has been approved
              h_Rejected = Has been rejected
        h_SetNextStageUser     The name of the next person in the
                               workflow cycle.
        h_CurrentApprover      A number designating the current
                               person in the workflow cycle. 0
                               means the Originator. The list of
                               persons associated with the
                               workflow cycle is stored in the
                               form used to create this page.

                             TABLE 19
                            Tag Styles
        CSS Selector    Description and Notes
        body, td        Default text style. Note: specify both tags
                        to set the default text style.
        a               Anchor style. Note: see also several other
                        more specific anchor styles, below.
        a:hover         Default style of anchors when mouse is over
                        the anchor. Note: IE only.
        form            Default style of forms. Note: The
                        margin-bottom property is set to Opx by
                        default to remove unwanted whitespace from
                        the bottom of all forms.
    (Note: Other tags, such as h1, h2, etc., can also be styled as needed.)


                         TABLE 20
                         Page Background
        CSS Selector      Description and Notes
        .h-page-bg        Page background. Note: class assigned to
                          body tag of all pages. For IE only, the
                          margin properties can be set to control the
                          page margin.


                         TABLE 21
               Folders, What's New, Search Results,
                        Tasks (list view)
        CSS Selector               Description and Notes
        .h-folderBanner-bg         Background of folder banner.
                                   Note 1.
        .h-folderBanner-text       Text in folder banner. Note
                                   1.
        a.h-folderBanner-text      Anchors in folder banner.
                                   Note 1.
        .h-folderBannerSelected-text Text of selected
                                   ("current") item in folder
                                   banner. Note 1.
        a.h-folderBannerSelected-text Selected anchor in folder
                                   banner. Note 1.
        .h-folderItem-bg           Background of items listed in
                                   folder. Note 1.
        .h-folderItem-text         Text of items listed in
                                   folder. Note 1.
        a.h-folderItem-text        Anchor listed in folder. Note
                                   1.
        .h-foldercompact-text      Compact text of item listed in
                                   folder. Note 1.
        .h-folderAbstract-text     Abstract text of item listed
                                   in folder.
        .h-folderBar-bg            Background of bar to left of a
                                   thread.
        .h-folder-dl {             Indentation of responses in
                                   response folder. Note: by
                                   default, the margin-bottom
                                   property is set to Opx to
                                   remove unwanted whitespace
                                   below indented items in
                                   response folders.
        .h-folderInterspace-bg { } Background color of vertical
                                   space between responses.
        .h-folderInterspace-text { Height of vertical space
                                   between responses. Note: use
                                   font-size to set the height.
        .h-folderSpace-text {      Height of vertical space
                                   between threads. Note: use
                                   font-size to set the height.
    Note 1: This style is used for the banner that displays column titles, as
     well as other banners in What's New, Search Results, etc.


                         TABLE 22
                      Tasks (timeline view)
        CSS Selector               Description and Notes
        .h-tasksBannerNow-textbg   Highlighted current date in
                                   Tasks banner.
        .h-tasksItem-bg            Background of items listed in
                                   Tasks.
        .h-tasksItemTimeline-bg    Highlighted period of a task.
        .h-tasksItemMilestone-bg   Highlighted period of a
                                   milestone


                         TABLE 23
                             Calendar
        CSS Selector               Description and Notes
        .h-calendarLabel-text      Date label.
        .h-calendarLabelSelected-text Date label (today's date).
        .h-calendarItemOther-bg    Background of day not in
                                   current month.
        .h-calendarItemToday-bg    Background of today's date.


                         TABLE 24
                  Text and fields in Page layout
        CSS Selector         Description and Notes
        .h-field-text,
        .h-field-text td     Style of the text value of a field.
                             Note: use this exact selector, as
                             shown, to style field text
                             distinctly from regular page
                             content.
        .h-pageSmall-text    "Smallprint" page text.
        .h-fieldSmall-text   "Smallprint" text content of
                             fields.
        .h-fieldHeader-bgtext Field header.
        .h-fieldOrder-bgtext Number to the left of the field
                             header.
        .h-page-text
        a:visited            Anchors inside the pageContent skin
                             component which have been visited.
                             Note: IE only.


                         TABLE 25
                           Edit Layout
        CSS Selector               Description and Notes
        .h-fieldHeaderEdit-bgtext  Field header
        .h-fieldEdit-text,
        .h-fieldEdit-text td       Field description text. Note:
                                   use exact selector, as shown.
        .h-fieldOrderEdit-bgtext, div
        .h-fieldOrderEdit-bgtext td Number to the left of the
                                   field header. Note: use exact
                                   selector, as shown. All
                                   properties in this selector
                                   must be marked ! important to
                                   take effect. E.g., color:
                                   green! important.
        .h-fieldSmallEdit-text     Small field text. Note: all
                                   properties in this selector
                                   must be marked ! important to
                                   take effect.
        .h-fieldSpecialEdit-text   Special field text. Note:
                                   used in Task Info field. All
                                   properties in this selector
                                   must be marked! important to
                                   take effect.


                         TABLE 26
                           QuickSearch
          CSS Selector         Description and Notes
          .h-searchField-text  Style of the text field associated
                               with the quickSearch skin
                               component.


                         TABLE 27
               Classes defined by the default theme
    The classes listed below are not built in to QuickPlace, but
     are defined by the default theme's style sheet. (Custom
    themes are not required to use these classes, and are free
     to define any other classes as appropriate.) However if
    modifying the default theme, these classes can be modified
                   to get a particular effect.
        CSS Selector                   Description and Notes
        .h-logo-text                   Logo text.
        .h-heading-textbg              Heading about table of
                                       contents and tools boxes.
        .h-sidebar-bg                  Background of table of
                                       contents and tool boxes.
        .h-toc-text                    Text of item listed in
                                       table of contents.
        .h-tocSelected-text            Text of selected item
                                       listed in table of
                                       contents.
        .h-nav-text                    Navigation link.
        .h-tool-text                   Tool link.
        .h-signIn-text                 Sign In link.
        .h-actionButtonBorder-bg       Border of action button.
        .h-actionButton-bg             Background of action
                                       button.
        .h-actionButton-text           Text of action button.
        .h-actionSpace-text            Space between action
                                       buttons.
        .h-pageTitle-textbg            Page title.
        .h-pageAuthorMod-text          AuthorAndModified text.
        .h-revision-text               Revision link (draft .vertline.
                                       published).
        .h-revisionSelected-text       Selected revision link
        .h-accent-bg                   Accent color. E.g., used
                                       in rule at bottom of
                                       page.
        .h-headlineFolderTab-bg        Background of unselected
                                       tab in headline folder.
        .h-headlineFolderTab-text      Text of unselected tab in
                                       headline folder.
        .h-headlineFolderTabSelected-bg Background of selected
                                       tab in headline folder.
        .h-headlineFolderTabSelected-text Text of selected tab in
                                       headline folder.
        .h-edit-bg                     Background of edit layout
                                       "docket".
        .h-actionButtonEdit-text       Text of action button in
                                       edit layout.
        .h-actionButtonBorderEdit-bg   Border of action button
                                       in edit layout.
        .h-actionButtonEdit-bg         Background of action
                                       button in edit layout.
        .h-shadow-bg                   Shadow. Note: used in
                                       sidebar and in edit
                                       layout "docket" shape.
        .h-shadowCorner-bg             "Missing" corner of
                                       shadow area.

                             TABLE 28
               SET DOCUMENT RELATED VARIABLES CODE
    sMapDocName = "SiteMap"
    Set ndb = ses.CurrentDatabase
    Set viewCurrent = ndb.getView( "h_Index" )
    Set docReport = viewCurrent.GetDocumentByKey(
    sMapDocName )
    If docReport Is Nothing Then
    Call logAgent.LogAction("Mapperizer: Document" &
    sMapDocName & "not found" )
    Exit Sub
    End If

                             TABLE 29
                     SET TOC AS SPECIAL VIEW
    Set viewTOC = ndb.getView("h_Toc")

                             TABLE 30
                   CREATE URLS/ATTACHED IMAGES
    Dim sFSlash As String
    Dim sBSlash As String
    Dim sDbLabel As String
    Dim iSlashPos As Integer
    sDbPath = ndb.FilePath & "/"
    sFSlash$ = Chr(47)
    sBSlash$ = Chr(92)
    iSlashPos = Instr(1, sDbPath$, sBSlash$)
    While iSlashPos <> 0
    Mid$ (sDbPath$, iSlashPos, 1) = sFSlash$
    iSlashPos = Instr(1, sDbPath$, sBSlash$)
    Wend

                             TABLE 31
                           TAG MAP HTML
    `writing sets
    sFolderImg = .vertline.<img src=../../h_index/.vertline. & sMapDocName &
    .vertline./$FILE/Folder.gif?OpenELement
    border=0
    width=20 height=13>.vertline.
    sPageImg = .vertline.<img src=../../h_index/.vertline. & sMapDocName &
    .vertline./$FILE/Page.gif?OpenELement
    border=0
    width=13 height=13>.vertline.
    sPageSubImg = .vertline.<img src=../../h_index/.vertline. & sMapDocName
     &
    .vertline./$FILE/PageSub.gif?OpenELement
    border=0
    width=29 height=13>.vertline.
    sIndentImg = .vertline.<img src=../../h_index/.vertline. & sMapDocName &
    .vertline./$FILE/Indent.gif?OpenELement
    border=0
    width=13 height=13>.vertline.
    sHeadingStyleTag = "<span class=h-mapHeading-text>"
    sStyleTag = "<span class=h-map-text>"
    sFolderStyleTag = "<span class=h-mapFolder-text>"
    sDetailStyleTag = "<span class=h-mapDetail-text>"
    sEndStyleTag = "</span>"
    sIndentConcat = ""

                             TABLE 32
                         TAG START OF MAP
    sHTMLHead = .vertline.<html><head><link rel=stylesheet
    type="text/css"
    href="Mapperizer.css"></head>.vertline. `only for debug
    sHTML01 = .vertline.<!-- start -->.vertline. `put JavaScripts here or
     the
    imported document
    sHTML02 = .vertline.<!-- end -->.vertline. `this will be
     concantenated at the
    end

                             TABLE 33
                      START LOOP THROUGH TOC
    sMainText = sHTML01
    Set docInTOC = viewTOC.GetFirstDocument
    If docInTOC Is Nothing Then `make sure the TOC is found
    Call logAgent.LogAction("Mapperizer: TOC Not Found" )
    Exit Sub
    End If

                             TABLE 34
                             STYLETAG
    sMainText = sMainText & sHeadingStyleTag &
    "All Documents in the"
    sMainText = sMainText & ndb.Title & "QuickPlace" &
    sEndStyleTag

                             TABLE 35
                       DATABASE STATISTICS
    sMainText = sMainText & "<br>" & sDetailStyleTag & "Current
    Database Size:"
    & Cstr(ndb.Size/1024) & "k"
    sMainText = sMainText & sDetailStyleTag & "Created:" &
    Cstr (ndb.Created)
    sMainText = sMainText & "Last Modified:" & Cstr(
    ndb.LastModified ) &
    sEndStyleTag & "<br>"

                             TABLE 36
                          TOC PROCESSING
    While Not ( docInTOC Is Nothing )
    If docInTOC.h_Type(0) = "0" Then `it is a doc
    Set docTemp = docInTOC

                             TABLE 37
                       ASSIGN DOCUMENT NAME
    If docTemp.h_Name(0) <> sMapDocName Then

                             TABLE 38
                BUILD URL FROM LINK TYPE DOCUMENT
    If docTemp.h_URLpointer(0) <> "" Then `it is a link
    sMainText = sMainText & "<br>" & "<a href=" &
    docTemp.h_URLpointer(0) & ">"

                             TABLE 39
                     BUILD URL FROM MAIN VIEW
    Else
    sMainText = sMainText & "<br>" & "<a href=../../h_Index/" &
    Cstr(docTemp.UniversalID)
    & "?OpenDocument>"
    End If
    sMainText = sMainText & sPageImg & sStyleTag &
    docTemp.h_Name(0) & sEndStyleTag
    sMainText = sMainText & sDetailStyleTag
    sMainText = sMainText & "(Last Changed:" &
    Cstr(docTemp.LastModified)
    sMainText = sMainText & "Size:"
    If docTemp.Size < 1024 Then
    sMainText = sMainText & "0"
    End If
    sMainText = sMainText & Cstr( docTemp.Size/1024 ) & "k"
    sMainText = sMainText & ")" & sEndStyleTag & "</a>"
    nLinkCount = nLinkCount + 1
    `end standard formatting
    End If

                             TABLE 40
                           LINK TO VIEW
    Elseif docInTOC.h_Type(0) = "1" Then `it is a folder/view
    sSysName = docInTOC.h_SystemName(0) `get the internal name
    of the view `if it is a link to a QuickPlace tool page

                             TABLE 41
                      INDENT RESPONSE FOLDER
    Else
    iNested = 0
    If docInTOC.h_FolderStyle(0) = "5" Then `it is a response
    folder
    iNested = 1
    End If

                             TABLE 42
          REDIRECT TO VIEW UPON REFERENCE TO DESIGN NOTE
    Set viewCurrent = ndb.getView( sSysName )
    sMainText = sMainText & "<br><a href=../../h_Index/" &
    Cstr(docInTOC.UniversalID)
    & "?OpenDocument>"
    sMainText = sMainText & Chr(13) & Chr(9) & sFolderImg
    sMainText = sMainText & sFolderStyleTag & docInTOC.h_Name(0)
    & sEndStyleTag & "</a>"

                             TABLE 43
                   GATHER ALL DOCUMENTS IN VIEW
    Set docTemp = viewCurrent.GetFirstDocument
    While Not (docTemp Is Nothing)
    If docTemp.h_Name(0) <> sMapDocName Then
    sMainText = sMainText & "<br>"
    If docTemp.IsResponse And iNested Then
    iIndentDistance = 13
    sIndentConcat = "<img src=blank.gif width=" &
    Cstr(iIndentDistance)
    & "height=1 border=0>"
    sPrevSetParentUnid = sThisSetParentUnid
    Else
    iIndentDistance = 0
    sIndentConcat = ""
    End If
    sMainText = sMainText & sIndentConcat

                             TABLE 44
                    LINK DOCUMENTS INDENTATION
    If docTemp.h_URLpointer(0) <> "" Then `it is a link
    sMainText = sMainText & "<a href=" & docTemp.h_URLpointer(0)
    & ">"
    Else
    sMainText = sMainText & "<a href=../../h_Index/" &
    Cstr(docTemp.UniversalID)
    & "?OpenDocument>"
    End If
    sMainText = sMainText & sPageSubImg & sStyleTag &
    docTemp.h_Name(0) & sEndStyleTag
    sMainText = sMainText & sDetailStyleTag
    sMainText = sMainText & "(Last Changed:" &
    Cstr(docTemp.LastModified)
    sMainText = sMainText & "Size:"
    If docTemp.Size < 1024 Then
    sMainText = sMainText & "0"
    End If
    sMainText = sMainText & Cstr( docTemp.Size/1024 ) & "k"
    sMainText = sMainText & ")" & sEndStyleTag & "</a>"
    Update the counter for displaying in the log.
    nLinkCount = nLinkCount + 1
    Start the loop again.
    End If
    Set docTemp = viewCurrent.GetNextDocument( docTemp )
    Wend
    End If

                             TABLE 45
                          MAP ROOM LINKS
    Else `it must be some other sort of link, such as a room
    (h_Type = "3")
    End If
    Set docInTOC = viewTOC.GetNextDocument( docInTOC )
    Wend
    Call logAgent.LogAction("Agent Mapped" & Cstr( nLinkCount )
    & "documents" )
    sMainText = sMainText & "<br>" & sHTML02 & "<br>"

                             TABLE 46
                     OUTPUT ACCUMULATED HTML
    If iDebug Then
    `debug version writes to a file
    fileNum% = Freefile()
    Open "D:.backslash.trash.backslash.trash.htm" For Output As fileNum%
    Print #fileNum%, sHTMLHead ; sMainText
    Close fileNum%
    Else
    `release version writes to a QuickPlace Main.nsf db
    docReport.PageBody = sMainText
    Call docReport.Save( True, True )
    End If
    Then finish off with the exit and error handing methods.
    Exit Sub
    lblLogError:
    Call logAgent.Logerror(Err, Error$)
    Resume Next
    End Sub

                             TABLE 47
                           FORCE UPLOAD
    <img src="Folder.gif">
    <img src="Page.gif">
    <img src="PageSub.gif">
    <img src="Indent.gif">

                             TABLE 48
                         PRINT TO SCREEN
    <script language=JavaScript>document.write( PageBody
    )</script>

                             TABLE 49
                 RENDER IMAGES ON SCREEN IN TABLE
    <table width=100% border=0 width=10 cellpadding=0
    cellspacing=0>
    <tr>
    <td height=1 align=right><img src="Folder.gif" width="1"
    height="1"><img
    src="Page.gif" width="1" height="1"><img src="PageSub.gif"
    width="1" height="1"><img
    src="Indent.gif" width="1" height="1"></td>
    </tr>
    </table>

                             TABLE 50
                        DRAW DOCUMENT BODY
    <script language=JavaScript>
    if ( typeof( PageBody ) == "undefined" ) {
    var PageBodyMessage = `Run the Mapperizer PlaceBot to see a
    site map .`;
    document.write( PageBodyMessage )
    } else{
    document.write( PageBody )
    }
    </script>

                             TABLE 51
                             LOG TEXT
    Started running agent `Mapperizer` on 09/05/2000 09:31:31 PM
    09/05/2000 09:31:31 PM: Mapperizer: IBM Redbook Example
    09/05/2000 09:31:31 PM: Mapperizer: Run agent: Mapperizer
    09/05/2000 09:31:32 PM: Agent Mapped 18 documents
    Ran LotusScript code
    Done running agent `Mapperizer` on 09/05/2000 09:31:32 PM