Edit an application
Updated: 2008-11-14
You can edit some application properties, as described in the following procedure. You cannot edit the application label, the name of the application database, or the name of the computer that is running SQL Server and that contains the application database. For information about how to change the name of an application database or the computer that is running SQL Server and contains the application database, see the PerformancePoint Server 2007 Deployment Guide.
To edit an application
On the Application page, select the application that you want to edit.
Click Edit. The Edit an Application dialog box opens. Properties that cannot be changed are indicated with a yellow background.
In the Name box, type a name for the application. Names are meant to be user-friendly descriptors for objects. Names can be up to 256 characters long and are not case sensitive.
In the Description box, type a description of the application. This can include the type of data that it contains or other information that may be helpful to users who are not familiar with the application. The description can be up to 512 characters long.
In the Staging Area section, you create a staging database, direct the application to a different staging database, or remove the current staging database from the application.
To create a new staging database for the application on the same computer that is running SQL Server and that contains the application database, select the Create new staging database check box. Then, in the Staging database name box, type a unique name for the staging database.
To register an existing database as the staging database for this application, clear the Create new staging database check box. Then, in the Staging database name box, type the name of the database that you want to use as the staging database. This database must be on the same computer that is running SQL Server and that contains the application database. Planning Server will verify that the database exists and is a valid staging database.
To remove the current staging database from the application, clear the Create new staging database check box, and then clear the Staging database name box. The existing database will not be deleted but it will no longer be associated with the application.
In the Locations section, type the URL or URI for the network share or Microsoft SharePoint Products and Technologies Web site that stores the supporting documents for assignments in the application.
Important You must specify locations for the first three folders. If you do not, some workflow features will not work, PerformancePoint Add-in for Excel users may receive errors, and Planning Business Modeler will not be able to display supporting documents such as form templates.
For security reasons, make sure that access permissions are enforced on all directories that store these documents. For more information, see Create an application.
In the Form templates location box, type the location for form templates that are associated with assignments. This location is required to support workflow features.
In the Report storage location box, type the location for the supporting reports that are distributed to PerformancePoint Add-in for Excel users through assignments. This location is required to support workflow features.
In the Assignment forms location box, type the location for the associated assignment instances for the application. This location is required to support workflow features.
In the Assignment master forms location box, type the location for the master forms for the application. This location can be used to store backup versions of reports that have been published as form templates. When users want to edit a form template, they have to edit the original report and then republish it as a form template. By saving a copy of the report to this location, published reports will be easier to locate if changes are needed.
Select or clear the Enable native SQL/MDX rules check box. When the check box is selected, business analysts can use rules that are written in SQL, MDX Query, or MDX Script. Planning Business Modeler passes rules that are written in native SQL or MDX to the designated underlying system without change.
Note
If you enable this feature, it may pose a security risk because users will have more processing capabilities that could affect many database objects. As an added layer of security, before a new or edited native rule can be run, a database administrator must set its isActivated property to TRUE in the RuleSetsOrRules table in the application database.
Select or clear the Enable Excel macro support check box. When the check box is selected, PerformancePoint Add-in for Excel users can use macros that can be run with Planning Server forms and reports. This setting applies only to Excel macros that are related to Planning Server.
Click OK.