News
Abstract
The following updates will be available in release 2.0.61 SC of Planning Analytics.
This document also describes known issues in 2.0.61 SC.
Content
Planning Analytics Cloud customers can now create their own TM1 databases by using Planning Analytics Workspace Administration. You no longer need to submit a support ticket to have a TM1 database created for you.
You must use the new Planning Analytics Workspace interface, which is also referred to as New Experience, to create a database. You can even create a database while using the New Experience in Preview mode; there's no need to commit to a permanent upgrade! You can learn more about enabling the New Experience in Preview mode in this Knowledge Center topic: Manage the new experience for your users.
You cannot create a database in Planning Analytics on Cloud using the Planning Analytics Workspace Classic interface.
To create a database, just click the Add button on the Administration/Databases page.

The database is created in the standard location. You can configure and manage the database just like any existing TM1 database. You can set up security, configure the service, and more. All users with the Planning Analytics Workspace Administrator role are given ADMIN access to the new database.
To rename or delete the TM1 database that you created, you still need to open a support ticket.
Welcome Kit change for Planning Analytics on Cloud
The security mode 1 "admin" user name and password for each TM1 database are no longer included in the Welcome Kit for Planning Analytics on Cloud.
This change reduces the size of the Welcome Kit and eliminates the need to regenerate and distribute the kit after each request to create, rename, or delete a TM1 database.
When a database is created, a randomly generated password is set for the security mode 1 "admin" user name. If you need to use the admin user, administrators can set a new password by using the AssignClientPassword TurboIntegrator function.
For more details, see The Welcome Kit.
Preview nested dimensions while forecasting
Forecasting in Planning Analytics Workspace now supports the preview of nested dimensions.
In the following example, SampleRegion and Product are the nested row dimensions. Jeans is selected for preview and Preview is enabled.

Sixty minute inactivity timeout for Planning Analytics Workspace on Cloud
Currently, Planning Analytics Workspace on Cloud enforces a 24 hour session timeout. This session timeout disconnects a user 24 hours after their most recent login and requires the user to log back in to Planning Analytics Workspace. The session timeout is enforced regardless of user activity. If a user is active continuously, the session timeout is still triggered 24 hours after the most recent login.
In addition to this session timeout, Planning Analytics Workspace 2.0.61 introduces an inactivity timeout. When a user is inactive for 60 minutes, the user is logged out of Planning Analytics Workspace. This inactivity timeout is mandatory and applicable to all Cloud customers. The 60 minute inactivity interval is static and cannot be modified.
Planning Analytics Workspace will warn a user about an imminent timeout due to inactivity. If the user does not intervene, the inactivity timeout occurs 60 minutes after the most recent activity.
When an inactivity timeout does occur, what is the impact on the user?
- Workspace end user state will be lost.
- Authoring of Books and Plans/Applications that are not saved will be lost.
This new inactivity timeout is applicable only to Planning Analytics Workspace on Cloud, but also impacts Planning Analytics for Microsoft Excel. For more information on how the inactivity timeout impacts Planning Analytics for Microsoft Excel, see Timeouts in IBM® Planning Analytics for Microsoft Excel.
For details on configuring timeouts in Planning Analytics Workspace Local, see Configuring parameters for Planning Analytics Workspace Local.



Start typing in the box to see the objects that contain your search string. The results are updated continuously as you enter characters.
Reset a sandbox
You can now reset data in a sandbox with a single click.
Click the Sandbox discard button to discard all data changes since your last commit action.



Was this topic helpful?
Document Information
Modified date:
09 March 2021
UID
ibm16412321