At mabl we believe that testing is a team sport that requires constant collaboration between QA professionals, developers, product managers, and other business stakeholders. To help keep everyone on the same page, use the activity feed to quickly review historical user activity across the workspace.
This article describes what you can do in the activity feed:
The workspace activity feed is located in Settings > Activity feed. Activity that isn't owned by any single workspace is recorded separately, in the company activity feed.
mabl API
In addition to reviewing workspace activity in the mabl app, you can also query workspace activity from the mabl API.
Filter workspace activity
Use activity feed filters to find specific events and review workspace activity. Combine the filters to focus on specific actions, such as flows created in the past two weeks or user activity for a given time period.
Tracked entities
The activity feed tracks create, update, and delete actions for the following workspace entities:
- application
- branch
- credentials
- database connection
- datatable
- environment
- file upload
- flow
- link agent
- link tunnel access
- permanent email address
- plan
- query
- resource group
- resource group assignment
- role grant
- snippet
- test
- user role
- workspace
For more information on recover actions, see the section on recovering deleted entities.
Event name
The activity feed supports searching by current and historical event names. For example, if a test was initially named "app - validate shipping calculator" and then renamed "checkout - validate shipping rates", you could search for either name in the activity feed and find all activity associated with the test.
Reusable flows and data-driven variables (parameters)
If you have a reusable flow that uses data-driven variables, it is best to use flow parameters instead of test-level variables and change the default flow parameter on a per-test basis as needed.
If the flow uses data-driven variables coming directly from the test, then any change to the default values of those variables in the test will result in a new flow version that will appear in the activity feed and in the change history for the flow. To avoid such unnecessary flow updates, it is best to use flow parameters.
You can use the filter controls to refine your activity feed view. When you apply a filter, the feed will update with the latest available information. The feed will also update when you navigate to it but will not update while you are viewing it.
In order to facilitate user collaboration, all users can view information in the workspace activity feed regardless of their role (e.g. viewer, editor, owner).
Recover deleted entities
Some deleted entities can be recovered using the workspace activity feed. Click on the restore icon to the right of the entity to recover it.
Recovering a deleted test
Requirements for recovering deleted entities
Only workspace owners can recover deleted entities. The entity must have been deleted less than 30 days ago and must be currently deleted.
The following types of entities can be recovered in the activity feed:
- file upload
- flow
- permanent email address
- plan
- resource group
- snippet
- test
Review company activity
Some resources belong to your company rather than to any single workspace. Changes to those resources are recorded in a separate activity feed on the account dashboard, which is available to workspace owners with account admin permissions.
To review company activity, expand the workspace dropdown in the top right corner of the mabl app and click on your company under Manage company. Then click Activity feed in the sidebar.
Tracked company entities
The company activity feed tracks the following changes:
- API keys created at the company level: when a key is created, changed, or revoked. Workspace API keys stay in that workspace's activity feed.
- SSO connections: when your connection is set up or reconfigured.
- Account admin changes: when someone is granted or loses the account admin role.
Activity on a resource that belongs to a workspace stays in that workspace's activity feed, so the company feed doesn't repeat workspace detail.