---
title: "Auditing Shared Actions usage in JMWE (Data Center)"
canonical: "https://support.appfire.com/space/SUPPORT/3450994815/Auditing%20Shared%20Actions%20usage%20in%20JMWE%20(Data%20Center)"
format: markdown
---
### Summary

This article covers two scenarios for auditing the usage of Shared Actions (as post-functions that are part of them) in Jira Misc Workflow Extensions (JMWE) for Data Center. It provides methods for modern versions (v8.7.x and above) using the built-in UI and SQL queries as alternatives to retrieve logged data.

---

### Option 1: Auditing usage in modern JMWE versions (v8.7.x and above)

In newer versions of JMWE, the app includes a built-in **Extension Logs** feature that tracks the execution of shared actions and post-functions.

#### Solution: Using the JMWE UI

1. Navigate to **Administration > Manage Apps > JMWE > Extension Logs**
2. When a Shared Action is executed, the entry is stored here
3. You can filter and search only for Shared Action executions to verify recent activity

**Note on log retention:**  
The main JMWE Configuration page governs the number** **of logs stored under the **Logs storage** section. By default, it stores the last *15* ***recent*** logs and *10* ***error ***logs for each workflow extension. If an action hasn't been used recently enough to stay within these limits, it can not appear in the UI.

---

### Option 2: Auditing usage using SQL queries (for version 8.7.x and above supporting AO tables)

If your version is modern enough to have the Active Objects tables but you prefer direct database access, use the following PostgreSQL queries.

**Step 1: Find the Shared Action ID by name**

```sql
SELECT "ID", "DESCRIPTION" FROM "AO_7AEB56_SHARED_ACTION"
WHERE "NAME"='MyAction';
```

*(Replace *`MyAction`* with your shared action name. Note the ID returned, e.g., *`f0113e23-76b8-422a-aaa4-51e3513fe75b`*)*

**Step 2: Find all logs associated with the Shared Action**

(Replace the Shared Action ID with the ID from the previous step)

```sql
SELECT * FROM "AO_7AEB56_EXECUTION_LOG"
WHERE jsonb_path_exists("EXECUTION_LOCATION"::jsonb, '$[*] ? (@.args."shared-action-id" == "f0113e23-76b8-422a-aaa4-51e3513fe75b")');
```

**Step 3: Find logs for post-functions within a Shared Action**

(Replace the Shared Action ID with the ID used in the previous step)

```sql
SELECT * FROM "AO_7AEB56_EXECUTION_LOG"
WHERE jsonb_path_exists("EXECUTION_LOCATION"::jsonb, '$[*] ? (@.args.ContainParentSharedAction == "f0113e23-76b8-422a-aaa4-51e3513fe75b")');
```

---

### <u>Notes</u>:

- Legacy versions like v7.0.3 do not have the "Extension Logs" UI and do not use the modern `AO_7AEB56_EXECUTION_LOG` table.

- **Absence of logs:** If no logs are found in the database or UI, it typically means the action has not been triggered within the retention window or the associated workflow transition is no longer in use.
- Information about JMWE log storage/retention can be found by visiting: [https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461602981/JMWE+Configuration#Logs-storage](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461602981/JMWE+Configuration#Logs-storage)