When selecting to clear members during the import, any member not specified is deleted from the outline after importing the dimension unless it is an ancestor of a member that was specified, or it is a base member of a shared member that was specified 

You can use import file functionality to import more metadata or to perform incremental updates from the source system 

Your import file must contain a list of Metadata records; and each metadata record contains a delimited list of property values that matches the order designed in the header record 

You can import data forms, dashboards and infolets by loading a local import file or an import file from the Inbox server 

You can rename or delete members of attribute dimensions during a metadata import 

Define a custom view 

Apply a filter user Contains and a specific value 

Drill-through to source from specified data cells

Re-register or modify the data source system 

Export data to PDF 

Validate only for cells and pages the user has access to 

Validate only for pages with existing blocks

• Validate only for users with access to this form 

Validate rules as Service Administrators, regardless of logged-in user, when the form is loaded or saved 

Validate for all page combinations and all existing or potential blocks V

• When Paid 

• Monthly, Quarterly or Semiannually 

• 
  When Billed 

After Completion

• 
  

  • Import data for enabled features 

• 
  Import data into Smart Lists  

• 
  Customize the data import process to your unique requirements 

Allow for a single Excel template to load data to all modules without custom modifications

• Load Data directly into data Management without the need for mappings 

• Smart View

• Calculation Manager 

• Admin Extension 

Data Integration 

• Data Maps 

• Data Management 

• Dashboards 

Data Integration

• 
  Navigation Flows 

• You can use Groovy Rules to dynamically generate calculation scripts at runtime based on context defined in the Groovy script 

• 
  You can use Groovy Rules to perform complex procedural calculations in memory before submitting the results to the database 

• You can use Groovy Rules to define member formulas that combine operators, calculation functions and numeric constants to perform calculations on members in Dimension Editor

You can use Groovy Rules to add validation checks for run time prompt values before running calculations, add data validations checks before submitting data and add error handling 

You can use Groovy Rules to dynamically calculate data and add validation checks before saving data on custom composite forms 

• 
  Promote Employee 

• Transfer

• Plan Departure 

Change Job 

• Remove Existing Employee 

• 
  Map a component to a Financials account in Benefits and Taxes. For Compensation Data, synchronize and then execute the data map. Review the details in the Financial Integration Summary form. 

• 
  When enabling Workforce, set up a data map to define how Workforce accounts map to Financials accounts. On the Financial Integration Summary form, calculate compensation to update the Workforce details.  

• When enabling Financials, set up a custom dimension to store the Workforce data.

When you configure Workforce enable Standard Rates from Workforce. On the Financial Integration Summary form, run a rollup to update the Workforce details 

• 
  Local

• 
  Inbox

Workspace

• Repository

• Specify if the nonanchor dimensions are required 

Indicate if the anchor dimension members not specified or referenced will be valid or invalid 

Specify if a nonanchor dimension is not required 

• Indicate if unselected anchor dimension members are invalid by default

• 
  Select the distribution where the conditions of the distribution match those of the input

Randomly generate a range of values for assumptions and enter best guess estimates one cell at a time 

Evaluate the input in question and list the condition surrounding this input 

• 
  Review the descriptions of the probability distributions 

Use the Monte Carlo method to best guess your probability distribution options based on a range of assumptions 

• 
  If you map Smart List to dimensions, the Smart List entry label or entry name in the source planning cube must match the member name in the reporting cube 

If you use member relationships and at least one member name in the source cube does not match a member in the reporting cube, clearing moving data proceeds without error 

If you map Smart List to dimensions, all Smart List entries in the source cube must match all member names in the reporting cube 

• If you map Smart List to dimensions, clearing and moving data proceeds by overwriting Smart List entries in the reporting cube with the Smart List entries in the source cube 

If you member relationships, all member names in the source cube must match all member names in the reporting cube 

• Benefits 

Taxes 

Additional Earnings 

• Salary 

• You can set the last historical period, number of years to use for historical averages, and the base period. 

You can select to use the current scenario's data for the last actual period. 

You can set the last historical month of the year, last actual month, and the number of years to use for historical averages. 

• You can change which month the fiscal year starts.  

You can change the last actual period.

• 90 Days 

• 60 Days 

• 30 Days 

• 1 Day

• All dimensions are displayed in the Global User Point of View. 

• 
  Dimensions selected by o report viewer for the Global Point of View, are saved for all viewers.  

• Only one dimension is in the Global User Point of View

• Dimensions not defined in a row, column, or page are displayed in the Global User Point of View. 

• Users and groups are restricted from accessing applications by removing custom application and plan-type security. 

• If a user with group access has individual access permissions that conflict with those of a group the user belongs to, group access permissions take precedence. 

• Planning roles can be assigned to members in all dimensions in all modules in the application. 

• A member with Read access that has a parent with Write access to all its descendants results in an access level of Read for that member.