• Each user can now create their own Private App, or their own Private Views within an existing Public App.
• As an end user, to accelerate the process of creating a Private View, you have the option to duplicate any existing public (or private) view to a new private view. This can greately accelerate the creation ans setup of a new view. Of course, if you prefer, you can always create Folders / Dashboards / Views / Wizards from scratch.  

• Power users can now create / duplicate / delete Apps / Views / Folders & Pop-ups  directly from the main interface, when edit mode is on.
• As a power user,  it will facilitate the app management and creation process even more.

UX 2.4 allows data input via spreading. Spreading can be enabled / disabled individually on a View / Grid widget level. Advanced options  can also disable spreading or restrict the list of spreading methods available at the entire application level or per view.

Currently relative proportional spread is not supported and will be added in a future release.

The wizard design was optimized to better leverage the screen space with the most relevant content. The following changes / options were added :

1. Allow collapse and expand the StepBar and hide the steps descriptions (descriptions display in mouse-over popup in this mode)
2. Allow collapse and expand the SubStep SideBar and hide the sub-steps descriptions (descriptions display in mouse-over popup in this mode)
3. Removing unnecessary buffer space on the Application TitleBar , StepBar, AppBar , ToolBar & FilterBar
4. Next / Back & Cancel Buttons have a permanent fixed position
5. When all buttons are hidden (Next / Back / Cancel), the lower wizard border and frame is hidden entirely

The new collapsed StepBar and collapsed SubStep SideBar can be enabled by default when a wizard opens and can be toggled manually by users by clicking the chevron buttons illustrated in the screenshot below.

Tree Map is now available as a new chart type in the charts collection. You can apply the new chart on any data.  Tree Maps allow drilling to any level on the hierarchy in the row dimension. The elements on the columns as can be used as a filter for the chart.

UX 2.4 supports language localization. The selected language is not based on browser local setting but is selected by the user based on their preference and stored in the content store.

In this release localization of all internal object names for UX components has been localized. Extending localization to support application captions in different languages will be supported in the next release. (Note that this level of localization also requires the application builder (you!) to localize caption attributes on the application database.

We have redesigned the Mobile mode filter bar to allow user friendly selections. More space is also allocated on the page for widgets to display and analyze data.

you can now enable a new navigation button to allow quick return to the specific location. Can be used as back button between related pages.

The button can be enabled or disabled on a per screen basis in the page advanced options.

Previously processes could only be called via a button which launched a popup dialog to allow inspection and input of parameters.

In UX 2.4 the Process Widget also allows for parameters to be displayed directly. This can simplify workflows by eliminating the need for the popup and additional clicks.  

If the "Info" property of a widget contains text, this text is displayed via mouse hover (or single tap on mobile devices) of the info symbol in the widget title.

UX 2.4 now supports custom PickLists. That is, in addition to supporting TM1 defined PickLists you can define PickLists per Widget grid. Custom PickLists can be based on static lists, dimensions, subsets,  or MDX.

There are 3 possible advantages of UX custom PickLists over TM1 PickLists depending on the use case:

1. Can be applied differently per screen and not universally
2. The MDX can accept variables based on the setting service and so can easily be made dynamic or multi-stepped
3. Validation can be optionally enforced with the allowInvalid property (that is optionally values not in the PickList can also be accepted)