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 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 display 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.
    Note: To populate dynamically added fields of the Domino document, which are not part of the map inputs structure, use the AdditionalFields property and provide the field names and field values in FieldDetails section.

    For Form Types that are same across multiple databases, you can now specify the database name as part of the optional parameters in map inputs, wherein the same orchestration can be used to perform outbound operations on different databases. To do this you must specify the database name in the databaseName optional parameter (described in the table given below). If the databaseName parameter is populated with a value, the outbound operation will be performed on the database specified in the databaseName parameter. If there is no value specified, the database name specified during configuration will be used to perform the outbound operation.

    The optional input parameter is described in the following table:

    Table 1. Database name optional parameter
    Parameter Name Description
    databaseName Specifies the database name that can be dynamically added in map inputs to enable a single orchestration to perform outbound operations across multiple databases having the same Form Type.
    The Domino connector also supports dynamic endpoint connection to a different Domino server. During run time, if you want to dynamically connect to a Domino server other than the one that is configured in the endpoint page, add the new optional parameters in dominoConnectionProperties of map inputs. The parameters of dominoConnectionProperties are described in the following table:
    Table 2. Optional connection parameters
    Parameters Description
    dominoConnectionProperties parameters
    hostName Specifies the host name or IP address of the machine on which Domino server is running.
    diiopPort Specifies the Domino Internet Inter ORB Protocol (DIIOP) port that allows Java™ applets or applications to access Domino data remotely using CORBA. The default value is 63148.
    username Specifies the user name to connect to the Domino server.
    password Specifies the password associated with the user name to connect to the Domino server.
    connectionPool parameters
    minimumConnections Specifies the lowest number of Domino server connections that the Integration Appliance keeps open in the connection pool. Entering 0 (zero) is supported. The default value is 5.
    maximumConnections Specifies the maximum number of Domino server connections that the Integration Appliance can keep open in the connection pool. Entering 0 (zero) means the maximum number of connections is unbounded. The default value is 25.
    maxIdleTime Specifies the amount of time in minutes that a Domino server connection can be open in an idle state before being closed by the Integration Appliance. Entering 0 (zero) means that the connections are closed when they are returned to the pool —no idle time. The default value is 120 minutes.
    maxWait Specifies the amount of time in seconds that the Integration Appliance waits for a connection when all the connections in the pool are exhausted. If no connection is obtained after the wait time, an exception is thrown. The default value is 300 seconds.
    reclaimConnections Specifies the interval at which the connector checks for idle connections. Idle connections are reclaimed until the minimum number of connections is reached, as specified in the Minimum Connections parameter. The default value is 5 minute.

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.

    The response of the AdditionalFields property is also displayed in 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.

Summary flag (field flag) behavior

When a document is created for a form containing fields of type Authors, Readers, or Names; and data is set for these fields in the Map Input, the summary flag is set with proper permissions based on the Domino field type. This feature is supported from Domino server version 8.5.3 onwards.

For example:
  1. If a Domino field of type Authors is set with a value CN=SYSTEM/O=IBM, the summary flag will be SUMMARY READ/WRITE-ACCESS NAMES "CN=SYSTEM/O=IBM".
  2. If a Domino field of type Readers is set with a value CN=SYSTEM/O=IBM, the summary flag will be SUMMARY READ-ACCESS NAMES "CN=SYSTEM/O=IBM".
  3. If a Domino field of type Names is set with a value CN=SYSTEM/O=IBM, the summary flag will be SUMMARY NAMES "CN=SYSTEM/O=IBM".



Feedback | Notices


Timestamp icon Last updated: Tuesday, 27 September 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.doc/Domino_create_outactivity.html