1. New Features
Adaptive Suite

2. New Features

3. Keyboard Shortcuts and Range Selection Improvements

4. Keyboard Shortcuts & Range Selection Improvements
Use Case This Feature Addresses: Users often need to select ranges of cells when working on sheets. The current functionality makes this more complex than necessary. This feature simplifies cell range selection and improves cell range selection performance. What It Does: This feature improves performance when selecting ranges and standardizes keyboard shortcuts that can be used for navigating and selecting ranges on sheets. What Parts of the Product It Impacts: Standard sheets. Cube sheets. Modeled sheets.

5. Keyboard Shortcuts & Range Selection Improvements
One click – easy access to all keyboard shortcuts on sheets

6. Improved Organization Administration

7. Improved Organization Admin
Use Case This Feature Addresses: This feature removes the Java applet dependency from the level admin page, allowing the page to render and be used quickly when there are large numbers of levels and/or many dimension and attribute values assigned to the organization hierarchy. It also provides scalable level drop-down on all sheet types and dimension drop-down on modeled and standard sheet types. What It Does: Delivers a scalable, performant UI for managing the organization hierarchy. What Parts of the Product It Impacts: Organization administration. Standard sheets. Cube sheets. Modeled sheets.

8. Improved Organization Admin
The rewritten Organization Admin page uses the same framework as the Dimension and Attribute admin pages from the last release (2014.2).
Java-applet free

9. Improved Organization Admin
Improved search – all results shown at the same time
This includes an improved search feature, where you can see all matching results at the same time, instead of having to hit “enter” to traverse the list, one keystroke at a time.

10. Improved Organization Admin
Includes level drop-down on all sheets…
In , we replaced the Level dropdown on all sheets with the new component.

11. Improved Organization Admin
And the dimension drop-down on standard and modeled sheets
We also updated the Dimension dropdown on Standard and Modeled sheets with the new component. The Dimension dropdown on Cube sheets is more complex, and is planned for replacement in the next release.

12. Enhanced Cube Sheets with Transaction Drill-Through

13. Enhanced Cube Sheets
Use Case This Feature Addresses: Allows GL and custom accounts to be associated with cube sheets. This means users perform data entry for these accounts directly on a cube sheet, and drill into transactions if there are any in the system. What It Does: Accounts flagged as "cube-entered" can be placed on a cube, where they behave just like a native cube account. Transactions can be imported and associated with a specific general ledger account. If that GL account is on a cube, its transactions can now be drilled into from the cube. Future releases will include functionality to fill out the feature. What Parts of the Product It Impacts: Account admin (GL and Custom) and cube account admin.
This feature also impacts the weighted-average option in Time and Level/Dimension Rollup property of cube-entered custom accounts and native cube accounts such that the "Weighted by" account must be either a cube-entered custom account or a native cube account, where all accounts involved (source and weighting) belong to the same cube.

14. Enhanced Cube Sheets
Optional flag on GL and custom accounts to indicate data entry source (standard or cube sheet)
For General Ledger and Custom accounts, a new option lets you indicate the sheet type that data entry/data manipulation for that account will occur. It’s one or the other, not both. However, a cube-entered account can be added to a Standard sheet for visibility.
This means such accounts can be placed directly on a cube, instead of having to create additional linked accounts, simplifying maintenance.

15. Add existing cube-entered accounts to the cube
Enhanced Cube Sheets
Although you add cube-entered GL and Custom accounts to a cube, the account details are still maintained in the source Manage your GL Account and Manage Your Custom Account pages.
Add existing cube-entered accounts to the cube

16. Transaction access from cube-entered GL accounts
Enhanced Cube Sheets
Transaction access from cube-entered GL accounts
For GL accounts, you can still associate transactions, which can be drilled to regardless of the sheet type (Standard or Cube).

17. Group Multi-Instance Refresh

18. Group Multi-Instance Refresh
Use Case This Feature Addresses: Linked instances currently need to be refreshed individually for every linked level. While this provides full control to the level owner on the parent instance over when and what data gets refreshed, it not very efficient when several linked instances and/or linked levels need to be refreshed at the same time. This feature provides a one-click ability to refresh all linked levels in an instance. This increases efficiency and speed when refreshing levels as well as reduces the risk that a linked level was overlooked and therefore accidentally not refreshed. What it Does: This feature provides the ability for a Level Administrator with Refresh Linked Levels permission to refresh all linked levels that the administrator has access to with a single action. This has following advantages: One-Click refresh for all instances instead of waiting for each refresh to complete; all refreshes occur around the same time; this eliminates likelihood of missing a linked level when refreshing many linked levels. What Parts of the Product it Impacts: Organization Admin

19. Group Multi-Instance Refresh
One click – easy access to all keyboard shortcuts on sheets

20. New Features

21. Journal Entry Numbering
Use Case This Feature Addresses: Journal entries are often expected to be numbered, similar to enterprise-level accounting software. This feature delivers the ability to have system-assigned or user-assigned numbers on journal entries, ensuring all numbers are unique in the model. What It Does: This feature provides the ability to ensure that all journal entries within the instance are uniquely numbered, optionally with gapless sequences. Each journal entry sub-version has an option to number entries manually, automatically, or not at all. What Parts of the Product It Impacts: Version Management (Consolidation users only), Journal Entry List page, Journal Entry page, Audit trail, and Printable view.

22. Journal Entry Numbering
Assigned at the Journal Entry sub-version
Automatic, Manual, or None
Numbering method, Starting number and Next number all exported in Printable View
Upgraded JE sub-versions set to “None”, can be change to Automatic or Manual.
No retroactive numbering on existing, un-numbered entries.
This feature provides the ability to ensure that all journal entries within the instance are uniquely numbered, optionally with gapless sequences. Each journal entry sub-version has an option to number entries manually, automatically, or not at all. This feature moves Consolidation forward with industry-standard functionality.

23. Journal Entry Numbering (Consolidation)
“Candidate” number shown to user during journal creation.
On Save, Journal Entry screen remains on the entry, allowing visibility to the actual number that was assigned. `

24. New Features

25. Flexible Scorecards

26. Flexible Scorecards
Use Case This Feature Addresses: This new dial type will enable customers to customize the data and layout of the scorecard. What It Does: A new dial type named as “Custom Scorecard” lets the customers choose the fields made available in the scorecard, and also provides the flexibility to display some of the most common data comparisons. The new dial type has 1-3 sections and the user can choose to display 1-7 fields in each section. Users can choose to display value (any version, any time), variance (between forecast and budget versions, between current year actuals and last year actuals), variance %, zone, trend, micro chart in any of the 7 fields. What Parts of the Product It Impacts: Visual Designer and edit-in-place (dial type menus)

27. Flexible data comparisons
Flexible Scorecards
Actuals to forecast
Current period vs. last period vs. last 2 periods
Period-to-date values
Choose micro chart type, column display order, and data/label formats
Flexible data comparisons
Flexible layout

28. Ability to Select Display Units in the Visual Designer

29. Ability to Select Display Units in the Visual Designer
Use Case This Feature Addresses: Enables the customer to customize the layout of the dial by selecting the units to display the data. What It Does: This feature lets users select the units for the data displayed in a dial. What Parts of the Product It Impacts: Visual Designer and editing-in-place (Data Settings Editor and Data Components Editor), and Data Designer (Metric Loader).

30. Ability to Select Display Units in the Visual Designer
Option to override the metric default
Expand
More intuitive unit selector

31. New Features

32. Adaptive Integration for Discovery Enterprise – Salesforce Data Source

33. Salesforce Data Source
Use Case This Feature Addresses: A pre-configured data source that will be able to bring all the data available within a Salesforce account. What It Does: This feature lets users with the data designer role create an instance of the pre-configured data source just by providing account credentials. The user can test the connection to Salesforce and get confirmation from the system. After configuring the data source, it operates just like any other data source in Adaptive Integration in that the user can selectively import data, apply transformation rules and map to Discovery Enterprise’s metric store. What Parts of the Product It Impacts: Data Designer

34. Salesforce Data Source
Configure connection to Salesforce
Test Connectivity, Import Structure, Import Data for all available tables
Import relationships between different tables
Merge with other data from other sources
Configure Data Source
Salesforce data source is an optional, pre-configured data source that will be made available to a customer of Discovery Enterprise. If a customer purchases this data source, they will be able to bring all data available from their salesforce user account. Salesforce data brought into Integration’s staging tables can be transformed and prepared before being used to load data into Discovery’s metric data store. Salesforce data can also be merged with data from other sources in the form of joins between staging tables.
Selective/Full Import
Visual data preparation

35. Adaptive Integration for Discovery Enterprise – Platform Enhancements

36. Integration Platform Enhancements
Use Case This Feature Addresses: Platform improvements across Adaptive Integration for manageability and debugging What It Does: Improvements to the Integration platform include the following – ability to have fine grained and real time visibility of integration tasks and loaders, enhanced debugging capabilities and new filtering capabilities for JDBC sources What Parts of the Product It Impacts: Data Designer

37. Platform Enhancements
Real-time view of Integration steps
Visibility into Integration tasks
Fine-grained (details by staging table, metric, dimension)
Real-time (streamed status messages)
Enhanced Execution History
Search easily through logs
Download logs for offline analyses
New filtering capabilities for JDBC
Period-based parameters
Filter records before import
Enhanced Execution History
Data designers can now benefit from the many platform enhancements available in Adaptive Integration.
When integration tasks and loaders run, they now show real time messages relating to each step in the integration process, from import to transform to load. And each step in turn provides information of the table or metric that is being affected. Additionally the progress bar has been enhanced to track the progress of import against each table.
The execution history UI has been enhanced to allow data designers to now search for specific errors within the log messages. Pagination has been improved to allow users to jump to a specific page or navigate back and forth between pages. And designers can now download all log messages into an excel file that can be used for offline analysis.
JDBC data sources can now be filtered by date-based parameters.

38. Adaptive Integration for Discovery Enterprise – Exchange Rate Tables in NetSuite

39. Exchange Rate Tables in NetSuite
Use Case This Feature Addresses: NetSuite customers can now bring over exchange rate information into Integration and to allow for currency conversion between values coming from different subsidiaries. What It Does: The NetSuite pre-configured data source now lets users import data into the Consolidated Exchange Rate table and Budget Exchange Rate table. These tables bring across Start and End Period Date columns, From Subsidiary ID, To Subsidiary ID, Current Conversion Rate, Average Conversion Rate and Historical Conversion Rate. What Parts of the Product It Impacts: Data Designer

40. Exchange Rate Tables for Currency Conversion
Budget Exchange Rate and Consolidated Exchange Rate tables available for import
Enable currency conversion between different currency rates
Convert values from one subsidiary to another
Exchange Rate Tables for Currency Conversion
Data designers can now benefit from the many platform enhancements available in Adaptive Integration.
When integration tasks and loaders run, they now show real time messages relating to each step in the integration process, from import to transform to load. And each step in turn provides information of the table or metric that is being affected. Additionally the progress bar has been enhanced to track the progress of import against each table.
The execution history UI has been enhanced to allow data designers to now search for specific errors within the log messages. Pagination has been improved to allow users to jump to a specific page or navigate back and forth between pages. And designers can now download all log messages into an excel file that can be used for offline analysis.
JDBC data sources can now be filtered by date-based parameters.

41. Thank You!