Actions and Processes executed via web UI to return taskId's

Currently, it is intended that actions and processes executed via the API return taskId's visible in the /tasks/ endpoint. These same tasks when executed via the web UI are not intended to return a taskId, resulting in different levels of detail returned by the API depending on the method of execution.

We propose that all Processes and Actions, regardless of the method used to execute them, should return a taskId that can be seen in the /tasks/ endpoint.

This would positively impact users, as it would provide consistency and they could expect the same level of detailed returned by the API across all situations.

Comments

Quick Links

New ideas

Keep row sub totals/totals when filtering a List/text formatted column in a combined grid
Now I can combine grids in the user interface, it would be useful to be able to retain any row totals and/or sub totals when I filter on a List or Text formatted column. In the example below, if I filter on Spread=Even, I lose the sub-totals for the numeric monthly data by Entity.
Enable Summary Method Ratio & Closing Balance in Polaris
Hello, We need the ability to apply both summary methods in the same line item in the Polaris engine as we do in the Classic engine as soon as possible, please! Thanks.
Combination Grid Enhancement - allow linkage of subsetted modules
Problem: Not able to combo modules within a Grid where you start with a module with a full list, then try to combo with a subsetted module of that same list. Example: When creating a Combo Grid with a Properties module (full list dimension) and a Calculation module (subset of the same list dimension), you are unable to…