Cloud Datastore (Beta) Insert Items activity

Introduction

A Cloud Datastore (Beta) Insert Items activity, using its Cloud Datastore (Beta) connection, inserts new data into a status storage or key storage and is intended to be used as a target to consume data in an operation.

Create a Cloud Datastore (Beta) Insert Items activity

An instance of a Cloud Datastore (Beta) Insert Items activity is created from a Cloud Datastore (Beta) connection using its Insert Items activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.

An existing Cloud Datastore (Beta) Insert Items activity can be edited from these locations:

• The design canvas (see Component actions menu in Design canvas).
• The project pane's Components tab (see Component actions menu in Project pane Components tab).

Configure a Cloud Datastore (Beta) Insert Items activity

Follow these steps to configure a Cloud Datastore (Beta) Insert Items activity:

• Step 1: Enter a name and specify settings
  Provide a name for the activity and specify the Cloud Datastore storage to interact with.

• Step 2: Review the data schemas
  Any request or response schemas are displayed.

Step 1: Enter a name and specify settings

In this step, provide a name for the activity and specify the storage. Each user interface element of this step is described below.

The interface used in this step of the configuration of an Insert Items activity depends on the Select storage option selected:

• Select existent storage: Select from a list of existing Cloud Datastore storages.
• Enter storage name manually: Manually enter the name of the Cloud Datastore storage.

Select existent storage

If Select existent storage is selected for Select storage, this user interface is presented:

• Name: Enter a name to identify the activity. The name must be unique for each Cloud Datastore (Beta) Insert Items activity and must not contain forward slashes / or colons :.

• Select storage: Select the option Select existent storage to choose an existing storage from a populated list.

• Select a storage: This section displays Cloud Datastore storages available for the environment.

  • Selected storage: After a storage is selected, it is listed here.

  • Search: Enter any column's value into the search box to filter the list of storages. The search is not case-sensitive. If storages are already displayed within the table, the table results are filtered in real time with each keystroke. To reload storages from the endpoint when searching, enter search criteria and then refresh, as described below.

  • Refresh: Click the refresh icon or the word Refresh to reload items from the Cloud Datastore endpoint. This may be useful if storages have been added or edited in Cloud Datastore. This action refreshes all metadata used to build the table of storages displayed in the configuration.

  • Selecting a storage: Within the table, click anywhere on a row to select a storage. Only one storage can be selected. The information available for each storage is fetched from the Cloud Datastore endpoint:

    • Name: The name of the storage.

    • Type: The type of storage, either Lookup by Key (key storage) or Lookup by Status (status storage).

    • Description: The description of the storage provided during storage creation.

• Optional settings: Click to expand additional optional settings:

  • Insert Strategy: Select the method of inserting data:

    • Prevail ordering of items during the insert (default): When selected during a batch request, the ordering of the inserted items is prioritized. This option can result in longer processing times.

    • Prevail performance with batch insertion (item ordering cannot be guaranteed): When selected during a batch request, the ordering of the inserted items is not prioritized and is delegated to Cloud Datastore itself.

  • Continue on error: Select to continue the activity execution if an error is encountered for a dataset in a batch request. If any errors are encountered, they are written to the operation log.

• Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

• Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Enter storage name manually

If Enter storage name manually is selected for Select storage, this user interface is presented:

• Name: Enter a name to identify the activity. The name must be unique for each Cloud Datastore (Beta) Insert Items activity and must not contain forward slashes / or colons :.

• Storage: Enter the name of the storage to interact with.

• Optional settings: Click to expand additional optional settings:

  • Insert Strategy: Select the method of inserting data:

    • Prevail ordering of items during the insert (default): When selected during a batch request, the ordering of the inserted items is prioritized. This option can result in longer processing times.

    • Prevail performance with batch insertion (item ordering cannot be guaranteed): When selected during a batch request, the ordering of the inserted items is not prioritized and is delegated to Cloud Datastore itself.

• Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

• Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the data schemas

Any request or response schemas are displayed. Each user interface element of this step is described below.

• Data Schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

  Note

  Data supplied in a transformation takes precedence over the activity configuration.

  The request and response data schemas consist of these nodes and fields:

  Key storage request node or field	Description
  json	Node containing the JSON request schema
  <custom field>	Any custom fields are included in the request
  Value	The item's user-defined Value for the key-value pair
  Key	The item's user-defined Key for the key-value pair
  AlternativeKey	The item's user-defined alternative key that accepts the value of the key-value pair

  Status storage request node or field	Description
  json	Node containing the JSON request schema
  Status	The success or failure of the operation
  RetryPolicyRetryCount	(For internal use only)
  RetryPolicyLastRetryDate	(For internal use only)
  DuplicationControl	(For internal use only)
  RetryPolicyNextRetryDate	(For internal use only)
  Key	The user-provided identifier of the item (set in an Insert Items activity)
  StatusMessage	Message with information on the insert status
  MessageBody	BigText for the operation payload

  Key and status storage response node or field	Description
  json	Node containing the JSON request schema
  responses	Node containing any responses
  item	Node containing each inserted item
  data	Data inserted into the storage
  id	The ID of the storage item
  created	Boolean representing the success (true) or failure (false) of the creation
  errors	Node containing any errors
  item	Node containing any error messages
  message	An error message

• Refresh: Click the refresh icon or the word Refresh to regenerate schemas from the Cloud Datastore (Beta) endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

• Back: Click to temporarily store the configuration for this step and return to the previous step.

• Finished: Click to save the configuration for all steps and close the activity configuration.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next steps

After configuring a Cloud Datastore (Beta) Insert Items activity, complete the configuration of the operation by adding and configuring other activities or tools as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

Cloud Datastore (Beta) Insert Items activities can be used as a target with these operation patterns:

• Transformation Pattern
• Two-transformation Pattern (as the first or second target)

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.