We're happy to announce that the latest major Anaplan release is now available. If you're an ALM user, check out the Comparison Report to analyse the structural differences between target and source models. You can now set a series color for a data item (such as a product line or region) and then apply that color to the series.
This release includes a number of important performance improvements.
Exports - reduced blocking
We've listened to your feedback and we've made improvements to the behavior of exports. Now, while an export is running, all users can navigate around the model in a read-only state. You'll also notice that you're blocked for a significantly shorter time during large and long-running exports.
Viewing Change History for Cells and Ranges
Retrieving the change history for individual cells and cell ranges is now more efficient. As a result, the process is less likely to timeout when working with large models containing many changes.
Because a new index must be initialized for each model, the process may still timeout the first time you view cell history. If this happens, please try again.
We're introducing the ability to use a revision tag as the basis for a new model. Models created from a revision contain the same structural information as the source revision tag but no production data. Think of these models as templates. Use this feature to:
Create a test model from any past revision to your development model
Create a production model from the latest revision to your development or test model
Migrate existing models to Application Lifecycle Management (ALM)
Models created in this way are structurally compatible, so changes can be promoted using Compare & Synchronize.
We've added a new Create Model From Revision button to the Revision Tags screen:
When you create a model from a revision, the new model is created in the workspace you're currently working in. Once created, you can import the model into a development, test, or production workspace.
Mark import data source (IDS) definitions and their associated imports as production data in a similar way to production lists. Once synced to your production model, you can then configure these "production" IDS definitions and imports in deployed mode. For example, you can change the source file or object for an IDS definition, or change an import's mappings.
Newly created "production" IDS definitions and imports can be synced from a source to a target model; from your development to your production model for example. After the initial sync, only renamed or deleted IDS definitions or imports are included in a sync.
Two new tabs have been added to Actions - Imports and Import Data Sources - providing a new, central location to configure all imports and IDS definitions on any given model.
Use the options on these tabs to configure "production" IDS definitions and imports in deployed mode.
Revision tags and related actions will be visible in the change history of a model.
A new entry is created in the History whenever you:
add a revision tag
copy a model
import a model
create a model from a revision tag
synchronize changes to or from a model
To view the change history for a model, go to Settings > History, select a time period, and then click Show History. Revision tags and related actions are listed together with model changes, in chronological order, but don't have a change ID.
You can't restore a model to a previous revision tag or related action using the Restore to ID feature.
Revert a model back to the most recent revision tag, discarding any structural changes not yet captured in a revision tag. Production data, such as the contents of production lists, is not affected.
This feature is useful if you've inadvertently disabled deployed mode in a production model and then made structural changes. In this situation, reverting back to the most recent revision tag prevents the production model from becoming incompatible with its sync source models (such as development models).
You'll notice a new Revert to Last Revision button on the Revision Tags screen:
Thebutton is available when at least one structural change has been made since the most recent revision tag.
We're introducing a number of improvements to chart functionality, including the ability to change the color representing a series on most kinds of chart.
The color for an individual series on a chart on a dashboard can be overwritten to create a consistent view of data items across a number of dashboards. You can select a color for a data item (such as a product line or region) and then apply that color to the series representing it in each dashboard containing relevant data. When a number of dashboards are viewed together, it's easy to track the information relating to that data item.
This functionality does not apply when generating charts. You can't set a series color for Timeline, Map, or Funnel charts.
When Chart Options for a chart on a dashboard are displayed, click the colored box next to the chart type to display the color selector. A dot displays in the center of the color that is currently selected.
To see the effect of changing the series color, hover on the colors on the palette to update the series and legend on the chart. Choose a color then click Update Dashboard.
Series color on Waterfall charts
To expand the flexibility of Waterfall charts, administrators can now select the colors used to display the increment, decrement, and totals values.
The default colors are green for an increment, red for a decrement, and blue for totals. However, these colors are not always suitable where a waterfall chart is being used to explain movement in, say, costs. If a decrease in costs is a positive outcome, displaying that decrease in red is not appropriate.
In the Data section of Chart Options, choose the colors for Increment, Decrement and Total values. Click the colored box next to the series name and choose a color from the palette displayed.
Click Publish to Dashboard or Update Dashboard to apply the change.
A number of improvements have been made to the layout of charts.
Negative values on Y-axis
Where the values selected for charting have a value greater than zero, the Y-axis on a chart will start at zero, and not a minus value.
Available in 2017.3
No negative values are displayed on the Y-axis when very small positive values are part of the data being charted for Line or Combination charts.
Excess white space on charts
For improved presentation and readability, excess white space at the top of charts has been reduced.
Available in 2017.3
Order of grouped items on Bar chart
To make the display and analysis of your data more intuitive, the order of bars on a bar chart is reversed, matching the order in which they were selected in the grid.
Previously, data items were displayed from the bottom of the grouping to the top, in the order they were selected or sorted. Now, the order is reversed - the first data item is displayed as the top bar and the last data item as the bottom bar. The first data item in the legend is the item at the top of the grouping.
In this example, Lease Revenue was displayed as the bottom bar in the group.
From 2017.3, when the same data is selected, Lease Revenue is displayed as the top bar in the group.
Available in 2017.3
This change is retrospective. The order of the bars on existing bar charts will be changed automatically. Check existing charts to ensure that any sorting still displays the data in the way you intended.
Disabling a legend item
It’s now possible to re-enable a legend item in a chart that was previously disabled and have that data item displayed on the chart. Previously, re-enabling the legend item and saving the dashboard didn’t work as expected.
Change to size of legend
The color representing a series is now displayed as a box in the legend of a chart (rather than a rectangle). This makes the legend more concise.
Browser tab now displays the model name
We're making it much easier to identify which browser tab a particular model is open in. The name of the open model is now displayed as the title of the browser tab.
Select Items to Show
New functionality allows you to hide or show line items on a module or dashboard grid via a dialog. This reduces the number of clicks and greatly improves the speed with which you can select the items you want to see.
The Select Items to Show menu option is available on the:
grid element menu
right-click context menu
Each line item is treated independently.
Select Items to show applies to line items, Time, and Versions. When Select Items to show is selected, the Select Items dialog is displayed.
Select Items to show is not available in Blueprint mode. The Select Items to show dialog is available if the view of the data displays less than 4000 items. Where the number of items exceeds 4000, filter the view to reduce it to less than 4000 items.
In this release we've made improvements to the LAG and LEAD time functions by adding a new, optional "STRICT" parameter.
LAG and LEAD take an offset that can be a line item or the result of an expression as a second parameter. For LAG, a positive offset represents the number of periods back; for LEAD it represents the number of periods forward.
The third parameter of LAG and LEAD represents a "fill" value. This can also be a line item or the result of an expression.
As the offset parameter can contain both values that are positive and also values that are negative, each period depends on all other periods of the source line item. This means that certain sequences of calculations that use variable lags or variable leads (which should not be circular) are treated as circular by the engine and rejected.
The new, optional fourth parameter, "STRICT" now allows you to define whether all non-positive values of the offset parameter be ignored and the corresponding fill value used. In this case, LAG will depend on all previous periods, and LEAD will depend on all following periods.
The optional mode values are:
NONSTRICT (default) allows positive, negative and zero values for n.
SEMISTRICT ignores negative values for n and uses the overflow value.
STRICT ignores zero and negative values for n and uses the overflow value. STRICT mode limits the x value to a line item.