Imports

Import refers to a collection of records brought into the software's staging area from an external source. Each import record is expected to include details such as the asset name, type, and pertinent metadata like Host, User, Password, Tags, or Included IP Addresses.

Once the import data is uploaded to the staging area, administrators can verify its integrity. A background validation process checks the existence of relevant asset types, containers, taxonomy values, referenced or member assets, and provides results within the import row for further inspection.

Upon successful validation, administrators can initiate a separate background import process for the selected import rows. This process generates assets within the software and tags the import rows with the created assets for future reference and navigation.

The initial upload of data to the staging area can be triggered from container actions, where the container acts as the destination for the import process and where imported assets are created.

This page displays the list of imports created in the software with the options to view the import details or to delete the import.

Creating the CSV Import File

The software parses an uploaded CSV file to perform the validation and eventual import of new assets and containers into the Asset Database. This CSV import file supports the following column headers:

Index: is an optional internal string that could be used to reference an asset from another part of the CSV (for example, a container, base or member asset)
Name: is the asset name. Name is a mandatory field for the entry to pass a validation. If a name is not specified the process will use the Host field value as the asset name.
Description: is the asset description.
Type: is the asset type by name (case sensitive) from the space asset types list.
Parents: is the list of asset container parents given by container name, double-colon separated path (A :: B :: C) or container index from the same CSV spreadsheet. Multiple parents are separated by an ENTER.
Base: is the base asset given by the asset name, double-colon separated path (A :: B :: C) or an asset index from the same CSV spreadsheet.
Members: is the list of asset members given by the list of Role:Asset pairs separated by ENTER where the role is a member Role and the asset is given by the asset name, double-colon separated path (A :: B :: C) or an asset index from the same CSV spreadsheet.
Tags: is the list of terms from the Tags field taxonomy given by double-colon separated term path (A :: B :: C). Multiple tags are separated by ENTER.
Custom Fields: are custom fields that could be applied to the asset with a column per each field. Examples of the fields are Host,User,Password,Private Key, Private Key Password,Included,Excluded.

Importing Assets from CSV

Using the guidance above to create a new CSV import file or using this CSV Example File as a template, perform the following steps to process the file for import:

Log in with an Administrator, Asset Manager or an account with the Container Asset Creator role on the container where the import is to occur.
Navigate into the container where the import is to take place and click the Actions > Import option.
Select CSV for the Type parameter.
For the File parameter, click the Upload button to the right side of this field and select your CSV file.
In the Action After Upload parameter, choose one of the available options:
- None: the import to the staging area will begin, but neither validation nor import will take place during this operation. Both Validation and Import operations can be performed manually after this process is complete.
- Start Validation: the import to the staging area will begin and validation will automatically be performed immediately after the staging import is complete. Import to the Asset Database will not occur automatically with this option.
- Start Import: the import to the staging area will begin and import to the Asset Database will automatically be performed immediately after the staging import is complete. No validation is performed between staging import and asset database import with this option.
When complete, click the Save button to begin the operation.

After the import is saved, you will be redirected to the View Import page where details, statuses and actions are available.

Note

If an asset with the same name already exists at the same location, the import operation will create a new minor version of this existing asset (major version with containers).

Importing Assets from LDAP (Active Directory)

Computer hosts can be imported from any enabled LDAP configuration that has been established between this tenant and an LDAP compatible directory, most commonly Microsoft Active Directory.

To import LDAP computer hosts as assets, perform the following steps:

Log in with an Administrator, Asset Manager or an account with the Container Asset Creator role on the container where the import is to occur.
Navigate into the container where the import is to take place and click the Actions > Import option.
Select LDAP for the Type parameter.
For the LDAP Configuration parameter, select the active LDAP configuration to be used, from the dropdown menu. Before performing an LDAP import, make sure that the LDAP configuration successfully connects to the LDAP server.
In the Query field, use the default query or create a custom query to return a list of Computers for import. Use LDAP search filter syntax to define your queries. The default query will return all computers with the operating system Windows Server.
Use the Asset Type parameter to define which asset type will be used to create each imported asset.
In the Reference Asset field specify the reference asset to use as a Shadow member asset to provide credentials to connect to each of the imported assets. For example, specify the asset with domain administrator or a shared account credentials that will be used to connect to every imported host.
In the Action After Upload parameter, choose one of the available options:
- None: the import to the staging area will begin, but neither validation nor import will take place during this operation. Both Validation and Import operations can be performed manually after this process is complete.
- Start Validation: the import to the staging area will begin and validation will automatically be performed immediately after the staging import is complete. Import to the Asset Database will not occur automatically with this option.
- Start Import: the import to the staging area will begin and import to the Asset Database will automatically be performed immediately after the staging import is complete. No validation is performed between staging import and asset database import with this option.
When complete, click the Save button to begin the operation.

After the import is saved, you will be redirected to the View Import page where details, statuses and actions are available.

AD attribute name is mapped to asset Name, operatingSystem is mapped to asset Description and dNSHostName is mapped to asset Host.

Note

If an asset with the same name already exists at the same location, the import operation will create a new minor version of the existing asset.

Importing Assets from VMWare

Computer hosts can be imported from any enabled VMWare configuration that has been established between this tenant and a VMWare instance.

To import VMWare hosts as assets, perform the following steps:

Log in with an Administrator, Asset Manager or an account with the Container Asset Creator role on the container where the import is to occur.
Navigate into the container where the import is to take place and click the Actions > Import option.
Select VMWare for the Type parameter.
For the VMWare Configuration parameter, select the enabled VMWare configuration to be used, from the dropdown menu. Before performing a VMWare import, make sure that the VMWare configuration successfully connects to the VMWare host.
In the Query field, enter a value that will filter upon the VMWare's Guest OS Family like Linux, Windows or Other. An empty query will return all VMWare hosts with any defined OS Family.
Use the Asset Type parameter to define which asset type will be used to create each imported asset.
In the Reference Asset field specify the reference asset to use as a Shadow member asset to provide credentials to connect to each of the imported assets. For example, specify the asset with domain administrator or a shared account credentials that will be used to connect to every imported host.
In the Action After Upload parameter, choose one of the available options:
- None: the import to the staging area will begin, but neither validation nor import will take place during this operation. Both Validation and Import operations can be performed manually after this process is complete.
- Start Validation: the import to the staging area will begin and validation will automatically be performed immediately after the staging import is complete. Import to the Asset Database will not occur automatically with this option.
- Start Import: the import to the staging area will begin and import to the Asset Database will automatically be performed immediately after the staging import is complete. No validation is performed between staging import and asset database import with this option.
When complete, click the Save button to begin the operation.

After the import is saved, you will be redirected to the View Import page where details, statuses and actions are available.

VM Name is mapped to asset Name, 'VM Guest OS; VM Host Name' is mapped to asset Description and VM IP Address is mapped to asset Host.

Note

If an asset with the same name already exists at the same location, the import operation will create a new minor version of the existing asset.

Importing Assets from AWS

EC2 instances can be imported from any enabled AWS configuration that has been established between this tenant and AWS.

To import AWS EC2 Instances as assets, perform the following steps:

Log in with an Administrator, Asset Manager or an account with the Container Asset Creator role on the container where the import is to occur.
Navigate into the container where the import is to take place and click the Actions > Import option.
Select AWS for the Type parameter.
For the AWS Configuration parameter, select the enabled AWS configuration to be used, from the dropdown menu. Before performing an AWS import, make sure that the AWS configuration connects successfully.
In the Query field, enter a query that will filter the import using the details of EC2 Instances like Instance ID, Platform, IP-Address and many others. An empty query will return all EC2 Instances. For more information about these queries, please review the AWS Queries section below.
Use the Visibility parameter to select either Public or Private which instructs the import process to use either the public or private IP Address and Host Name of each EC2 Instance when creating the asset.
Use the Asset Type parameter to define which asset type will be used to create each imported asset.
In the Reference Asset field specify the reference asset to use as a Shadow member asset to provide credentials to connect to each of the imported assets. For example, specify the asset with domain administrator or a shared account credentials that will be used to connect to every imported host.
In the Action After Upload parameter, choose one of the available options:
- None: the import to the staging area will begin, but neither validation nor import will take place during this operation. Both Validation and Import operations can be performed manually after this process is complete.
- Start Validation: the import to the staging area will begin and validation will automatically be performed immediately after the staging import is complete. Import to the Asset Database will not occur automatically with this option.
- Start Import: the import to the staging area will begin and import to the Asset Database will automatically be performed immediately after the staging import is complete. No validation is performed between staging import and asset database import with this option.
When complete, click the Save button to begin the operation.

After the import is saved, you will be redirected to the View Import page where details, statuses and actions are available.

Public/Private IP DNS Name is mapped to asset Name, Platform Details is mapped to asset Description and Public/Private IP address is mapped to asset Host.

Note

If an asset with the same name already exists at the same location, the import operation will create a new minor version of the existing asset.

AWS Queries

AWS Queries are used to filter specific EC2 instances during import. AWS Query is a comma-separated list of filter criteria built from name=value pairs where name is the name of the filter and value is the value to query for the name, or the list of comma separated values in parenthesis.

Below is an example of a query to filter Linux instances with t2.nano or t3.micro instance types.

platform-details = Linux/UNIX, instance-type=(t2.nano, t3.micro)

Below is an example of a query to filter Windows instances with t2.nano or t3.micro instance types.

platform = windows

Please refer to AWS documentation for a complete list of supported filter conditions. Several examples of filters are given below:

affinity - The affinity setting for an instance running on a Dedicated Host (default | host).
architecture - The instance architecture (i386 | x86_64 | arm64).
availability-zone - The Availability Zone of the instance.
block-device-mapping.attach-time - The attach time for an EBS volume mapped to the instance, for example, 2022-09-15T17:15:20.000Z.
block-device-mapping.delete-on-termination - A Boolean that indicates whether the EBS volume is deleted on instance termination.
block-device-mapping.device-name - The device name specified in the block device mapping (for example, /dev/sdh or xvdh).
block-device-mapping.status - The status for the EBS volume (attaching | attached | detaching | detached).
block-device-mapping.volume-id - The volume ID of the EBS volume.
boot-mode - The boot mode that was specified by the AMI (legacy-bios | uefi | uefi-preferred).
capacity-reservation-id - The ID of the Capacity Reservation into which the instance was launched.
capacity-reservation-specification.capacity-reservation-preference - The instance's Capacity Reservation preference (open | none).
capacity-reservation-specification.capacity-reservation-target.capacity-reservation-id - The ID of the targeted Capacity Reservation.
capacity-reservation-specification.capacity-reservation-target.capacity-reservation-resource-group-arn - The ARN of the targeted Capacity Reservation group.
client-token - The idempotency token you provided when you launched the instance.
current-instance-boot-mode - The boot mode that is used to launch the instance at launch or start (legacy-bios | uefi).
dns-name - The public DNS name of the instance.
ebs-optimized - A Boolean that indicates whether the instance is optimized for Amazon EBS I/O.
ena-support - A Boolean that indicates whether the instance is enabled for enhanced networking with ENA.
enclave-options.enabled - A Boolean that indicates whether the instance is enabled for AWS Nitro Enclaves.
hibernation-options.configured - A Boolean that indicates whether the instance is enabled for hibernation. A value of true means that the instance is enabled for hibernation.
host-id - The ID of the Dedicated Host on which the instance is running, if applicable.
hypervisor - The hypervisor type of the instance (ovm | xen). The value xen is used for both Xen and Nitro hypervisors.
iam-instance-profile.arn - The instance profile associated with the instance. Specified as an ARN.
iam-instance-profile.id - The instance profile associated with the instance. Specified as an ID.
image-id - The ID of the image used to launch the instance.
instance-id - The ID of the instance.
instance-lifecycle - Indicates whether this is a Spot Instance, a Scheduled Instance, or a Capacity Block (spot | scheduled | capacity-block).
instance-state-code - The state of the instance, as a 16-bit unsigned integer. The high byte is used for internal purposes and should be ignored. The low byte is set based on the state represented. The valid values are: 0 (pending), 16 (running), 32 (shutting-down), 48 (terminated), 64 (stopping), and 80 (stopped).
instance-state-name - The state of the instance (pending | running | shutting-down | terminated | stopping | stopped).
instance-type - The type of instance (for example, t2.micro).
instance.group-id - The ID of the security group for the instance.
instance.group-name - The name of the security group for the instance.
ip-address - The public IPv4 address of the instance.
ipv6-address - The IPv6 address of the instance.
kernel-id - The kernel ID.
key-name - The name of the key pair used when the instance was launched.
launch-index - When launching multiple instances, this is the index for the instance in the launch group (for example, 0, 1, 2, and so on).
launch-time - The time when the instance was launched, in the ISO 8601 format in the UTC time zone (YYYY-MM-DDThh:mm:ss.sssZ), for example, 2021-09-29T11:04:43.305Z. You can use a wildcard (), for example, 2021-09-29T, which matches an entire day.
maintenance-options.auto-recovery - The current automatic recovery behavior of the instance (disabled | default).
metadata-options.http-endpoint - The status of access to the HTTP metadata endpoint on your instance (enabled | disabled)
metadata-options.http-protocol-ipv4 - Indicates whether the IPv4 endpoint is enabled (disabled | enabled).
metadata-options.http-protocol-ipv6 - Indicates whether the IPv6 endpoint is enabled (disabled | enabled).
metadata-options.http-put-response-hop-limit - The HTTP metadata request put response hop limit (integer, possible values 1 to 64)
metadata-options.http-tokens - The metadata request authorization state (optional | required)
metadata-options.instance-metadata-tags - The status of access to instance tags from the instance metadata (enabled | disabled)
metadata-options.state - The state of the metadata option changes (pending | applied).
monitoring-state - Indicates whether detailed monitoring is enabled (disabled | enabled).
network-interface.addresses.association.allocation-id - The allocation ID.
network-interface.addresses.association.association-id - The association ID.
network-interface.addresses.association.carrier-ip - The carrier IP address.
network-interface.addresses.association.customer-owned-ip - The customer-owned IP address.
network-interface.addresses.association.ip-owner-id - The owner ID of the private IPv4 address associated with the network interface.
network-interface.addresses.association.public-dns-name - The public DNS name.
network-interface.addresses.association.public-ip - The ID of the association of an Elastic IP address (IPv4) with a network interface.
network-interface.addresses.primary - Specifies whether the IPv4 address of the network interface is the primary private IPv4 address.
network-interface.addresses.private-dns-name - The private DNS name.
network-interface.addresses.private-ip-address - The private IPv4 address associated with the network interface.
network-interface.association.allocation-id - The allocation ID returned when you allocated the Elastic IP address (IPv4) for your network interface.
network-interface.association.association-id - The association ID returned when the network interface was associated with an IPv4 address.
network-interface.association.carrier-ip - The customer-owned IP address.
network-interface.association.customer-owned-ip - The customer-owned IP address.
network-interface.association.ip-owner-id - The owner of the Elastic IP address (IPv4) associated with the network interface.
network-interface.association.public-dns-name - The public DNS name.
network-interface.association.public-ip - The address of the Elastic IP address (IPv4) bound to the network interface.
network-interface.attachment.attach-time - The time that the network interface was attached to an instance.
network-interface.attachment.attachment-id - The ID of the interface attachment.
network-interface.attachment.delete-on-termination - Specifies whether the attachment is deleted when an instance is terminated.
network-interface.attachment.device-index - The device index to which the network interface is attached.
network-interface.attachment.instance-id - The ID of the instance to which the network interface is attached.
network-interface.attachment.instance-owner-id - The owner ID of the instance to which the network interface is attached.
network-interface.attachment.network-card-index - The index of the network card.
network-interface.attachment.status - The status of the attachment (attaching | attached | detaching | detached).
network-interface.availability-zone - The Availability Zone for the network interface.
network-interface.deny-all-igw-traffic - A Boolean that indicates whether a network interface with an IPv6 address is unreachable from the public internet.
network-interface.description - The description of the network interface.
network-interface.group-id - The ID of a security group associated with the network interface.
network-interface.group-name - The name of a security group associated with the network interface.
network-interface.ipv4-prefixes.ipv4-prefix - The IPv4 prefixes that are assigned to the network interface.
network-interface.ipv6-address - The IPv6 address associated with the network interface.
network-interface.ipv6-addresses.ipv6-address - The IPv6 address associated with the network interface.
network-interface.ipv6-addresses.is-primary-ipv6 - A Boolean that indicates whether this is the primary IPv6 address.
network-interface.ipv6-native - A Boolean that indicates whether this is an IPv6 only network interface.
network-interface.ipv6-prefixes.ipv6-prefix - The IPv6 prefix assigned to the network interface.
network-interface.mac-address - The MAC address of the network interface.
network-interface.network-interface-id - The ID of the network interface.
network-interface.outpost-arn - The ARN of the Outpost.
network-interface.owner-id - The ID of the owner of the network interface.
network-interface.private-dns-name - The private DNS name of the network interface.
network-interface.private-ip-address - The private IPv4 address.
network-interface.public-dns-name - The public DNS name.
network-interface.requester-id - The requester ID for the network interface.
network-interface.requester-managed - Indicates whether the network interface is being managed by AWS.
network-interface.status - The status of the network interface (available) | in-use).
network-interface.source-dest-check - Whether the network interface performs source/destination checking. A value of true means that checking is enabled, and false means that checking is disabled. The value must be false for the network interface to perform network address translation (NAT) in your VPC.
network-interface.subnet-id - The ID of the subnet for the network interface.
network-interface.tag-key - The key of a tag assigned to the network interface.
network-interface.tag-value - The value of a tag assigned to the network interface.
network-interface.vpc-id - The ID of the VPC for the network interface.
outpost-arn - The Amazon Resource Name (ARN) of the Outpost.
owner-id - The AWS account ID of the instance owner.
placement-group-name - The name of the placement group for the instance.
placement-partition-number - The partition in which the instance is located.
platform - The platform. To list only Windows instances, use windows.
platform-details - The platform (Linux/UNIX | Red Hat BYOL Linux | Red Hat Enterprise Linux | Red Hat Enterprise Linux with HA | Red Hat Enterprise Linux with SQL Server Standard and HA | Red Hat Enterprise Linux with SQL Server Enterprise and HA | Red Hat Enterprise Linux with SQL Server Standard | Red Hat Enterprise Linux with SQL Server Web | Red Hat Enterprise Linux with SQL Server Enterprise | SQL Server Enterprise | SQL Server Standard | SQL Server Web | SUSE Linux | Ubuntu Pro | Windows | Windows BYOL | Windows with SQL Server Enterprise | Windows with SQL Server Standard | Windows with SQL Server Web).
private-dns-name - The private IPv4 DNS name of the instance.
private-dns-name-options.enable-resource-name-dns-a-record - A Boolean that indicates whether to respond to DNS queries for instance hostnames with DNS A records.
private-dns-name-options.enable-resource-name-dns-aaaa-record - A Boolean that indicates whether to respond to DNS queries for instance hostnames with DNS AAAA records.
private-dns-name-options.hostname-type - The type of hostname (ip-name | resource-name).
private-ip-address - The private IPv4 address of the instance. This can only be used to filter by the primary IP address of the network interface attached to the instance. To filter by additional IP addresses assigned to the network interface, use the filter network-interface.addresses.private-ip-address.
product-code - The product code associated with the AMI used to launch the instance.
product-code.type - The type of product code (devpay | marketplace).
ramdisk-id - The RAM disk ID.
reason - The reason for the current state of the instance (for example, shows "User Initiated [date]" when you stop or terminate the instance). Similar to the state-reason-code filter.
requester-id - The ID of the entity that launched the instance on your behalf (for example, AWS Management Console, Auto Scaling, and so on).
reservation-id - The ID of the instance's reservation. A reservation ID is created any time you launch an instance. A reservation ID has a one-to-one relationship with an instance launch request, but can be associated with more than one instance if you launch multiple instances using the same launch request. For example, if you launch one instance, you get one reservation ID. If you launch ten instances using the same launch request, you also get one reservation ID.
root-device-name - The device name of the root device volume (for example, /dev/sda1).
root-device-type - The type of the root device volume (ebs | instance-store).
source-dest-check - Indicates whether the instance performs source/destination checking. A value of true means that checking is enabled, and false means that checking is disabled. The value must be false for the instance to perform network address translation (NAT) in your VPC.
spot-instance-request-id - The ID of the Spot Instance request.
state-reason-code - The reason code for the state change.
state-reason-message - A message that describes the state change.
subnet-id - The ID of the subnet for the instance.
tag: - The key/value combination of a tag assigned to the resource. Use the tag key in the filter name and the tag value as the filter value. For example, to find all resources that have a tag with the key Owner and the value TeamA, specify tag:Owner for the filter name and TeamA for the filter value.
tag-key - The key of a tag assigned to the resource. Use this filter to find all resources that have a tag with a specific key, regardless of the tag value.
tenancy - The tenancy of an instance (dedicated | default | host).
tpm-support - Indicates if the instance is configured for NitroTPM support (v2.0).
usage-operation - The usage operation value for the instance (RunInstances | RunInstances:00g0 | RunInstances:0010 | RunInstances:1010 | RunInstances:1014 | RunInstances:1110 | RunInstances:0014 | RunInstances:0210 | RunInstances:0110 | RunInstances:0100 | RunInstances:0004 | RunInstances:0200 | RunInstances:000g | RunInstances:0g00 | RunInstances:0002 | RunInstances:0800 | RunInstances:0102 | RunInstances:0006 | RunInstances:0202).
usage-operation-update-time - The time that the usage operation was last updated, for example, 2022-09-15T17:15:20.000Z.
virtualization-type - The virtualization type of the instance (paravirtual | hvm).
vpc-id - The ID of the VPC that the instance is running in.

View Imports

Once the CSV import process is uploaded, regardless of the Action After Upload selected, you can view the details of the import upload from its View Import page. You should be automatically redirected to this page, but if you need to navigate to it manually, you can do so from the Database > Imports menu.

The View Import page provides extended details about the uploaded CSV file, actions to process the assets and status or operations. To use the View Imports page:

Log in with Administrator, Asset Manager or an account with the Container Asset Creator role on the container where the import is to occur.
Navigate to Database > Imports and for the import you wish to review, click its Actions > View option.
This import specific View Import page provides the following details and options:
- Type: Type of file uploaded for import.
- Name: Name of the uploaded file.
- Container: Root container where imported assets will be created.
- Created At: Creation time of import entry.
- Statistics: Import statistics of the uploaded file. This includes the total number of objects processed, total number of draft objects (those not validated nor imported), total number of validated objects and total number of imported objects. Number are represented based on the object's state in the format INFO/WARN/ERROR.
- State: State of the import entry in the import workflow with states:
  - Draft: The entry loaded into the import
  - Validated: The entry is validated
  - Imported: The entry is imported into the asset database
- Level: State level of import entry processing:
  - INFO: The processing of the entry is successful.
  - WARN: The entry processing finished successfully but with warnings.
  - ERROR: The entry processing finished with errors usually indicated in Messages field.
- Name: is the asset name. Name is a mandatory field for the entry to pass validation. If a name is not specified the process will use the Host field value as the asset name.
- Type: is the asset type from the space asset types list.
- Host: is the asset field as populated in the uploaded. file
- Tags: displays the list of tags, if any, that were assigned to this asset in the uploaded file.
- Message: Error message generated by the validation process will appear in this column.
- Actions: use the Actions expansion arrow to show extended details about each entry.

The View Import page is needed to review, validate or approve assets prior to their creation. When you are ready to further process the import:

If all asset states are Draft, then you can use Actions menu to Start Validation or Start Import. The Start Validation option will begin a process to validate each of the assets in this upload. You can use the Refresh button to monitor this process until it completes. The Import Statistics will update to reflect the total number of objects validated which can be used to determine when the operation is finished. If you choose Start Import at this stage, validation will be skipped.

Once the validation process is complete, each entry's State will either be updated to Validated or Error. A Validated state indicates that no errors were detected in the validation process and this entry is ready for import. An Error state indicates that an issue was found with this entry and you should review both the entry itself and any message that appears in the Message column. Use this Message to resolve the issue in the CSV file and begin the process again, as a new upload, to validate the results.

If you do not wish to redo the process, you can use the Actions > Clear Errors option to remove these Error entries from the list and to remove them from future validation and import operations.

And finally, if the entries are validated and you wish to proceed with the asset creation, you can use the Actions > Start Import option. You can use the Refresh button to monitor this process until it completes. The Import Statistics will update to reflect the total number of objects imported which can be used to determine when the operation is finished. When the import operation does complete, each entry should display Imported in the State column.

You can now navigate into your import container using the link from the Container parameter in the header to confirm the asset creation.

Periodic Imports

Periodic (scheduled) imports are available on some import operations that will allow for a reoccurring import of new assets. When an initial Import operation is created, the Periodic schedule can be assigned (i.e. Once a month, every Sunday, etc.)

Periodic imports do not update or delete existing assets from a previous completed import of this operation. Only new assets are created when found in a subsequent periodic import operation.

For those Import operations that support Periodic imports, the following parameters are used for the configuration:

Trigger: Set the parameter to Periodic to configure a periodic import schedule. Setting it to Once will perform a one-time Import operation.
Schedule: Define your periodic import schedule using the Schedule Builder button to create a Schedule Expression. Use the Select button to confirm your schedule.

Note

If the initial Import operation is created using either the None or Start Validation setting of the Action After Upload parameter, new assets from periodic imports will only appear in the staging area. Only Start Import will automatically create assets in the Asset Database during initial and periodic import operations.