Maintenance Opt-ins

This article provides information on the Maintenance opt-ins.

• Asynchronous processing for export data

• Custom URL

• Data Load Missing Segment Member

• Update Only Leaf Node Roll-Up Operator for Segment Hierarchy Data Loads

• Additional Web Service Access Authentication

• Performance Improving Partitioning Functionality

• Data Load Cloud Processing

• Dynamic Dimension Security

Note:

By default, these flags are turned off. Contact Planful Support to opt in for these features.

Asynchronous processing for export data

Export Data is handled asynchronously in all newly configured applications, enhancing the application's performance by processing requests with a quick response time. Processing Export Data requests with large data sets synchronously can negatively impact the application's performance. To improve efficiency and experience, enabling asynchronous processing is recommended for your application.

Custom URL

Planful customers have the option to establish a personalized URL for their Planful application. For instance, a customized Planful URL could be configured as xyz.planful.com. For more information, click here.

Data Load Missing Segment Member

This feature, available by request, eliminates data load failures due to missing segment members. Missing segments represent those that are not available in the Planful system but are available in the data files loaded to Planful. For example, during a web service file load, the load will fail if Planful encounters segment members not in the system. However, you may now use this opt-in feature, which automatically adds missing segment members.

Note:

This feature works for GL Data Load types only. It works with all forms of data loads (web services, file loads) except for copy/paste.

For instance, let's consider a segment member, Account X exists in a data file you are loading to Planful. However, Account X is considered "missing" because it does not exist in Planful. With this feature, the system (Planful) will add Account X with default properties. Upon completion (of the data load), you will receive an email indicating which segment members were created/added. At this point, you may modify the added Account X's default properties and position it properly within the tree structure. Then, rerun the Data Load Rule so all data loads as intended. To ensure that the account properties can be changed, enable “Enforce changing the account properties when the data is available” on the Maintenance >Administration> Security Administration page.

Update Only Leaf Node Roll-Up Operator for Segment Hierarchy Data Loads

By default, when uploading a leaf member of a segment hierarchy via a DLR input file with Allow Property Change enabled, the system updates the properties, including the parent’s roll-up operator, based on the value specified for the leaf node.

This feature is especially useful when you want to update the properties of leaf nodes during a DLR upload without affecting parent node roll-up operators.

Notes:

• This feature is opt-in and applies only to the Main Hierarchy.

• Contact Planful Support to enable this functionality.

• This impact applies to both new and existing leaf nodes loaded via DLRs.

How It Works

To update only the Leaf Node roll-up operator and not the parent node roll-up operator, the following conditions must be met:

Note:

If any required condition is not met (e.g., an entry set to No in the leaf node column), the system reverts to default behavior where parent roll-up operators are updated based on the uploaded file.

Example:

You upload a segment hierarchy file where the leaf node Account_4000 has a roll-up operator of "~". It rolls up to a parent node Account_3000, which currently uses a "+" roll-up operator.

You upload a segment hierarchy file where the leaf node Account_4000 has a roll-up operator of "~". It rolls up to a parent node Account_3000, which currently uses a "+" roll-up operator.

• With the feature enabled and all conditions met:

  • Only Account_4000 is updated to "~".

  • Account_3000 retains its existing "+" operator.

• Without the feature, or if any condition is not met:

  • Both Account_4000 and its parent Account_3000 are updated to "~".

Note:

This feature is supported only for the Main Hierarchy. It does not apply to Alternate Hierarchies.

Additional Web Service Access Authentication

SSO support applies to Web Services. In addition to SSO support, there is a new enhancement, which requires a valid Planful user ID (Login) for Web Services access.

Note:

Contact Planful to enable this enhancement. This enhancement is opened by default for new customers live on Planful after February 2015.

Access the Web Service Access page by navigating to Maintenance > Configuration Tasks, and click Web Service Access. Currently, Web Service Access configuration allows you to enter any value for Login and Password fields. With this update, for security purposes, you must enter a valid Planful user ID (Login).

The Login and Password fields are not available to ensure that only valid Planful users (with valid a login and password) have access to Web Services.

Performance Improving Partitioning Functionality (I.D. open_FACT_GL_PARTITION)

Performance depends on the data volumes by scenario and the overall size of the FACT_GL table. By partitioning the table, performance is improved.

Data Load Cloud Processing

This functionality allows all GL Data and Translation data loads (set up using Data Load Rule functionality) to be automatically updated and processed in the cloud.

Dynamic Dimension Security

Note:

In this section, Dynamic Dimension Security and Dimension Security are used synonymously.

Dynamic Dimension Security significantly improves Dynamic Reports performance and is available on an opt-in basis. (If Workforce Reporting is turned on, Dynamic Dimension security is enabled by default.) This feature is applicable for the Financial and Workforce Reporting Areas.

• If dimension security is turned on, but user access is not provided for the respective dimensions, the following message will appear:

"You are not authorized to access the Reporting Area.
Contact your System Administrator.”

• If access is provided to the user on the main hierarchy, access to the corresponding leaf members in the alternate hierarchy is automatic if dimension security is turned on. Alternate hierarchies have automatic permissions if Copy Budget Entity Security is selected on the Dimension Security Configuration page.

• If access is provided to the user on a member within the main hierarchy, access is automatic to view the calculated members that are defined using the member on which the access is turned on in the dimension tree. However, the data calculation is displayed in the report for calculated members only if the user has access to all the members that are used in the calculated member rule. If the user does not have access to at least one member applied on the rule, the report is run successfully and an empty line is returned for the calculated line. This behavior is applicable only if dimension security is turned on.

• If all attributes are selected, it applies only to those dimensions for which attributes are mapped and ignores the ones which are not mapped.