Understanding attributes
  • 12 May 2021
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Understanding attributes

  • Dark
    Light
  • PDF

This article explains Lightico Attributes and describes when to use the different types of attributes.

About attributes

Using Lightico Attributes, you can store customer information throughout a session. For example, you can create an attribute called phone_number to store the phone number of the customer. If customers are required to enter their phone number multiple times throughout a session, you can bind all the phone number fields in that session to the phone_number attribute. 

This way, customers only have to enter their number once during the session and all subsequent phone number fields in the session are automatically populated with the same information. The information from the attribute appears in the relevant places inside the final document.

Furthermore, If you are integrated with a CRM or other software platforms that store customer data, you can map the attributes to the relevant fields in your integrated platform. In this case, the phone number could be pulled directly from the integrated platform and the customer would not have to enter it at all. You can also set up your integration to be bi-directional so that if the customer updates information during a session, the associated field is updated in the integrated platform.

Dataset attributes

You can also build more complex attributes based on datasets, where each value is associated with different properties. For example, you can build a dropdown attribute containing a few different subscription plans. For each plan you can associate different properties such as the price of the plan and number of licensed users. You can then use these properties to build conditions into your workflow.

Attributes in workflows

Attributes are also the core building blocks of Lightico automation workflows. Inside a workflow, you can build multiple conditions based on these attributes. For example, you can choose to show customers a payment form only if the customer_age attribute is greater than 18 or use a customer_address attribute to show certain legal terms and conditions based on the state in which the customer lives.

Types of attributes and when to use them

There are 2 types of attribute entities:

Depending on the entity type and the field type, some attributes can be used in documents, some attributes can be used in workflows, and some can be used in both. The following table describes which attributes can be used where.

Field Type (Entity Type)Use in documentUse in workflow
Text (Document)
Drop Down List (Document)
Drop Down List (Data Source)
Digits (Document)
Date (Document)
Function (Document)
Radio Button Group (Document)
Radio Button Group (Data Source)
Checkbox group (Document)
Checkbox group (Data Source)
Signature Date (Document)
Boolean (Document)

Create Attributes

For information about creating basic attributes for use inside a template based document or workflow, see Create basic attributes.

For information about creating dataset attributes for use inside a workflow, see Create dataset attributes.



Was this article helpful?