---
title: Application Triggers
slug: kronpam-reference-guide-3-9-0/application-triggers
description: Learn how to effectively use AAPM Triggers to update client application passwords in this comprehensive document. Discover step-by-step instructions on defining triggers, searching for relevant records, and configuring the AapmTriggerProcessJob in the Job
docTags: 
createdAt: 2022-07-31T14:08:41.000Z
---

One way to have client applications work with dynamically changed passwords is by restarting the client apps with the new passwords after an account password has been changed. Application triggers can be utilized for this purpose, as the Password Vault connects to the server running the client apps and restarts the apps with the new password.
To create application triggers:

1. Navigate to **Secrets  > Application Management.**
2. Open the **Application Triggers **tab.
3. Click on +**Add.**
4. Select the **Vault account** used to trigger a restart after the account password change.
5. Select the **Configuration.**
6. Select the target type as either **Single Device** or** Bulk.**
7. Select a device if you selected Single Device target type, or select the Device Group and the Element Type if Bulk target type is selected and click **Save.**

Each entry in the **Application Trigger** list expands to show its device and command details, including **Hostname**, **Configuration**, **Vault Account**, **Target Type**, **Device Name**, **Access Protocol**, **Element Type Name**, **Authentication Username**, and — for configurations that use one, such as the File strategy — **Command Template**.

:::hint{type="info"}
Fields in this expanded detail that hold a long or system-generated value, such as **Command Template**, show a copy icon on the left when you hover over them. Click the icon to copy the value to the clipboard; Kron PAM briefly displays a **Copied** confirmation message.
:::

According to the rule in the **Application Trigger** definition, **Trigger Name**, **Vault Account**, and **Parameter Name** values cannot be defined with the same values multiple times.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/nOnfsiFj1qC-PA4c5iJOx_image.png" size="80" width="980" height="669" position="center" caption="Application Triggers" darkWidth="980" darkHeight="669" showCaption="true"}

When an account password changes and an Application Trigger is set off, a **Trigger Processes** record is created for each matching device, associated with the relevant **Application Trigger **definitions. 

To search for these process records, use the Trigger Processes tab:

1. Navigate to **Secrets > Application Management.**
2. Open the **Trigger Processes **tab.
3. Select the desired** Process**.
4. Click to** Continue.**

The **Trigger Process** table lists the following columns for each record:

| **Column**        | **Description**                                                                            |
| ----------------- | ------------------------------------------------------------------------------------------ |
| **Strategy**      | The configuration strategy the trigger uses, for example *Tenable Configuration*.          |
| **Target Device** | The device the trigger process ran against.                                                |
| **Creation Time** | The date and time Kron PAM created the process record.                                     |
| **Log**           | A short summary of the process result, for example an error message if the process failed. |
| **Instance Name** | The name of the application instance the trigger updated.                                  |
| **Status**        | The process result, for example *Failed* or *Success*.                                     |
| **Actions**       | Available actions for the record.                                                          |

Click a row to expand it and view its **Start Time** and **End Time**.

:::hint{type="info"}
**Instance Name** and **Logs** appear only as table columns. Kron PAM doesn't repeat them in the expanded row detail, since they're already visible in the table.
:::

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/htsJMBT8PfL9_YyXqGriq_image.png "Trigger Processes")

The initial status of this process is **Waiting**. To trigger this process at a specific time, the **AapmTriggerProcessJob** job must be defined in the **Jobs Scheduler**:

1. Navigate **Administration** > **Jobs Scheduler**.
2. Open the **Trigger List** tab.
3. Select **AapmTriggerProcessJob** as the Job.
4. Fill in the **Trigger Name** and **Cron Expression** fields.
5. To enable the job, select **Enabled** for the **Active **field and click **Save**.

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/ulPGAlEBOPdq0nxjHk0fc_image.png "Saving an Trigger Processes Job")

:::hint{type="info"}
Regardless of how many** Triggers** are set, running only one **Trigger Process Job** is enough to run all triggers.
:::

To define the Application Trigger Strategy:

1. Navigate to **Secrets > Configuration**.
2. Open the** Application Configuration** tab.
3. Click the **Options** button to **Show Properties.**
4. Define the properties.