Lotus Notes/Domino Tutorials... View in Kryl|View in English




LotusScript

  • This course will take you step by step through the process of creating a LotusScript agent, starting with a general idea of what you need an agent to do, and going through all the steps to create and test that agent. It will introduce some concepts that are essential to programming in LotusScript, and describe some of the thought processes that might be used to create an agent to accomplish the job at hand.
    Courtesy: IBM
  • [Info][Site]






    LotusScript

  • In order to create LotusScript agents, you must have the Domino Designer client installed. To verify that you have the Domino Designer client, start your Notes client and look for the Designer icon in the Bookmarks bar at the left of the Notes client window. It looks like the yellow Notes icon with a green triangle on top of it. Courtesy: IBM
  • [Info][Site]






    LotusScript

  • For this module, imagine that you work for a company that provides services to industries across the US. Your customers are divided into four regions with home offices in each region. All customers call one common 800 number to place an order for services, and the person taking the call creates a document in a Notes database to route the order to the correct regional office by filling out the region and city fields in the form. All of these documents appear in a view named "Service Requests". Courtesy: IBM

    [Info][Site]






    LotusScript

  • To take a look at the types of Domino Object variables that are available in the LotusScript programming language, go to the Designer Help LotusScript/COM/OLE Classes / LotusScript Classes A-Z. You can expand the section LotusScript Classes A - Z to see the list of all the LotusScript classes for working with Notes and Domino. Courtesy: IBM
  • [Info][Site]






    LotusScript

  • Open the example database in the Designer client, by first starting the Designer client, and then use File - Database - Open to select and open the database in the Designer client, just like we did to open it in the Notes client. Courtesy: IBM
  • [Info][Site]






    LotusScript

  • For a list of these keywords, open the Designer Help topic Language / Script and Statement Construction Rules / Keywords for a alphabetical listing of all the LotusScript keywords. Do not use any of these words when naming your variables. Courtesy: IBM
  • [Info][Site]






    LotusScript

  • The Domino object system is organized in a hierarchy, in which objects are contained by other objects, and they also contain other objects. This is displayed visually in a chart that you can display in the Designer client. Courtesy: IBM


  • [Info][Site]



    LotusScript

  • Look again at the "Domino Class for LotusScript and OLE" chart on the Designer client welcome page. The top of the back-end class hierarchy is the NotesSession class. This is indicated in the classes chart by the fact that there are arrows going only from the NotesSession box, there are no arrows going to it. Courtesy: IBM
  • [Info][Site]






    LotusScript

  • Another class we are going to need to work with in our sample agent is the NotesDatabase class. The database is the container for all data in Notes and Domino, so you can expect to be using this class a lot. To find the documentation on this class, go to the Designer Help topic LotusScript/COM/OLE Classes / LotusScript Classes A-Z / NotesDatabase. Courtesy: Eclipse.org
  • [Info][Site]






    LotusScript

  • Earlier, we created our agent named "Update Locations", but did not put any code in it. Now that we know a little bit about the NotesSession and NotesDatabase classes, we can use that knowledge to start writing the code for our agent. So with the database open in the Designer client, under Shared Code click on Agents, and we see our agent on the right part of the screen. Double-click the "Update Locations" agent to edit it, and since we have already set the Agent Properties we can close that dialog box. In the Objects pane, click on Initialize. This is where the code for the agent will go. Courtesy: JasperSoft.org
  • [Info][Site]






    LotusScript

  • A common practice with LotusScript agents is to write an agent to process the documents that are in a particular view in a database. A view provides a convenient way to have an agent operate only on documents that meet a certain criteria, because a view selection formula specifies what criteria a document must meet to appear in that view. Courtesy: IBM
  • [Info][Site]






    LotusScript

  • The LotusScript class that represents a Notes document is the NotesDocument class. Just as you spend most of your time working in documents in your Notes client, you will be using the NotesDocument class a lot in LotusScript because the document is the core component of data in Notes. LotusScript provides the ability to create documents, put data in document fields, and read data from document fields, as well as ways to get other information about documents. Take a minute to review the list of properties and methods of the NotesDocument class in Designer Help. Courtesy: IBM
  • [Info][Site]



    Back 2 top