Summer20 Release Notes

Enhancements to Application Behavior

Reports

• The Apply/Remove POV option is moved from the File Cabinet toolbar to the toolbar of Dynamic Report, Report Collection, and Financial Package Publisher.

• When you apply a sort order and save the Dynamic Report, the sort order is retained in Dynamic Report, Report Collection, and Financial Package Publisher.

• You must redeploy Subline data report in Standard reports post this release.

Platform

• When you load Segment Hierarchy using a Data Load Rule, the order in which data is mentioned in the load file is retained.

Structured Planning: Workforce Planning User Interface Redesign

We had introduced a preview of the new and improved Workforce Planning as part of the Spring20 and June20 releases.

With this release, these enhancements are now available in the Production environment. Admin users can enable this feature directly from the Planful application (refer to the Enable New Workforce Planning UI section). Admin users can also enable the new user interface for end users and for the admin screen as well.

We suggest that you test this feature and familiarize yourself with the functionality in the Sandbox environment before you enable it in Production.

In continuation to the previous releases, we have made some enhancements in Workforce Planning to improve the overall experience of using the application. All the changes made to Workforce Planning in the Spring20, June20, and Summer20 releases have been listed here in detail.

Business Value

The new Workforce Planning user interface reduces the number of clicks while performing actions on the Employees page. The new interface is more user-friendly, and you can now directly make selections without having to navigate to different pages. The new UI enables you to quickly perform tasks, enables easy search, and provides an improved user experience, thereby enabling smooth business workflows.

Overview of the updates to WFP User Interface for Summer20:

• Ability to view allocations in graphical format

• Improved Employee and Employee Position deletion

• Bulk selection in roster to enable mass update and mass delete

• Flexible and improved search functionality

• Personalize the roster view

• Ability to add compensation items to roster

• Ability for Admin users to view and edit all scenarios

For detailed information on the enhancements for the new Workforce Planning UI, refer to the Detailed Workforce Planning Enhancements section.

Enable New Workforce Planning UI

We have made it extremely convenient for Admin users to enable the new UI. Only Admins can enable the new Workforce Planning UI for all users by following these steps:

1. Go to Maintenance > Workforce Planning module > Employees tab.

2. Turn ON the Enable New UI option to enable the enhanced Workforce Planning version, as shown in the following image.

   A confirmation message is displayed.

   

3. Click Ok.

   The new Workforce Planning UI has been enabled for all users including Admin users.

   Note:

   You cannot turn OFF the Enable New UI option to switch back to the classic Workforce Planning UI version.

Detailed Workforce Planning Enhancements (Employees page and Employees tab)

• All the updates made to the Workforce Planning template that have been listed in this section are applicable for the Roster view (Employees page for end users and the Employees tab for Admin users). The updates that are specific to just one of these screens have been clearly called out in the description.

You can access the Employees page by going to Maintenance > Planning Control Panel > Workforce Planning in Input mode.

You can access the Employees tab by going to Maintenance > Workforce > Workforce Planning Setup.

Improved Workforce Planning User Interface

• We have enhanced the Employees page and Employees tab to make it more user-friendly. The following images illustrate the new Roster view of the Employees page and Employees tab.

  Improved Employees page for end users

  

  Improved Employees tab for admin users

  

Enhanced Scenario Selection

• We have added a new Scenario selection list box. You can use this list box to select a scenario directly from the roster view.

  Scenario Selection on the Employees page for end usersScenario Selection on the Employees tab for admin users

  

Enhanced Budget Entity Selection

• We have added a new Budget Entity selection list box. You can use this list box to directly select one or more budget entities.

  Budget Entity Selection on the Employees page for end users

  

  Budget Entity Selection on the Employees page for admin users

  

Enhanced Search Functionality

• We have introduced the search functionality to make it easier for you to search for the required employee from the roster view.

• Type an employee name or employee number, or position description in the Search employees box and then press Enter. The Search feature displays the most relevant search results.

• You can customize the search by selecting the appropriate fields from the list box. You can select any number of fields from the list box, but for optimal experience we recommend that you select up to ten fields.

• The Employee Number, Employee Name, and Position Description fields are selected by default.

  Search functionality on the Employees page for end users

  

  Search functionality on the Employees tab for admin users

  

Improved More Menu

• We have moved all the options from the More menu to a new menu as shown in the following images. This modification improves the user experience and showcases better visibility on the page.

  More Menu on the Employees page for end users

  

  More Menu on the Employees tab for admin users

  

Update Employee Data

• You can double-click any field in the roster view to modify the selected field, as highlighted in the following image. This update is available for both end users and Admin users (Employees page and Employees tab).

  

Edit Employee Profile

• We have added a hyperlink to the Employee Number field. To edit an employee’s profile, click the employee number link of the required employee. This update is available for both end users and Admin users (Employees page and Employees tab).

  

Add a New Employee

• We have introduced the Add button to help you to quickly create an employee profile.

• We have also made minor enhancements to the Add Employee functionality to make it more user-friendly.

• All mandatory fields have asterisks marked next to the respective field names.

• We have also introduced the Customize Compensation list box. You can select compensation items from this list as displayed in the following image.

  

  Add button on the Employees page for end users

  

  Add button on the Employees tab for admin users

  

Delete Multiple Employees and Employee Positions

• We have improved the employee-deletion process. After you have selected one or more employees, click the Delete icon and select the Delete Employee(s) or Delete Position(s) option to delete the selected employee or employee position as shown in the following image.

  Delete Employee and Positions options on the Employees page for end users

  

  Delete Employee and Positions options on the Employees tab for end users

  

  Delete Employee example:

  For example, consider that you have selected the 2021 Budget scenario that consists of multiple employees. And you have selected Michelle Wright with the Senior Analyst position for deletion. Michelle Wright has multiple positions (Analyst, Senior Analyst, and Controller).

  When you select the Delete Employee(s) option, the selected employee and her respective position (Senior Analyst) are deleted from the scenario. In addition, all other positions associated with Michelle Wright are also removed from the scenario.

  Delete Position example:

  For example, consider that you have selected the 2021 Budget scenario that consists of multiple employees. And you have selected Michelle Wright with the Senior Analyst position for deletion. Michelle Wright has multiple positions (Analyst, Senior Analyst, and Controller).

  When you select the Delete Position(s) option, only the selected position (Senior Analyst) of the employee is deleted from the scenario. However, all other positions associated with Michelle Wright will still continue to remain in the scenario.

Improved Duplicate Functionality

• We have made the employee profile-duplication process better for your benefit. After you have selected one employee, click the Duplicate icon and specify the number of copies that you require. You can use the + and - buttons to increase or decrease the number of employee profile copies that you want to create. Then, click Duplicate to create one or more duplicate employee profiles.

• By default, the number of duplicate profiles to be created is set as 1.

• This update is available for both end users and Admin users (Employees page and Employees tab).

  Duplicate functionality on the Employees page for end users

  

  Duplicate functionality on the Employees page for admin users

  

Process Multiple Budget Entities

• We have improved the employee-processing functionality to automatically process multiple employees across multiple budget entities.

• Earlier, you could process only one budget entity at a time. Now, you can process multiple budget entities simultaneously.

  You can do so by clicking the Process list box > Current Budget Entities section, and then selecting either the All Employees or Unprocessed Employees option.

• This update is available for both end users and Admin users (Employees page and Employees tab).

  Process list box on the Employees page for end users

  

  Process list box on the Employees tab for admin users

  

View Employee Allocations in Graphical Format

• We have introduced graphs in the Allocations tab of the Employee Add and Employee Edit pages. The graphical representation of allocations is available for applications that have the Employee Allocations Method list box set as By Department on the Define Workforce Planning Budgeting Criteria page.

• You can click Show Graph on the Allocations tab to view the graphical representation of allocations for an employee.

  

• The graphical representation is available for scenarios including default scenarios.

• This update is available for both end users and Admin users (Employees page and Employees tab).

Ability to Select Multiple Records

• You can now select all records or individual employees on a page. You can also select all records on multiple pages by using the new master check box. The new master check box enables you to update multiple employees or delete multiple employees simultaneously. This enhancement helps you to save a considerable amount of time while performing these actions.

• You can use the Select Current Page option to select all employees on the current page. Alternatively, you can use the Select All Records option to select all employees in the selected budget entity or entities.

  Note:

  Employees who are in lock state will not be selected when you use the Select Current Page or Select All Records option.

• This update is available for both end users and Admin users (Employees page and Employees tab).

  

Ability to Personalize the Roster View

• We have added our existing personalization feature to the new Workforce Planning user interface. You can use the Settings icon to rearrange or hide columns as required. This customization then remains as your default view until you reset it.

• Admin users can use the Settings option to customize the Roster view (Employees page) for end users. The changes made by Admin users to the default scenario are applicable for all new scenarios, but not for the existing scenarios in the application.

• Admin users can also select existing scenarios and customize the Roster view (Employees page) for end users.

  Personalization on the Employees page for end users

  

  Personalization on the Employees tab for Admin users

  

Customize the Roster to Add Compensation Items

• Admin users can now add compensation items to the roster by using the new Customize Roster option. This option enables users to update compensations for multiple employees in the roster view. After compensations have been added to the roster, they are also added to the list of column names in the Settings options for personalization.

• After Admin users have added compensation items to the roster, end users can view and edit these compensations.

• The All Scenarios option in the Customize Roster window helps Admin users to add the selected compensation items to all scenarios in the application.

  Note:

  This update is available only for Admin users (Employees tab).

  

  

• The compensation items that are linked to the following Compensation Basis categories are available in the Customize Roster window for Admin users:

  • % of Wages

  • % of Wages with Annual Cap

  • Fixed Amount

  • Fixed Amount based on Employee Attribute

  • Fixed Amount per FTE

  • Rate X Hour

  • Tiers on Employee attribute - Value in % Wages

  • Tiers on Employee attribute - Value in % Wages with Annual Cap

  • Tiers on Employee attribute - Value in % Wages with Varying Annual Cap

  • Tiers on Employee attribute - Value in Hours per Period

  • Tiers on Employee attribute based on Rate X Hour with Cap

• For the compensation items to appear in the Customize Roster window, the following conditions must be met:

  • The Set as Global Constant check box must be cleared.

  • The Fixed & Equal for All Employees value criterion must be selected.

  • The Fixed & Different for Each Employee value criterion must be selected.

  • The Varies Annually & Equal for All Employees value criterion must be cleared.

  • The Varies Annually & Different for Each Employee value criterion must be cleared.

Ability for Admin Users to View and Edit All Scenarios in Workforce Setup

• Admin users can now view and edit the employee information of all scenarios for which they have access.

• Admin users can access the employee information of the required scenario on the Employee tab (Workforce Setup).

  

Additional Updates

The following updates are available for both end users and Admin users (Employees page and Employees tab):

• In the Employees roster view, when you select multiple budget entities from the Budget Entity selection list box, the Home Budget Entity and Position Budget Entityfields are empty in the Add Employee window or have no entity selected by default. This is to help users select the required entity in these fields when there are multiple budget entities selected.
  Note:

  If you have selected a single budget entity from the Budget Entity list box, the budget entity selected in the Budget Entity list box is also displayed in the Home Budget Entity and Position Budget Entity fields by default.

  Multiple budget entities have been selected in the following image.

  

  Because multiple budget entities have been selected, the Home Budget Entity and Position Budget Entity fields do not have any entity selected by default.

  

• The values in the Hire Date, Position Start, Position End fields are greyed out if they are beyond the specific date ranges. This is to ensure that users can only add dates in the Position Start field that are always greater than or equal to the corresponding dates in the Hire Date field. In addition, users can only add dates in the Position End field that are always greater than or equal to the corresponding dates in the Position Start field.

  An example of these combinations is illustrated in the following image.

  

• On the Report View pages, you can select multiple budget entities from the Budget Entity list box.

  

• We have made the following improvements to the All Noteswindow:

  • You can select multiple budget entities from the Budget Entitylist box.

    

  • You can use the Search box to search for an employee name, or employee number, or position description.

    

  • Click the content under the Notes column to view the entire note.

Limitations

• You cannot bookmark the Employees page for end users if you have selected multiple budget entities in the Budget Entity list box.

• You cannot load data to those compensation items that you have added to the roster from the Customize Roster window by using APIs and Data Load Rules.

• The Entity Workflow and Template Workflow options in the improved More menu are not available on the Employees tab for Admin users.

• While using the following Report views, we recommend that you select as few budget entities as you require:

  • Compensation Item View

  • Natural Account View

  • GL Account View

  • GL Account Detail View

    In future releases, we plan to extend this functionality to allow you to add a greater number of budget entities while using these report views.

Structured Planning: Enhanced the Refresh Closed Periods Process

We have improved the process to refresh closed periods data for Forecast and Plan scenarios.

Earlier, when you refreshed the data for closed periods for Forecast and Plan scenarios, the process was time-consuming. And when large quantities of data were involved during this process, it required you to remain on the page for a long time and wait for the success notification to appear. This notification used to be available on the Scenario List page for a limited amount of time and disappeared within a few seconds.

With this release, you can schedule the processing of refresh closed period data for Forecast and Plan scenarios. This processing occurs on the background (in the cloud).

We have enhanced the refresh closed periods data process to enable you to view the progress on the Cloud Scheduler and Detail View pages. The success notification that appears after the data is refreshed remains on the Scenario List page until you close the notification.

Business Value

The updated process to refresh closed period data for Forecast and Plan scenarios is time-saving, convenient, and allows users the flexibility to create tasks in Cloud Scheduler as necessary.

View the Status of the Data Refreshed for Closed Periods

The data for closed periods is refreshed in the cloud. To view the detailed status of this data, follow these steps:

1. Go to Maintenance > Admin > Scenario Setup.

   The Scenario List page appears.

2. On the Scenario List page, select the required Forecast or Plan type scenario.

3. Click the three vertical dots icon, and then select Refresh Closed Period Data.

   The scenario is submitted for refreshing closed period data.

4. A notification is displayed when the closed period data for the selected scenario is processed successfully.

5. Click the Click here link to view the detailed status of that scenario.

   The Detail View page appears with the time and status details of the scenario.

   

6. You will also receive an email notification indicating the status of the task submitted for refreshing closed period data.

Create a Task in Cloud Scheduler to Refresh Closed Period Data

1. Go to Maintenance > Admin > Cloud Scheduler, and then click the Process Flow tab.

2. Click the Add icon.

   The Add Process Flow page appears.

3. Click the General Information tab, and then add the appropriate details in the Code, Name, and E-mail Recipients fields.

   

4. Click the Tasks tab.

   

5. Click the Add icon.

   The New Task window appears.

6. From the Task Type list box, select the Refresh Closed Period Data task.

7. From the Scenario list box, select a scenario.

   The Task Name field is auto-populated with the name of the scenario that you selected. You can change the task name as required.

8. The Dependencies field is optional.

   Select the tasks that must be executed in sequence with the task you are creating. Dependency indicates that the new task cannot be started until the dependent tasks have been successfully completed. A dependent task is executed only if the task upon which it is dependent, has been successfully completed.

   If the task upon which it is dependent fails, the dependent task will not be executed.

   All tasks without dependencies are executed simultaneously.

9. In the E-Mail Recipients field, type your email address.

   An email notification is sent to this email address after the task has been completed.

10. Click Save.

    

11. Click the Scheduler tab, and then add the relevant details in the Start Date, Start Time, and Time Zone fields.

    

12. To repeat this task, select the Repeat check box and then specify the frequency of recurrence in the respective fields as shown in the following image.

    

13. Click Save & Schedule.

    The task has been created and scheduled for the specified time.

    Note:

    To refresh closed period data in the application, you can create one job (on the General Information tab) in an application.

    For more information on Cloud Scheduler, refer to the Cloud Scheduler section.

Reports: Sort is Now Retained in Dynamic Reports

Now, Dynamic Reports retains the sort order selected for a column on the grid. If you apply the Sort Ascending/Descending order to a column and save the Dynamic Report, the selected sort order is retained when you navigate to another page or login to the application the next time.

A new Default Sort Order option has been added to the Grid list box as shown in the image below.

The Default Sort Order option provides you the ability to sort the columns on the grid based on the member sequence selected while creating the Dynamic Report as shown in the image below.

The selected member sequence is displayed in the Dynamic Report when the Default Sort Order option is selected as shown in the image below.

Business Value

This functionality provides you the flexibility to save your sort preferences on a Dynamic Report and provides you the ease of viewing sorted data based on your preference every time you open the report. In addition, this functionality significantly saves time and reduces the effort previously required to sort the Dynamic Report every time you navigate to another page or login to the application.

Prior to this release, the sort order selected for a column was not retained even if you saved the Dynamic Report. You had to select the sort order every time you opened the Dynamic Report. The default sort order was displayed on the grid when you moved away from the Dynamic Report.

In Practice: Access the Default Sort Order Option

Go to Report > open a Dynamic Report > Grid list box > Default Sort Order.

For more information about the Sort functionality, refer to Reports and the File Cabinet.

The sort order is retained when you:

• Use the Dynamic Report in Report Collection and FPP.

• Copy or Save As a Dynamic Report.

• Share the Dynamic Report with another user.

• Insert a formula in the report.

When you share a Dynamic Report with sort order applied to a column and the other user does not have access to a Dimension member in the sorted column, the sort order is applied automatically to the next column. Additionally, if you have applied the sort order to the last column in the report and there is no column next to it, then the report will display the default sort order.

When you apply sort order to a column in a report, the position of rows with formulas is updated based on the sort order.

When you apply sort order to a Dynamic Commentary column, the sorting is performed based on the data available in the column.

Reports: Point of View Redesign

With this release, the Point of View (POV) functionality has been re-engineered to set a new paradigm in providing a seamless and hassle-free experience across Dynamic Reports, Report Collections, and Financial Package Publisher. Now, you have the ability to control the data displayed in an individual report by defining the POV settings once.

Business Value

Now, you have complete control over data at an individual report level by just defining the POV settings once; thereby drastically reducing the effort of updating the POV settings every time you run a report. This provides enhanced user experience and flexibility to view the required data quickly.

Enhancements

The redesign has been achieved through the following major enhancements:

• Apply/Remove POV Option Moved to Toolbar of Dynamic Report, Report Collection, and Financial Package Publisher

• POV is Now Retained

Apply/Remove POV Option Moved to Toolbar of Dynamic Report, Report Collection, and Financial Package Publisher

Now, the Apply/Remove POV option is available on the toolbar of a Dynamic Report, Report Collection, and Financial Package Publisher. This functionality is now enabled by default for all new and existing customers.

Previously, the Apply/Remove POV option was available on the toolbar of the File Cabinet page.

The image below displays the Apply/Remove POV option in the More list box of the Dynamic Report toolbar.

The image below displays the Apply/Remove POV option in the Report Collection toolbar.

The image below displays the Apply/Remove POV option in the Financial Package Publisher toolbar.

POV is Now Retained

Now, if you apply the Point of View (POV) setting to a dimension and save the report, the applied POV setting is retained when you navigate to another page or login to the application the next time. This functionality is now enabled by default for all new and existing customers.

When you open a shared report with POV settings defined by another user, the report is displayed with the applied POV setting.

The Apply/Remove POV setting on the report is retained:

• When you Save As or Copy a report.

• In a Dimension based report and reports with Substitution Variables on the Page axis.

For example, if you select Assets as POV for the Account Dimension, then the Dynamic Report will display data based on the POV setting as displayed in the image below.

The POV setting works based on the existing precedence rules in Report Collections and FPP.

In Report Collection, the selected bursting criteria and page members take precedence over the POV setting.

In FPP, the selected page members take precedence over the POV setting. For more information about precedence, refer to the Reports and the File Cabinet guide.

In Practice: Set up the POV Settings

1. Click the Point of View icon on the application home page toolbar or go to Maintenance > Reports > Point of View.

2. From the Reporting Area drop-down list, select the required Reporting Area. The dimensions for the selected Reporting Area are displayed.

3. In the Hierarchy pane, select dimension members for the required dimension.

4. Click Save.

For more information about the POV settings, refer to the Point of View guide.

Reports: New Email Notification Options for Dynamic Commentary

Now, two new options, Resolved Comment and Marked Task As Complete have been added under the Enable Email Notification for Dynamic Commentary section of the My Setting page. You will now receive email notifications for the Dynamic Commentary functionality whenever a comment is resolved or whenever a task is marked as complete. By default, these options are selected. You may clear these options if you do not want to receive notifications for these actions.

Business Value

With this enhancement, you can track resolved comments, completed tasks, and all other actions in the Dynamic Commentary functionality conveniently at the comfort of your inbox notifications. This enhancement significantly reduces the time required previously to view the resolved comments and completed tasks.

The image below displays the Resolved Comment and Marked Task As Complete check boxes.

In Practice: Configure Email Notifications for Dynamic Commentary

To configure email notifications for Dynamic Commentary, click your Profile Name, navigate to My Settings > General tab and then select or deselect the required check box under the Enable Email Notification for the Dynamic Commentary section.

The Resolved Comment and Marked Task As Complete email notifications are available for comments posted on Dynamic Reports, Spotlight Analyze, Reports (Web & XL), and Excel Based reports.

For more information about the Enable Email Notification for the Dynamic Commentary functionality, refer to the Getting Started guide.

You will receive resolved email notification when:

• A user other than the initiator of the comment thread resolves the comment.

• The comment is resolved from the comments window or from the Comments Manager page.

You will receive Mark as Completed email notification when the assignee of the task changes the status to Complete.

If you change the status of a task from marked as complete to not completed, an email notification is not sent to the user.

Reports: Scorecard Reporting Area will not be Supported

With this release, the Scorecard Reporting Area is no longer supported in Dynamic Reports and Dashboards.

The deprecation of Scorecard Reporting Area will impact the following areas:

• While creating a new Dynamic Report/Report Set/Report Collection/Dashboard chart, the Scorecard Reporting Area option will not be available. Also, the Scorecard cube will not be created for new applications.

• Any existing reporting artifacts on Scorecard Reporting Area will not be displayed in the File Cabinet or Dashboards.

• Reports or charts from the Scorecard Reporting Area used in Report Collections, Financial Package, and Dashboard will be automatically removed.

• Any Substitution Variables or Custom Members created on the Scorecard Reporting Area will be removed from the application.

• The Scorecard Reporting Area option will not be available for Scenario and Dimension processing.

• User POVs defined on the Scorecard Reporting Area will be removed.

For more information, refer to Feature Deprecation - Scorecard Reporting Area.

Reports : Ability to Navigate to Comments Window from Task Manager

Now, you can directly navigate from the Task Manager page to the Comments Window where the task has been assigned to a user. This functionality provides flexibility to view comments on the fly and saves time by reducing the number of clicks.

Prior to this release, you could open only the corresponding report from the Task Manager page.

In Practice: Access the Comments Window from Task Manager

1. On the application home page, click the Task Manager icon. The Task Manager page is displayed.

2. From the TASK LOCATION column, click the required report hyperlink as shown in the image below.

   

   The corresponding comment is displayed in the report as shown below.

   

Reports: Enhancement to Comments Manager

We have made significant improvements to the Comments Manager page to enhance the overall page usability and to provide a rich user experience. The page now provides new User Interface labels that are closely aligned to the user actions performed on the page.

The following are the improvements made to the Comments Manager page:

• Ability to show, hide, and rearrange sequence of columns in the grid.

• New pane to display comment thread.

• Ability to refresh the Comments Manager page.

• New drop-down menu to display the selected filters from Selection Criteria.

• Ability to reset filters in Selection Criteria.

• User Interface enhancements in Selection Criteria, like improved spacing between fields and increased pane width.

• Ability to perform various actions, such as Highlight, Remove Highlight, and Delete using right click on the comment.

In Practice: Access the Comments Manager Page

Go to Maintenance > Admin > Comments Manager.

For more information on Comments Manager, click here.

Settings

A new Settings icon has been added to the toolbar that provides access to the new SHOW/HIDE COLUMNS drop-down list.

Now, you have the flexibility to show, hide, and re-arrange the columns in the Comments Manager page based on your requirements.

You can drag and drop a column to reorder in the SHOW/HIDE COLUMNS drop-down list. The column settings are retained when you navigate away from the Comments Manager page or sign out of the application.

Refresh

A new Refresh icon has been added to the toolbar. You can use this icon to reload the Comments Manager page.

Comment Thread Pane

Now, you have the flexibility to view a comment thread directly from the Comments Manager page. You can view all comments posted in a thread on the go while working in the Comments Manager page; thereby saving time and effort.

Prior to this release, you had to navigate to the corresponding report to view the Comment Thread window.

To open the Comment Thread pane, click the required row and the Comment Thread pane will be displayed on the page.

You can perform various actions, such as Resolve, Edit, Highlight, and Delete directly while you are on the Comments Manager page.

You cannot perform the following actions from the Comment Thread pane:

• Update the status of a task

• Mention a user

• Assign a task to a user

Reset

A new Reset button has been added to the Selection Criteria pane. Now, you can use the Reset button to remove existing data in all fields at once. When you click this button, default values are displayed in all fields. This new button significantly saves the time previously required to edit individual fields and provides the flexibility to update all fields on the go.

The image below displays the new Reset button.

View Selection Criteria Details using Drop-down Menu

A new drop-down menu has been added to the Comments Manager page. You can view the fields selected in the Selection Criteria pane by using this drop-down menu. This new menu greatly improves the usability of the Comments Manager page by allowing you to view the fields selected in the Selection Criteria pane on the fly; thereby saving the time and effort required previously to navigate to the Selection Criteria pane.

When you click the Arrow icon, a menu will be displayed as shown below.

Dynamic Planning: Ability to Export Reports to PDF in Spotlight

Now, you have the ability to export and print reports containing charts in Spotlight Web- Reports. A new Export list box has been added to the toolbar. The following new options are available:

• Export to PDF - Allows you to download a report in PDF format.

• Print - Allows you to print a report in the PDF format. All charts are printed at the end of the PDF file. Only one chart per page is displayed.

The new options provide ease of access and flexibility to perform the required actions with just the click of a button.

For more information about Spotlight - Reports, refer to Spotlight User Guide: Report Task.

The image below displays the new icon added to the toolbar.

The downloaded PDF will have the following default properties:

• Orientation - Portrait

• Paper Size - Letter

• Repeat Row & Column headers - Enabled

Limitations

• The following chart types are not supported when you export or download a report:

  • Pie of Pie

  • Bar of Pie

  • Bubble

  • 3-D bubble

  • Scatter

  • All Stacked linesv

  • 3-D linev

  • 3-D Area

  • 3-D Column

  • Spark lines

  • Histogram

  • Box and Whisker

  • Tree map

  • Sunburst

  • Surface

  • Combo charts

• When you have multiple tables on the worksheet, the Repeat row/column headers setting is not supported. 

Dynamic Planning: Writeback Map Enhancement

Dynamic Planning models have the ability to track the leaf level data which is changed. Changes to the data can happen from various sources like users changing the data from a view or report or users loading the data or users running a map or users loading the data. In all these cases the leaf level data is marked as dirty. Next time when users run an aggregation if change data tracking for a given model is enabled then the aggregation engine will only aggregate the data that has changed (i.e. data that needs to be aggregated vs. aggregating entire data).

With this release we are extending the same change data tracking functionality for writeback. When users run writeback maps the data will be moved from dynamic planning to structured planning based on map definition. With this enhancement instead of moving the entire data based on the map only the data that has changed will be moved from dynamic planning to structured planning. When users are working with large volumes of data and only few data records have changed then this approach will significantly improve the writeback map performance as its only moving the data that has changed.

In terms of tracking the data that’s changing, the writeback process will use the entire data block. Data block will be defined based on the key dimensions of the model and even one cell within the data block is changed that the entire block will be considered as changed. In the coming releases we are considering to further optimize the tracking and track individual cells vs. data blocks. Tracking the changes at the individual cell level will further optimize the writeback process. From a best practice we always recommend having one writeback map step in the calculation.

To enable this functionality please reach out to our customer support team. Once it's enabled for your tenant you need to enable change data tracking for the model and then run the writeback map. There is no change in the way users create a writeback map or they way users run the write back map.

Dynamic Planning: External Source Model Updates

For extensive information about External Source Models, click here.

New Folder Structure for External Source Model Maps

We now have folder structure functionality available for External Source Model (ESM) Maps. Folder structure functionality is already available for Calculations, Maps, Views, Reports, and so on. Similar functionality is now available for ESM maps. Customers should use the latest version of Spotlight XL to leverage this functionality.

Business Value

This functionality helps to organize maps for ease of tracking.

In Practice

1. Access ESM Maps in SpotlightXl by selecting the Model task and the External Source Model > Source Map subtask.

2. The ESM model is the primary folder under which all associated maps can be grouped. Add folders and organize maps as needed.

3. Favorites and Recents folders are also available

Audit Log to Track the Creation of External Source Models

The Audit Log now tracks the date and creator of an External Source Model. It also tracks the date and user when modified.

Business Value

Detailed audit logs provide businesses with the ability to track user actions resulting in accountability and transparency.

In Practice

1. Access the Audit Log in SpotlightXL by selecting the Manage task and the Application Administration > Audit Log subtask.

2. Select the External Source Model component.

Auto Completion of Last Accessed External Source Model

Now, when you navigate to the External Source Model and Source Map pages in SpotlightXL, the last accessed model or map is populated automatically; eliminating clicks.

Business Value

Auto population saves time and eliminates extra clicks.

In Practice: Access the External Source Model Page

1. In SpotlightXL, select the Model task and the External Source Model > Source Model subtask.

2. Select a model and navigate away from the page. When you return, the selected model is displayed.

In Practice: Access the External Source Model Map Page

1. In SpotlightXL, select the Model task and the External Source Model > Source Map subtask.

2. Select a map and navigate away from the page. When you return, the selected map is displayed.

Renamed Field on the External Source Model Map Page

We’ve renamed a field on the External Source Model Map page for consistency and clarification purposes. The field named Model below has been renamed to Target Model.

Ability to Provide a Description for External Source Models and Maps

Prior to this release there was no field available on the External Source Model (ESM) Model or Maps pages to enter a description of the model or map.

Business Value

Descriptions provide a means to more easily and quickly identify models.

In Practice: Entering a Description for an ESM Model

1. In SpotlightXL, select the Model task and the External Source Model > Source Model subtask.

2. Select a model and enter a description in the new Description field.

In Practice: Entering a Description for an ESM Map

1. In SpotlightXL, select the Model task and the External Source Model > Source Map subtask.

2. Select a map and enter a description in the new Description field.

Dynamic Planning: Features Now Available by Default

Prior to this release, the features below were only available on an opt-in basis. Customers need to contact support for enabling these features.

With this release, these features are enabled by default in your application in either Spotlight (web version), SpotlightXL or both.

Spotlight Model Manager - a visual user interface on the Web (Spotlight) for creating, viewing, and maintaining the models and associated artifacts in your application. For detailed information, see the Using Model Manager topic.

SpotlightXL Display Properties for Views - Properties are available in run mode in the ribbon as shown in the image below.

Spotlight Ability to Convert a Master Model Into a Direct Access to PCR Model by Restoring It - For detailed information, see Detailed Steps to Convert a Master Model to a Direct Access to PCR Model and Prerequisites.

Ability to Select Multiple Page Dimensions for a Direct Connect Model - Select multiple members of page filters for views and reports built on Direct Connect Models. Available by default in Spotlight and SpotlightXL. See the Support for Multiple POV Selections in SpotlightXL and Spotlight for Direct Connect Models topic.

SpotlightXL Using Variables in ESM Model Setup - You can use variables and expressions in External Source Model (ESM) Formulas and Maps. Variable and expression usage can simplify ESM maintenance. For detailed information see the External Source Model topic.

Dynamic Planning: API Enhancements

The following API enhancements are now available to all customers.

Export Dimension / Attribute Hierarchy (Master and Analytic Models)

With this API you can include attribute and dimension mapping. You can also export the Attribute hierarchy for a given model in JSON format as well as XML. Example requests and responses in json and xml formats are provided below with dimension and attribute examples.

Export Dimension / Attribute Hierarchy (Master and Analytic Models)

This API allows you to export the entire dimension/attribute hierarchy from a specified model in XML or JSON format. The following data is exported:

• Hierarchy member code

• Hierarchy member parent

• Hierarchy member rollup operator

• Hierarchy member display label

• Mapped attributes

• Mapped dimensions

POST /api/modeling/model/dimension/export HTTP/1/1

Content-Type: application/json or application/xml

Accept: application/json or application/xml

X-ACCESS-TOKEN: $ACCESS_TOKEN_GUID$

Request Payload JSON

{
	“modelName”: “$ModelName”,
    “dimensionName”: “$DimensionName/$AttributeName”,
    “includeAttributes”: true
    “includeDimensions”: true
}

Request Payload

<?xml version="1.0" encoding="UTF-8"?>
<payload>
<model>$ModelName</model>
<dimension>$DimensionName</dimension>
<include-attributes>$includeAttributes</include-attributes>
<include-dimensions>$includeDimensions</include-dimensions>
</payload>

Parameters

1. $ModelName: (type: string) Name of the model. If the model specified does not exist, the operation is canceled.

2. $DimensionName: (type: string) Name of the Dimension that is associated with this model. If the dimension specified does not exist, the operation is canceled.

3. $AttributeName: (type: string) Name of the Attribute that is associated with this model. If the Attribute specified does not exist, the operation is canceled.

4. $includeAttributes: (type: boolean) Include attribute mapping (if applicable).

5. $inclueDimensions: (type: boolean) include dimension mapping (if applicable).

Payload Sample JSON: Dimension Example

{
	“modelName”: “Financial Data”,
	“dimensionName”: “Account”,
	“includeAttributes”: true
}

Request

{
  "members": [
    {
      "memberCode": "Expense",
      "rollupOp": "-",
      "memberDisplayLabel": "Expense"
    },
    {
      "memberCode": "28 DYN Income",
      "memberParent": "Expense",
      "rollupOp": "+",
      "memberDisplayLabel": "28 DYN Income",
      "mapping": [
        {
          "attributeName": "colour",
          "attributeCode": "green"
        }
      ]
    },
    {
      "memberCode": "28 HYP A/C",
      "memberParent": "Expense",
      "rollupOp": "+",
      "memberDisplayLabel": "28 HYP A/C",
      "mapping": [
        {
          "attributeName": "colour",
          "attributeCode": "red"
        }
      ]
    },
    {
      "memberCode": "28 Expense",
      "memberParent": "Expense",
      "rollupOp": "+",
      "memberDisplayLabel": "28 Expense",
      "mapping": [
        {
          "attributeName": "colour",
          "attributeCode": "orange"
        }
      ]
    },
    {
      "memberCode": "ExtraAccountMem21",
      "memberParent": "Expense",
      "rollupOp": "+",
      "memberDisplayLabel": "ExtraAccountMem21"
    },
    {
      "memberCode": "ExtraAccountMem22",
      "memberParent": "Expense",
      "rollupOp": "+",
      "memberDisplayLabel": "ExtraAccountMem22",
      "mapping": [
        {
          "attributeName": "colour",
          "attributeCode": "blue"
        }
      ]
    }
  ]
}

Payload Sample JSON: Dimension leaf member disabled example

When the dimension leaf member is disabled, dimension members mapped to attribute members will not be exported.

{
  "modelName": "Financial Data",
  "dimensionName": "color",
  "includeDimensions":true
}

Response

{
    "members": [
        {
            "memberCode": "color",
            "rollupOperator": "~",
            "memberDisplayLabel": "color"
        },
        {
            "memberCode": "blue",
            "memberParent": "color",
            "rollupOperator": "+",
            "memberDisplayLabel": "blue",
            "mapping": [
                {
                    "dimension": "Account",
                    "dimensionCode": [
                        "Account22"
                    ]
                }
            ]
        },
        {
            "memberCode": "orange",
            "memberParent": "color",
            "rollupOperator": "+",
            "memberDisplayLabel": "orange",
            "mapping": [
                {
                    "dimension": "Account",
                    "dimensionCode": [
                        "28 Expense"
                    ]
                }
            ]
        },
        {
            "memberCode": "red",
            "memberParent": "color",
            "rollupOperator": "+",
            "memberDisplayLabel": "red",
            "mapping": [
                {
                    "dimension": "Account",
                    "dimensionCode": [
                        "28 HYP A/C"
                    ]
                }
            ]
        },
        {
            "memberCode": "green",
            "memberParent": "color",
            "rollupOperator": "+",
            "memberDisplayLabel": "green",
            "mapping": [
                {
                    "dimension": "Account",
                    "dimensionCode": [
                        "28 DYN Income"
                    ]
                }
            ]
        },
        {
            "memberCode": "_Attribute_Default",
            "memberParent": "color",
            "rollupOperator": "+",
            "memberDisplayLabel": "_Attribute_Default",
            "mapping": [
                {
                    "dimension": "Account",
                    "dimensionCode": [
                        "Account21"
                    ]
                }
            ]
        }
    ]
}

Payload Sample JSON: Dimension leaf member enabled example

When the dimension leaf member is enabled, dimension members mapped to attribute members will be exported.

{
  "modelName": "Financial Data",
  "dimensionName": "Enterprise",
  "includeDimensions":true
}

Response

{
    "members": [
        {
            "memberCode": "908",
            "memberParent": "_Attribute_Default",
            "rollupOperator": "+",
            "memberDisplayLabel": "908 - Elim - Hot - Nev Corp"
        },
        {
            "memberCode": "909",
            "memberParent": "_Attribute_Default",
            "rollupOperator": "+",
            "memberDisplayLabel": "909 - Elim - Hot - Nev Inc"
        },
        {
            "memberCode": "2020 AFN",
            "memberParent": "_Attribute_Default",
            "rollupOperator": "+",
            "memberDisplayLabel": "2020 AFN"
        },
        {
            "memberCode": "Enterprise",
            "rollupOperator": "~",
            "memberDisplayLabel": "Enterprise"
        },
        {
            "memberCode": "Sales",
            "memberParent": "Enterprise",
            "rollupOperator": "+",
            "memberDisplayLabel": "Sales"
        },
        {
            "memberCode": "Finance",
            "memberParent": "Enterprise",
            "rollupOperator": "+",
            "memberDisplayLabel": "Finance"
        },
        {
            "memberCode": "_Attribute_Default",
            "memberParent": "Enterprise",
            "rollupOperator": "+",
            "memberDisplayLabel": "_Attribute_Default",
            "mapping": [
                {
                    "dimension": "Company",
                    "dimensionCode": [
                        "908",
                        "909",
                        "2020 AFN"
                    ]
                }
            ]
        }
    ]
}

Payload Sample JSON: Attribute Example

{
  "modelName": "Financial Data",
  "dimensionName": "colour",
  "includeAttributes": true
}

Response

{
    "members": [
        {
            "memberCode": "Expense",
            "rollupOperator": "-",
            "memberDisplayLabel": "Expense"
        },
        {
            "memberCode": "28 DYN Income",
            "memberParent": "Expense",
            "rollupOperator": "+",
            "memberDisplayLabel": "28 DYN Income",
            "mapping": [
                {
                    "attribute": "color",
                    "attributeCode": "green"
                }
            ]
        },
        {
            "memberCode": "28 HYP A/C",
            "memberParent": "Expense",
            "rollupOperator": "+",
            "memberDisplayLabel": "28 HYP A/C",
            "mapping": [
                {
                    "attribute": "color",
                    "attributeCode": "red"
                }
            ]
        },
        {
            "memberCode": "28 Expense",
            "memberParent": "Expense",
            "rollupOperator": "+",
            "memberDisplayLabel": "28 Expense",
            "mapping": [
                {
                    "attribute": "color",
                    "attributeCode": "orange"
                }
            ]
        }
    ]
}

Payload Sample XML: Dimension Example

<?xml version="1.0" encoding="UTF-8"?>
<payload>
    <model>Financial Data</model>
    <dimension>Account</dimension>
    <include-attributes>true</include-attributes>
</payload>

Response

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Payload>
    <Member>
        <Member-Code>Expense</Member-Code>
        <Rollup-Operator>-</Rollup-Operator>
        <Member-Display-Label>Expense</Member-Display-Label>
    </Member>
    <Member>
        <Member-Code>28 DYN Income</Member-Code>
        <Member-Parent>Expense</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>28 DYN Income</Member-Display-Label>
        <Mapping>
            <Attribute>color</Attribute>
            <Attribute-Code>green</Attribute-Code>
        </Mapping>
    </Member>
    <Member>
        <Member-Code>28 HYP A/C</Member-Code>
        <Member-Parent>Expense</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>28 HYP A/C</Member-Display-Label>
        <Mapping>
            <Attribute>color</Attribute>
            <Attribute-Code>red</Attribute-Code>
        </Mapping>
    </Member>
    <Member>
        <Member-Code>28 Expense</Member-Code>
        <Member-Parent>Expense</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>28 Expense</Member-Display-Label>
        <Mapping>
            <Attribute>color</Attribute>
            <Attribute-Code>orange</Attribute-Code>
        </Mapping>
    </Member>
</Payload>

Payload Sample XML: Attribute Example with dimension leaf member disabled

<?xml version="1.0" encoding="UTF-8"?>
<payload>
    <model>Financial Data</model>
    <dimension>color</dimension>
     <include-dimensions>true</include-dimensions>
</payload>

Response

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Payload>
    <Member>
        <Member-Code>color</Member-Code>
        <Rollup-Operator>~</Rollup-Operator>
        <Member-Display-Label>color</Member-Display-Label>
    </Member>
    <Member>
        <Member-Code>blue</Member-Code>
        <Member-Parent>color</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>blue</Member-Display-Label>
        <Mapping>
            <Dimension>Account</Dimension>
            <Dimension-Code>Account22</Dimension-Code>
        </Mapping>
    </Member>
    <Member>
        <Member-Code>orange</Member-Code>
        <Member-Parent>color</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>orange</Member-Display-Label>
        <Mapping>
            <Dimension>Account</Dimension>
            <Dimension-Code>28 Expense</Dimension-Code>
        </Mapping>
    </Member>
    <Member>
        <Member-Code>red</Member-Code>
        <Member-Parent>color</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>red</Member-Display-Label>
        <Mapping>
            <Dimension>Account</Dimension>
            <Dimension-Code>28 HYP A/C</Dimension-Code>
        </Mapping>
    </Member>
    <Member>
        <Member-Code>green</Member-Code>
        <Member-Parent>color</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>green</Member-Display-Label>
        <Mapping>
            <Dimension>Account</Dimension>
            <Dimension-Code>28 DYN Income</Dimension-Code>
        </Mapping>
    </Member>
    <Member>
        <Member-Code>_Attribute_Default</Member-Code>
        <Member-Parent>color</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>_Attribute_Default</Member-Display-Label>
        <Mapping>
            <Dimension>Account</Dimension>
            <Dimension-Code>Account21</Dimension-Code>
        </Mapping>
    </Member>
</Payload>

Payload Sample XML: Attribute - with dimension leaf member enabled

<?xml version="1.0" encoding="UTF-8"?>
<payload>
    <model>Financial Data</model>
    <dimension>color</dimension>
     <include-dimensions>true</include-dimensions>
</payload>

Response

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Payload>
    <Member>
        <Member-Code>908</Member-Code>
        <Member-Parent>_Attribute_Default</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>908 - Elim - Hot - Nev Corp</Member-Display-Label>
    </Member>
    <Member>
        <Member-Code>909</Member-Code>
        <Member-Parent>_Attribute_Default</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>909 - Elim - Hot - Nev Inc</Member-Display-Label>
    </Member>
    <Member>
        <Member-Code>2020 AFN</Member-Code>
        <Member-Parent>_Attribute_Default</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>2020 AFN</Member-Display-Label>
    </Member>
    <Member>
        <Member-Code>Enterprise</Member-Code>
        <Rollup-Operator>~</Rollup-Operator>
        <Member-Display-Label>Enterprise</Member-Display-Label>
    </Member>
    <Member>
        <Member-Code>Sales</Member-Code>
        <Member-Parent>Enterprise</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>Sales</Member-Display-Label>
    </Member>
    <Member>
        <Member-Code>Finance</Member-Code>
        <Member-Parent>Enterprise</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>Finance</Member-Display-Label>
    </Member>
    <Member>
        <Member-Code>_Attribute_Default</Member-Code>
        <Member-Parent>Enterprise</Member-Parent>
        <Rollup-Operator>+</Rollup-Operator>
        <Member-Display-Label>_Attribute_Default</Member-Display-Label>
        <Mapping>
            <Dimension>Company</Dimension>
            <Dimension-Code>908</Dimension-Code>
            <Dimension-Code>909</Dimension-Code>
            <Dimension-Code>2020 AFN</Dimension-Code>
        </Mapping>
    </Member>
</Payload>

Success Response

HTTP/1.1 200 OK

Error Responses

Service Not Available (Possibly due to maintenance)

HTTP/1.1 404 Not Found

One or more HTTP headers were missing

HTTP/1.1 412 Precondition Failed

Could not find payload body <payload>…</payload>

Could not find model: xxx

Could not find dimension: xxx

Dimension cannot be null or empty.

HTTP/1.1 412 Precondition Failed

Unauthorized Access (Access key lookup failed)

HTTP/1.1 401 Unauthorized

Invalid XML (Bad Request)

HTTP/1.1 400 Bad Request

Dynamic Planning: Export Leaf-Level Data (Scoped) (Master and Analytic Models)

This API allows you to export the leaf level data from a specified model in XML format, and, with this release JSON format. Additionally, you can now specify one or more filters to export specific data, and you can use attributes as filters and operation type.

POST /modeling/model/data/export HTTP/1.1

Content-Type: application/json or application/xml

Accept: application/json or application/xml

X-ACCESS-TOKEN: $ACCESS_TOKEN_GUID$

Request Payload JSON - example with Attribute and Operation Type

{
  "model": "$ModelName",
  "filters": [
    {
      "dimension": "$Dimension"/”$Attribute”,,
      "filterType": "$FilterType",
      "filterValues": [
        "$value1",
        "$value2"
      ]
    }
  ],
  "memberDisplay": "$MemberDisplay",
  "suppressZeroes": "$SupressZerosFlag"
  “operationType”: “operationType”
}

Request Payload JSON - example with Attribute

{
  "model": "$ModelName",
  "filters": [
    {
      "dimension": "$Dimension"/"$Attribute",
      "filterType": "$FilterType",
      "filterValues": [
        "$value1",
        "$value2"
      ]
    }
  ],
  "memberDisplay": "$MemberDisplay",
  "suppressZeroes": "$SupressZerosFlag"
}

Request Payload XML - example with Attribute and Operation Type

<?xml version="1.0" encoding="UTF-8"?>
<payload>
   <model>$ModelNamel</model>
   <filters>
      <filter>
         <dimension>$Dimension/$Attribute</dimension>
         <filter-type>$FilterType</filter-type>
         <filter-value>$value1</filter-value>
         <filter-value>$value2</filter-value>
      </filter>
   </filters>
   <member-display>$MemberDisplay</member-display>
   <suppress-zeroes>$SupressZerosFlag</suppress-zeroes>
  <operation-type>AND</operation-type>
</payload>

Request Payload XML - example with Attribute

<?xml version="1.0" encoding="UTF-8"?>
<payload>
   <model>$ModelNamel</model>
   <filters>
      <filter>
         <dimension>$Dimension/$Attribute</dimension>
         <filter-type>$FilterType</filter-type>
         <filter-value>$value1</filter-value>
         <filter-value>$value2</filter-value>
      </filter>
   </filters>
   <member-display>$MemberDisplay</member-display>
   <suppress-zeroes>$SupressZerosFlag</suppress-zeroes>
</payload>

Parameters

1. $ModelName: (type: string) Name of the model

2. $Dimension: (type: string) Name of the dimension

3. $Attribute: (type: string) Name of the attribute

4. $FilterType: (type: string) Dimension filter type, can be FixedMember or MemberAndBelow

5. $FilterValue: (type: string) Value of the filter

6. $MemberDisplay (type: string) Optional, can be either Code or Display Label, but defaults to Code

7. $SupressZerosFlag (type: boolean) Optional, can be either True or False, but defaults to True

8. $OperationType: (type: string) Operation Type, can be OR or AND, but default is OR - applicable among attribute filter values.

Payload Sample JSON - example with Operation Type and Region Attribute

{
  "model": "Financial Data",
  "filters": [
    {
      "dimension": "Account",
      "filterType": "MemberAndBelow",
      "filterValues": [
        "Expense"
      ]
    },
    {
      "dimension": "BusinessCenter",
      "filterType": "FixedMember",
      "filterValues": [
        "000"
      ]
    },
    {
      "dimension": "Company",
      "filterType": "FixedMember",
      "filterValues": [
        "2020 Host Spain",
        "2020 HOST CND"
      ]
    },
    {
      "dimension": "CostCenter",
      "filterType": "FixedMember",
      "filterValues": [
        "1000"
      ]
    },
    {
      "dimension": "Department",
      "filterType": "FixedMember",
      "filterValues": [
        "Sales"
      ]
    },
    {
      "dimension": "Geography",
      "filterType": "FixedMember",
      "filterValues": [
        "000-0000"
      ]
    },
 {
  "dimension": "Region_Attribute",
  "filterType":  "FixedMember",
      "filterValues": [
        "North America"
      ]
    },
{
  "dimension": "Region_Attribute",
  "filterType":  "FixedMember",
      "filterValues": [
        "South America"
     ]
    }
  ],
  "memberDisplay": "DisplayLabel",
  "suppressZeroes": true,
  “operationType”: “AND”
}

Response JSON - example with Operation Type and Region Attribute

[
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Dec-15",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "32.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Jun-15",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "23.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Nov-15",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "31.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Oct-16",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "45.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "May-15",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "22.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Feb-16",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "35.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Aug-15",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "26.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Jan-16",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "33.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Jul-15",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "24.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Feb-15",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "18.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Jul-16",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "41.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Jun-16",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "40.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Sep-16",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "44.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Apr-15",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "20.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Aug-16",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "43.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Mar-15",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "19.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Oct-15",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "28.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Apr-16",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "37.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Mar-16",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "36.0"
    },
    {
        "BusinessCenter": "000",
        "Company": "2020 Host Spain",
        "CostCenter": "1000",
        "ICSegment": "Default",
        "ProductLine": "00",
        "Reporting": "G/L Data (LC)",
        "Time": "Sep-15",
        "Account": "28 Expense",
        "Department": "Sales",
        "Geography": "000-0000 - Balance Sheet",
        "Scenario": "Budget 2013",
        "Amount": "27.0"
    }
]

Payload Sample JSON - example with Region Attribute

{
  "model": "Financial Data",
  "filters": [
    {
      "dimension": "Account",
      "filterType": "MemberAndBelow",
      "filterValues": [
        "Expense"
      ]
    },
    {
      "dimension": "BusinessCenter",
      "filterType": "FixedMember",
      "filterValues": [
        "000"
      ]
    },
    {
      "dimension": "Company",
      "filterType": "FixedMember",
      "filterValues": [
        "2020 Host Spain",
        "2020 HOST CND"
      ]
    },
    {
      "dimension": "CostCenter",
      "filterType": "FixedMember",
      "filterValues": [
        "1000"
      ]
    },
    {
      "dimension": "Department",
      "filterType": "FixedMember",
      "filterValues": [
        "Sales"
      ]
    },
    {
      "dimension": "Geography",
      "filterType": "FixedMember",
      "filterValues": [
        "000-0000"
      ]
    },
    {
      "dimension": "Region_Attribute",
      "filterType": "FixedMember",
      "filterValues": [
        "North America"
      ]
    }
  ],
  "memberDisplay": "DisplayLabel",
  "suppressZeroes": true
}

Payload Sample XML - example with Attribute and Operation Type

<?xml version="1.0" encoding="UTF-8"?>
<payload>
   <model>Financial Data</model>
   <filters>
      <filter>
         <dimension>Account</dimension>
         <filter-type>MemberAndBelow</filter-type>
         <filter-value>Expense</filter-value>
      </filter>
      <filter>
         <dimension>BusinessCenter</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>000</filter-value>
      </filter>
      <filter>
         <dimension>Company</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>2020 Host Spain</filter-value>
         <filter-value>2020 HOST CND</filter-value>
      </filter>
      <filter>
         <dimension>CostCenter</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>1000</filter-value>
      </filter>
      <filter>
         <dimension>Department</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>Sales</filter-value>
      </filter>
      <filter>
         <dimension>Geography</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>000-0000</filter-value>
      </filter>
       <filter>
         <dimension>Region_Attribute</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>North America</filter-value>
      </filter>
   </filters>
   <member-display>DisplayLabel</member-display>
   <suppress-zeroes>true</suppress-zeroes>
   <operation-type>AND</operation-type>
</payload>

Payload Sample XML - With Attribute

<?xml version="1.0" encoding="UTF-8"?>
<payload>
   <model>Financial Data</model>
   <filters>
      <filter>
         <dimension>Account</dimension>
         <filter-type>MemberAndBelow</filter-type>
         <filter-value>Expense</filter-value>
      </filter>
      <filter>
         <dimension>BusinessCenter</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>000</filter-value>
      </filter>
      <filter>
         <dimension>Company</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>2020 Host Spain</filter-value>
         <filter-value>2020 HOST CND</filter-value>
      </filter>
      <filter>
         <dimension>CostCenter</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>1000</filter-value>
      </filter>
      <filter>
         <dimension>Department</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>Sales</filter-value>
      </filter>
      <filter>
         <dimension>Geography</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>000-0000</filter-value>
      </filter>
       <filter>
         <dimension>Region_Attribute</dimension>
         <filter-type>FixedMember</filter-type>
         <filter-value>North America</filter-value>
      </filter>
   </filters>
   <member-display>DisplayLabel</member-display>
   <suppress-zeroes>true</suppress-zeroes>
</payload>

XML Sample Response - example with Attribute and Operation Type

<?xml version="1.0" ?>
<records>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Dec-15</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>32.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Jun-15</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>23.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Nov-15</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>31.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Oct-16</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>45.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>May-15</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>22.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Feb-16</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>35.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Aug-15</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>26.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Jan-16</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>33.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Jul-15</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>24.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Feb-15</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>18.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Jul-16</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>41.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Jun-16</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>40.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Sep-16</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>44.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Apr-15</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>20.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Aug-16</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>43.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Mar-15</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>19.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Oct-15</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>28.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Apr-16</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>37.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Mar-16</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>36.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Sep-15</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>27.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Nov-14</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>14.0</Amount>
    </record>
    <record>
        <BusinessCenter>000</BusinessCenter>
        <Company>2020 Host Spain</Company>
        <CostCenter>1000</CostCenter>
        <ICSegment>Default</ICSegment>
        <ProductLine>00</ProductLine>
        <Reporting>G/L Data (LC)</Reporting>
        <Time>Dec-14</Time>
        <Account>28 Expense</Account>
        <Department>Sales</Department>
        <Geography>000-0000 - Balance Sheet</Geography>
        <Scenario>Budget 2013</Scenario>
        <Amount>15.0</Amount>
    </record>
</records>

Success Response

HTTP/1.1 200/204 OK

Error Responses

Service Not Available (possibly due to maintenance)

HTTP/1.1 503 Service Unavailable

One or more HTTP headers were missing

HTTP/1.1 412 Precondition Failed

Unauthorized Access (access key lookup failed)

HTTP/1.1 401 Unauthorized

Invalid JSON/XML (bad request)

HTTP/1.1 400 Bad Request

Not Found (source model not found)

HTTP/1.1 404 Not Found

Dynamic Planning: Update to the SpotlightXL Add-In

If you have automated installation for SpotlightXL, then there is nothing you need to do as the update will be done automatically.

If you manually install SpotlightXL and related updates, then you must access the Installation Guide and download the latest update.

Consolidation: Post Month-to-Date (MTD) Balances using a Dynamic Journal

With this release, the new MTD (Month-to-date) posting type entries enable you to post Dynamic Journals based on the month’s activity. The Month-To-Date (MTD) posting type entries for Dynamic Journals evaluate entries based on the month’s activity, whereas the Year-To-Date (YTD) posting type entries evaluate the entries based on the cumulative balance for the line items.

Business Value

The Month-To-Date (MTD) posting type entry for Dynamic Journals helps you to post Month-to-Date (MTD) balances by using a Dynamic Journal and evaluate entries based on the month's activity.

In Practice: Add a new Dynamic Journal

1. In the Consolidation Control Panel, under Processes, click Dynamic Journals. The Dynamic Journals grid appears.
2. Click the Add icon. The Add Dynamic Journal dialog box appears.
3. On the Propertiestab, specify the required information for the following fields:
   • In the Code field, enter a code of your choice.
   • In the Name field, enter a Dynamic Journal name.
   • In the Period field, select the month and year range. During the selected time period, the Dynamic Journal is active.
   • In the Posting Type list box, select the MTD or YTDposting type.
     Note:

     MTD (Month-to-date) evaluates entries based on the month’s activity; whereas, YTD (Year-to-date) evaluates the entries based on the cumulative balance of the line items.
   • In the Reporting list box, select whether the Journal is a Dynamic JE (CC) or a Dynamic JE(LC). A journal can be in common currency or in local currency.
     Note:

     A local currency is often used by a company's subsidiaries and then converted to a common currency for consolidated reporting purposes.
   • If you are adding an Unbalanced Journal, select the Unbalanced Journal check box. In Unbalanced Journals, debits are not equal to the total of the credits.
4. To navigate to the Journal Entry tab, click Next or click the Journal Entrytab. The grid displays segment columns based on the application configuration and user's security. To set up a journal entry, perform the following steps:
   • To add a new row, click Add.
   • To set up the values for each column, do any one of the following:
     • Specify the required values directly in the UI.
     • Paste the copied line items from an MS Excel spreadsheet to the journal entry grid.
       You can copy or paste all values, including description, segments, and debit or credit values. Use shortcut keys (Ctrl+C and Ctrl+V) to perform this action.
   • To build a formula for the journal entry, perform the following steps:
     1. Click Rule in the journal entry row. The rule pane appears.
     2. Build a formula by using Simple Rule or Advanced Rule:
        • Simple Rule —For the dimensions for which you want to select a member, open the selection pane and select the member.
        • Advanced Rule —In the left side box, expand the member hierarchy, select the member, and then click the Add icon. Repeat the same procedure to select the function in the right side box. Click the tick (√) icon to verify the syntax of the formula.
     3. To save the rule, click Save

5. Click Save.

Consolidation: Input One-sided or Unbalanced Entries using a Dynamic Journal

With this release, we have a new feature called Unbalanced Journals. You can now define Dynamic Journals as Balanced Journals or Unbalanced Journals. In Unbalanced Journals, debits are not equal to the total of the credits. You can create, save, edit, and update Unbalanced Journals.

Business value

Unbalanced Journals provide you the ability to input one-sided or unbalanced entries by using a Dynamic Journal. Prior to this release, only Balanced Journals were used to add the Dynamic Journal entries.

In Practice: Add a new Dynamic Journal

1. In the Consolidation Control Panel, under Processes, click Dynamic Journals. The Dynamic Journals grid appears.

2. Click the Add icon. The Add Dynamic Journal dialog box appears.

3. On the Propertiestab, specify the required information for the following fields:
   • In the Code field, enter a code of your choice.
   • In the Name field, enter a Dynamic Journal name.
   • In the Period field, select the month and year range. During the selected time period, the Dynamic Journal is active.
   • In the Posting Type list box, select the MTD or YTDposting type.
     Note:

     MTD (Month-to-date) evaluates entries based on the month’s activity; whereas, YTD (Year-to-date) evaluates the entries based on the cumulative balance of the line items.
   • In the Reporting list box, select whether the Journal is a Dynamic JE (CC) or a Dynamic JE(LC). A journal can be in common currency or in local currency.
     Note:

     A local currency is often used by a company's subsidiaries and then converted to a common currency for consolidated reporting purposes.
   • If you are adding an Unbalanced Journal, select the Unbalanced Journal check box. In Unbalanced Journals, debits are not equal to the total of the credits.

4. To navigate to the Journal Entry tab, click Next or click the Journal Entrytab. The grid displays segment columns based on the application configuration and user's security. To set up a journal entry, perform the following steps:

   • To add a new row, click Add.

   • To set up the values for each column, do any one of the following:

     • Specify the required values directly in the UI.

     • Paste the copied line items from an MS Excel spreadsheet to the journal entry grid.

   • You can copy or paste all values, including description, segments, and debit or credit values. Use shortcut keys (Ctrl+C and Ctrl+V) to perform this action.

   • To build a formula for the journal entry, perform the following steps:

     1. Click Rule in the journal entry row. The rule pane appears.

     2. Build a formula by using Simple Rule or Advanced Rule:

        • Simple Rule —For the dimensions for which you want to select a member, open the selection pane and select the member.

        • Advanced Rule —In the left side box, expand the member hierarchy, select the member, and then click the Add icon. Repeat the same procedure to select the function in the right side box. Click the tick (√) icon to verify the syntax of the formula.

     3. To save the rule, click Save

5. Click Save.

Platform: New Icon to Better Leverage Support Assets

We have added a Support icon on the main navigation pane in the Planful application. The Support icon helps you to easily access various help and support resources, with minimal number of clicks and an improved user experience.

You can access the following assets by clicking the Support icon:

• Support Portal – to contact our support team.

• Online Help – to refer to all documentation assets of the Planful application.

• Online Community – to participate in and contribute to our online user community.

• Planful Academy – to get trained in several areas of our product.

To access the Help and Support section, click the Support icon on the main navigation pane (as illustrated in the following image).

Platform: User Management Renamed to User & Role Management

The User Management page has been renamed to User & Role Management. The new name appropriately reflects the actions that can be performed on this page; thereby improving clarity.

In Practice: Access User & Role Management

Go to Maintenance > Admin > User & Role Management.

For more information, refer to the User Management Admin Guide.

Platform: New Navigation and Approval Role Management Access Options

With this release, two new Role Management options have been introduced in the Navigation Access page. The following are the new options:

• Navigation Role Management - When selected, allows you to change the Navigation Role of any user. Additionally, you can add and update the Navigation Access of any Navigation Role.

  If the Navigation Role Management check box is not selected, the user will have read only access to the Navigation Role page and will not be able to perform any actions, such as, Edit, Add, Delete, and so on.

• Approval Role Management - When selected, allows you to add and update any Approval Role.

  If the Approval Role Management check box is not selected, the user will have Read only access to the Approval Role page and will not be able to perform any actions, such as, Edit, Add, Delete, and so on.

  

Business Value

This functionality provides administrators the ability to efficiently control the Navigation and Approval access for a user.

Prior to this release, users with access to User Management were able to update their own Navigation Role along with other user’s Navigation Role.

In Practice: Access Navigation and Approval Role Management check boxes

Go to Maintenance > Admin > User & Role Management > Navigation Role > Navigation Access > Maintenance > Administration > Role Management > Navigation and Approval Role Management.

For more information, refer to the User Management Admin Guide.

Platform: Segment Hierarchy Load Now Retains Order from the Load File

Now, when you load Segment Hierarchy using a Data Load Rule, the order in which data is mentioned in the load file is retained.

Prior to this release, the data from the load file was arranged alphabetically and the original order was not retained. This is applicable to Finance hierarchies only (main and alternate).

For example, when you load a parent and child members using a Data Load Rule as shown in the image below.

The Child Code order is retained in the Hierarchy Management page as displayed in the image below.

Platform: Clear Data Now Available in Shared Mode

With this release, the Clear Data functionality is now available in applications where Shared Mode is enabled. The Clear Data functionality allows you to delete financial data posted by the Consolidation process or loaded using Data Load Rules.

Prior to this release, the Clear Data functionality was not supported in Shared Mode. For more information, refer to Shared Mode.

In Practice: Access the Clear Data Page

Go to Maintenance > DLR > Clear Data.

For more information about the Clear Data functionality, refer to the Data Integration Admin Guide.

The image below displays the Clear Data page in Shared Mode.