User Guide

Property Description
Example: true
export.provisioning.all Indicates whether to export all provisioning data. Set this
property to
false to export a subset of the provisioning data
by using these properties in tandem:
● export.projectnames
● export.applicationnames
Alternatively, you can select a subset by setting
export.provisioning.apps.
Note: The values of these properties are ignored if
export.provisioning.all is set to true.
Example:
true
export.delegated.lists Indicates whether to export delegated lists.
Example:
true
export.user.filter (Optional.) Filter to use to select users for export.
See “Considerations for Setting Filters” on page 112.
Example:
*
export.group.filter (Optional.) Filter to use to select groups for export.
See “Considerations for Setting Filters” on page 112.
Example:
*
export.role.filter (Optional.) Filter to use to select roles for export.
See “Considerations for Setting Filters” on page 112 for more
information.
Example:
*
export.producttype (Optional.) A comma-separated list of product types for which
roles are to be exported (must be specified as
<product
code>-<product version>
). See “Product Codes” on
page 111.
Example:
HAVA–9.3.1
export.provisioning.apps A list of applications (in (projectname=application
name)
format) from which provisioning data is to be exported.
Applications names are listed in the User Management
Console.
Example:
(( Planning_Project = Plannig_Application_Nam
e
)( Hyperion_BI+_Project_Name = Hyperion
System 9 BI+ Appplication1
))
import operations
import.fileformat
The format of the import file. You can import data from XML
or CSV files.
Example:
xml
110
Managing Provisioning