Reviewing Applications Activity

Applications Activity Logs provide a tenant-scoped record of supported interactions in the Applications experience. The page combines KPI summaries, filters, a paginated event table, and an event-detail drawer.

Open Applications, select More, then Logs, or open https://<workspace>.raptix.app/applications/logs. The initial view is newest first and uses a server-side 30-day window. The page opens with Applications selected; use the Documents tab for document activity.

Before you start

• Confirm that your account is an administrator or can open the Applications More tools.
• Decide which user, resource, action, and time period you need to investigate.
• Treat this page as a record of supported UI events, not as a guarantee that every backend or security event is present. UI event recording is best effort.

Understand the page

The page contains four main areas:

1. Six KPI cards summarize the current filtered result.
2. Show Filters opens search, date, and targeted filter controls.
3. The activity table shows 50 events per page.
4. Details opens the full available context for one event.

Currently recognized Applications action labels include:

Runnable form views can also appear with the form.view action key.

Review and sort events

Each table row shows:

• time;
• user and email;
• action;
• outcome;
• resource type and resource name;
• parent resource; and
• a Details action.

The default sort is Time, descending. Select a sortable heading to sort by Time, Email, Action, Outcome, or Resource. Select the active heading again to reverse the direction. User and Parent are not sortable.

Use Previous and Next when the result spans more than one 50-row page. The footer shows the total result count and current page.

Inspect an event

1. Select Details on a row.
2. Review the human-readable fields first: action, outcome, time, actor, actor roles, resource, parent, and user agent.
3. Under System identifiers, use the action key, request ID, and resource ID when correlating an event with technical records.
4. Review Metadata when it is present.
5. Close the drawer with its close control, by selecting outside it, or by pressing Escape.

The drawer does not display a user IP address. Do not infer a user's network location from this page.

Export filtered activity

1. Apply the required filters and sort order.
2. Select Export.
3. Keep the page open while the button shows Exporting….

The CSV contains the full filtered result, not only the visible table page, up to 20,000 rows. It preserves the selected sort and includes:

• Time
• User
• Email
• Action
• Outcome
• Resource Type
• Resource
• Parent
• Action Key
• Request ID

If more than 20,000 rows match, RAPTIX exports the first 20,000 and displays a warning. Narrow the date range or other filters, then export again to obtain a complete bounded result.

Outcomes and audit limits

Rows can represent Success, Denied, or Error outcomes when those values exist in the stored activity data. The supported Applications UI logger records successful interactions on a best-effort basis; a missing row does not prove that an action was never attempted.

Activity rows cannot be edited or deleted from this interface. Available history depends on records retained for the current RAPTIX workspace.

Loading, empty, and error states

• Loading rows appear while the current page is fetched.
• No activity log entries found means nothing matches the current scope.
• An inverted date range displays a specific message; swap From and To.
• If the page cannot load results, use Try again. If the problem continues, verify connectivity and Applications access.
• If export fails, keep the filters in place and select Export again.

Troubleshooting

The log page is unavailable

Confirm that the account is an administrator or can open the Applications More tools. General permission to browse Applications is not enough to open Logs.

Expected events are missing

Check the active filter count, date range, action key, and actor email. Select Reset to return to the initial view, then add filters one at a time. Remember that supported UI event logging is best effort.

Builder events are hard to find

Open Show Filters and select the builder.open action key. The table displays those rows as Builder Opened.

The export warning reports 20,000 rows

The exported file is intentionally capped. Add an explicit date range and, if needed, export separate non-overlapping periods.