Attachment actions

Use the different logic block attachment actions to manipulate attachments on and between records. 

Loop Attachment

Use the Loop Attachment action to loop over the attachments on a given record. This enables you to add logic to process the attachments on the record, such as adding conditional logic that checks for a specific attachment. 

Add Attachment

Use the Add Attachment action to add an attachment to a target record. This enables you to rename an attachment on a record, or to copy an attachment from one record to another record. 

Delete Attachment

The Delete Attachment action allows you to delete a specific attachment, or all attachments, on a given record. 

Example

For example, you could:

  • Loop attachments on a given record to a specific attachment. 
  • Add the attachment back to your record with a new name. 
  • Delete the attachment with the old name. 

Copy Attachments action

The Copy Attachments action allows you to copy all attachments from one business record to another.

To configure the Copy Attachments, you must include a unique data source name from the originating business data source, as well as the business data record to which they are being copied. 

When the Copy Attachments action runs, all attachments associated with a business record are included. Attachments must exist in the source record. If there are no attachments, the logic block can run successfully, but no attachments are copied and there will not be a notification message. 

Apply Styles action

Use the Apply Styles action to apply a style definition to elements in your application. Style definitions change or conditionally change the UI elements of fields.

In the Apply Styles action, enter the name of the application, the field you want to style, and the style definition you want applied. You can select a prebuilt definition or create your own. To view or create a style definition, navigate to the Style Definition application. 

Each style definition designates what changes should be applied to the specified field. For example, the definition could highlight, change the font color, or mark a field as required. Use conditional logic to control when the style is applied. For example, the style definition could be applied when a value changes, is selected, or exceeds a certain amount. 

Learn more in Style definitions and Style Definitions application topic.

Run Model Definition action

 Use the Run Model Definition action to initiate a model created in the Model and Prompt Definitions application. 

Output

The Output Data Source is shaped by the outputs of your Model Definition record. The values populated are dictated by the type of model definition being run, such as: 

  • Automated Machine Learning and Anomaly Detection—Populates the prediction fields for your Automated Machine Learning or Anomaly Detection definitions. 
  • Prompt Definitions—Populates the fields defined on the Output Definitions page of your prompt definition. The output is the response from the LLM. 

Provide a unique name for the output so that it can be referenced in other logic block actions. 

Input

The Input Mappings are dictated by the type of model definition being run, such as:

  • Automated Machine Learning and Anomaly Detection—Specify an entire record as the input to provide meaningful data for the machine learning. 
  • Prompt Definition—Specify either an entire record or individual fields as inputs. The input is how you insert values into your prompt definition.