Once the attributes are defined, they can be executed through a job. The job can be run from either the Attribute List or the Attribute Builder page. This article will cover the following topics:
- Executing Attribute group(s) from the Attribute List screen.
- Executing an Attribute Group from the Attribute Builder screen.
- A note for the Legacy client using Audience (versions prior to 8.0.0)
Before diving into the job execution process, there are a few important points to consider:
- When you create an attribute under a data layer for the first time, an attribute app is automatically created in the backend with the name <data_layer_name>-AttributeBuilder. For example, if the data layer name is OnlineStreaming, the app will be named OnlineStreaming-AttributeBuilder.
- Jobs executed from the Attribute List or Attribute Builder are considered ad-hoc jobs, as they do not need to be manually saved.
- When you run an ad-hoc job for the first time (from the Attribute List or Attribute Builder), a job named Attribute-Run is automatically created under the app where the execution occurs. Subsequent executions will use the same job but with a different execution ID. The execution details and history of ad-hoc jobs can be viewed on the Operations screen.
- Ad-hoc job execution cannot be scheduled or configured. If a job needs to be scheduled, you can create a new job from the Operations screen and save it with a custom name. Only manually created jobs can be scheduled.
- Additionally, ad-hoc job execution does not include the 'Drop & Replace' process mode as a safety precaution.
- When an ad-hoc job (i.e., Attribute-Run) is already running, no other attribute under the same data layer can be executed until the first job execution is completed.
Executing Attribute Group(s) from the Attribute List Page
You can execute attribute group(s) from the Attribute List page by following these steps:
- In the Attribute Groups list, select the desired attribute group(s) by checking their checkboxes.
- Click the 'Execute' button. This will open the Execute Attribute(s) pop-up window, which displays the selected groups as steps.
- Enter the job execution details, such as the execution date Range, Process Mode, Runtime Template, etc.
- Click the Execute button.
This will start the job execution. The details of the running job can be viewed by clicking on the 'Activity' icon displayed next to the '+' icon. The 'Activity' screen can be also accessed from the Attribute Builder screen.
When the group is unchecked, the activity screen will disappear, but the job will continue running in the background.
If an ad-hoc job is already running and the user selects additional attribute group(s), the 'Execute' button will be disabled, as only one job can run at a time.
Executing Attribute Group From the Attribute Builder Page
You can execute an attribute group from the Attribute Builder page by following these steps:
- Go to the Attribute Group List.
- Click the 'Pencil' icon to navigate to the Attribute Builder page.
- Click the Run button. This will open the Execute <attribute_group_name> pop-up window with the selected groups displayed as steps.
- Enter the job execution details, such as the Date Range, Process Mode, Runtime Template, etc.
- Click the Execute button.
This will start the job execution. Once the job begins, an activity icon will display a count of one, indicating that a job is in progress. The Run button will remain disabled until the job finishes, as only one ad-hoc job can be executed at a time.
Manual Job Creation and Scheduling Jobs
If you want to create, save, and schedule a job, this can be done from the Operations screen. For more details, refer to the Operations-Audiences article.
Note for Legacy Clients
Legacy clients using Audience (versions prior to 8.0.0) may encounter a scenario where the checkboxes for certain attribute groups appear disabled after selecting one or more attribute groups. This occurs because the disabled attributes are not part of the same app as the selected attribute group(s). Only attributes belonging to the same app can be selected and executed together in a single job.