Creating a Domino document

Use the Create Document activity to create a document in the Domino server.

Using the create activity

  1. Right-click Orchestration in the Project pane and click New Orchestration to create or open an orchestration. The orchestration pane is displayed.
  2. Select the Activities tab and expand the Domino folder.
  3. Drag and drop Create Document activity from the Domino folder onto the orchestration. The graphical representation of the orchestration, including the checklist is displayed.
  4. The Checklist pane lists the tasks (Summary, Pick Endpoint, Configure, Map inputs, Map outputs) that you must complete to configure the outbound activity.
  5. Click Pick Endpoint, and then select a Domino endpoint.

    For instructions on creating or editing a Domino endpoint, see Creating or editing an endpoint for a Domino activity

  6. Click Configure from the Checklist. The Configure pane is displayed.
    • Click Browse to select an existing database from the Browse Domino databases pane. The Browse Domino databases displays all the databases for the selected endpoint.
    • Click Next to select an existing form from the Browse Domino Forms pane. The Browse Domino Forms displays all the forms present in the selected database of the Domino server.
Note: The Next button is enabled only after selecting the database name.

Specifying the map inputs for create activity

  1. Click Map Input from the Checklist pane.

    The input parameters for the specific Domino activity are displayed under the To Activity pane.

    Note: You must map all the required input parameters of the activity, whose data comes from previous activity.

Specifying the map outputs create activity

  1. Click Map output from the Checklist pane.

    The output parameters for the Domino activity are displayed under the From Activity pane.

    Some of the common output parameters are defined in the following table.
    Parameter Name Description
    UniversalID A UniversalID of a document is a read-write property that uniquely identifies a document across all replicas of a database. In character format, the UniversalID is a 32-character combination of hexadecimal digits (0-9, A-F). The UniversalID is also known as the uniqueID or UNID. The datatype is string.
    NotesID A NotesID of a document is a read only property and has a hexadecimal value of up to 8 characters, which uniquely identifies a document within a particular database. A note ID represents the location of a document within a specific database file. So the documents that are replicas of one another generally have different note IDs. A note ID does not change, unless the document is deleted.
    Form A form provides the structure for creating and displaying documents, which are the design elements that store data in the database. When you enter the information in a form and save it, the information is saved as a document. When you open the document, the document uses the form as a template to provide the structure for displaying the data.
    Note: Changing a form (for example, by adding a field) does not change documents previously created with that form until they are modified and saved, either manually or automatically by an agent. Removing a field from a form does not remove the value of that field from previously created documents.
    ParentDocumentUNID A parentdocumentUNID of a document is a read-only property. It is defined as the universal ID of a document's parent, if the document is a response document. If a document does not have a parent, it returns an empty string (""). The datatype is string.

    Note: You can map the output parameters of the activity based on requirement.