Create Asset activity - Precisely Data Integrity Suite

Before you configure the activity, create or identify an asset type that contains the fields that you want to set, such as name, description, PII, or CDE. If the asset will be created from request form inputs, create a Request Type that is allocated to that asset type and add the required fields to the request form.

• Asset Type ID: Specify the asset type that the activity creates. You can use the asset type ID from the workflow trigger after the trigger is configured, or paste a specific asset type ID.
• Asset Properties: Add one property row for each field that you want to set on the new asset. The Key value is the field API name, not the display name. The activity does not currently provide a dropdown list of fields from the selected asset type, so you must know the API name for each field that you want to set.
• Value: Enter a hard-coded value, or click + to select an available variable, such as a request form response variable.

The activity does not validate values against the target field type while you configure the workflow. For example, you can enter text in a Boolean field value. If the catalog API rejects the value when the workflow runs, the activity fails.

After the Create Asset activity executes successfully, the following outputs are available for use in downstream workflow activities:

• Asset ID: The unique identifier of the newly created asset.
• Asset Name: The name of the newly created asset.

The Create Asset activity currently works best with simple field values:

• Text fields, such as name and description.
• Boolean fields, such as PII and CDE.
• List or multi-select fields when the value comes from a form variable, including fields with multiple selected values. If a form field has changed from single-select to multi-select, check that the variable does not still reference a single array index, such as [0].
• A single hard-coded object ID.

• You cannot use the Create Asset activity if the workflow trigger type is set to Schedule.
• If an asset type has no required properties defined, the Create Asset activity will not run.
• Assets created by this activity will show the creator as "system" rather than the user who initiated the workflow.
• The Key field is the target field API name. It is not the field display name.
• The activity does not currently provide a field dropdown based on the asset type ID.
• The activity does not validate field values while you configure the workflow.
• When the activity fails, workflow history shows a generic service error. More detailed catalog response information is available only in internal logs.
• The activity completes or fails as a single workflow step. Unlike the Make API Call activity, it does not expose a status code that can be used for fail routing or conditional branching.
• Hard-coded multi-select arrays are not currently supported. A single hard-coded object ID works, and a multi-select value from a form variable works.
• Link fields are not currently supported. Catalog link values require a piped format, such as name|url, but the workflow UI requires the value to start with http or https.
• Relationship fields and relation lookups are not currently supported. The related asset must exist before the new asset can be created.

The Create Asset activity is simpler than the Make API Call activity because you do not need to configure authentication, build the full JSON request body, or handle a status code. Use it for simple assets that use text fields, Boolean fields, a single value, or list values from a form.

Use the Make API Call activity when you need full control over the JSON body or response handling, such as for hard-coded multi-select arrays, link fields, or relationships.

Summary: A data steward submits a request to create a new asset. The request form collects values such as name, description, PII, CDE, and list selections. The workflow uses those form values to create the asset and can optionally send an email notification when the asset has been created.

1. Step 1: Configure the target asset type:
   1. Create or identify the asset type that the workflow will create.
   2. Add the fields that the workflow should set, such as Name, Description, PII, or CDE.
   3. Record the field API names for the fields that the Create Asset activity will set.
2. Step 2: Configure the Request Type:
   1. Create a Request Type that is allocated to the asset type.
   2. Add request form fields for the values that users must provide when they request a new asset.
3. Step 3: Build the workflow:
   1. Create a workflow with the Trigger Type set to Make a Request.
   2. Select the Request Type that you configured.
   3. Add a Form activity if the workflow needs to collect or confirm additional values after the request is submitted.
   4. Add a Create Asset activity before the End activity.
   5. Optionally, add a Send Email activity after the Create Asset activity.
4. Step 4: Configure the Create Asset activity:
   1. Set Asset Type ID to the asset type ID from the trigger, or paste a specific asset type ID.
   2. For each field that the workflow should set, add one property row.
   3. In Key, enter the field API name.
   4. In Value, click + and select the variable for the corresponding request form response, or enter a supported hard-coded value.
   5. If a list field uses a multi-select form value, confirm that the variable returns the full value instead of a single indexed item such as [0].
5. Step 5: Test the workflow:
   1. Click Make a Request and select the Request Type.
   2. Complete the request form and submit it.
   3. Confirm that the workflow runs the Create Asset activity and creates the asset with the expected field values.
   4. If the activity fails with a service error, check that each key is a field API name and that each value matches the format expected by the target field type.