We'll prioritize ideas by vote count, so make your voice heard.
Vote and you'll get auto-updates on progress. 😎
This is test Desc from public roadmap
Apsona already computes a distinct count. A lookup field's Count metric returns the correct number of unique values, but only when the step's...
Currently, embedded reports displayed through a Visualforce page can be cut off, causing action buttons to be hidden from users. This limitation...
Revoking a DocGen license doesn't stop a Viewer-license user from creating and running merge actions — the merge buttons remain on the Salesforce...
To let a coordinator run an import or match routine, you must grant builder-tier access — which also lets them create/edit mappings and can break...
The Send Email and Snapshot buttons are always exposed on the dashboard header, with no way to keep a dashboard visible while turning these off for...
Once a chart or dashboard is shared, any non-admin can rename, edit, or trash it — including assets they don't own. Enforce creator-level...
Dashboards are org-wide today — every user sees the name and frame of every dashboard, even ones they shouldn't. MSRs already have folder...
Apsona calculated fields are currently processed client-side after report data is retrieved, so their calculated results cannot be used directly in...
User story As an Apsona Builder responsible for document generation, I want one workspace that shows a merge action together with its full dependency...
When configuring Apsona Merge Action buttons within Salesforce Flow, users currently cannot customize the button labels/names or fully control the...
In a Multi-Step Report (MSR), calculated fields can use JavaScript logic that references fields from specific steps. Currently, if a user renames a...
Currently, there is no option to turn off the email notification that gets sent to the running user when a Trigger Merge is run. It would be great to...
The addition of merge features to a Grid
We have a process where a User uses the mass update feature on a Grid multiple times in a row. This is needed in order to make sure data is properly...
Currently, Trigger Merge does not support passing Run Parameters. As a result, users cannot dynamically provide parameter values at runtime to...
I would like to be able do rearrange my calculated after creating them. A drag and drop feature would be very helpful.
Currently, Scheduler 2.0 sends job success and failure notifications only to the user who created the scheduled job. There is no option to specify one...
As a user, I want the Lookup fields in an Apsona Grid to respect the Lookup field filters that are built on the field in Salesforce so that we can...
Currently, merge actions invoked through Trigger Merge (Flow) do not support Multi-Step Reports (MSRs) as sublist reports. When users attempt this...