Home
Administrator Guide
With Unica Plan, you organize the people, tasks, and budget for marketing programs, while you reduce costs and time to market.
Multiple locale support
For organizations with Unica Plan users in multiple locales, you can translate the labels and text strings in the user interface for each locale.
Localized object types
To localize user interface labels and text strings for object types, you edit .xml and .properties files for the objects.

Administrator Guide
With Unica Plan, you organize the people, tasks, and budget for marketing programs, while you reduce costs and time to market.
- Overview
  With Unica Plan, you organize the people, tasks, and budget for marketing programs, while you reduce costs and time to market.
- Plan interface customization options
  Unica Plan offers options for customizing the user interface. You can customize or rebrand the Unica Plan interface to match your organization's needs.
- Unica Plan integrations
  Unica Plan offers integration with Unica Campaign, Unica Centralized Offer Management, and Unica Journey. Integration with Unica Centralized Offer Management is only used for migrating offer management capability from Unical Plan to Unica Centralized Offer Management.
- Marketing object types
  Marketing objects are the work products that a team develops and reuses in the course of marketing activities. In addition to a set of standard marketing object types that is supplied with Unica Plan, you can create custom marketing object types.
- Project and request deactivation
  After your organization uses Unica Plan for some time, the user interface can become cluttered with out-dated or unwanted projects and requests. You can deactivate projects and requests to reduce clutter and simplify searches.
- Plan reports
  Unica Plan provides a set of default reports and dashboard report components. The Unica Plan reports package provides extra reports and dashboard report components, which are created in IBM® Cognos®, a separate business intelligence application.
- Template Basics
  A template for a marketing object type, such as a plan, program, or project, defines the information that your organization wants to capture about the object. Then, you use templates to create object instances. If you have the Financial Management module installed, an invoice template defines the information that your organization wants to capture in invoices.
- Adding or editing templates
  After you identify the template components that you need, you can create the template. You need to build components before assembling them in the template.
- Program and project templates
  Program and project templates have additional tabs that customize the object instances that are made from the template.
- About forms
  A form is a collection of attribute fields that gather information about an object.
- About attributes
  An attribute defines a piece of information that you want to gather from a user. For example, the information can be text, integers, dates, or a choice from a predefined list. In Unica Plan, you define attributes to collect these different types of information, and then place them on forms. Then, you can add or more forms to templates as tabs. When users create items, they select a template. Each attribute that is included in the template corresponds to a field or other user interface control on the tabs that collect information.
- About metrics
  Metrics measure the performance of an object and are always numeric. Typical metrics include financial metrics, such as cost and revenue, and performance metrics, such as the number of contacts and the number of responses in a particular marketing campaign.
- Multiple locale support
  For organizations with Unica Plan users in multiple locales, you can translate the labels and text strings in the user interface for each locale.
  - Localized object types
    To localize user interface labels and text strings for object types, you edit .xml and .properties files for the objects.
  - About localized format and symbol settings
    The <Plan_Home>/conf/<locale>/format_symbols.xml file stores values to localize the display of dates, currency, months, and days of the week for each supported locale.
  - Multi-locale support for templates
    Templates in Unica Plan have features to support organizations that use multiple locales. You can use the properties file to localize the template. You can also localize some aspects of templates through the Unica Plan user interface.
  - Localizing templates through the properties file
    Export and edit the properties file to localize field values on templates.
  - Globalizing standard attributes
    You can customize the attributes on plan, program, and project templates for your organization and locales. You can globalize standard attributes that display on the plan, program, or project Summary tab by editing the Attributes tab.
  - Localizing forms
    If your organization supports multiple languages, you can make forms available in multiple languages so users can work with forms in their own languages. You localize a form by exporting it and then creating a translated properties file for each locale that you want to support.
  - Localizing metrics
    You can export the properties file and then modify it to localize metrics.
  - Localizing lists
    When you save a list, the system generates a properties file for the appropriate list. The file name is <list_category>_<defaultLocale>.properties.
- About security
  You configure security policies that grant users permission to access specific objects and features through assigned access roles.
- Setting up alerts
  Alerts are notifications of important changes that users need to know about, or reminders about actions that they need to take.
- About list definitions
  The user interface of Unica Plan presents several list box controls that you can configure to provide a customized set of options.
- Implementing project health rules
  To help project owners and participants track the overall status of their projects, you configure the system to calculate project health.
- Exporting and importing metadata
  You can transfer data structures (metadata) between Unica Plan systems using the export and import features.
- Setting up libraries for digital assets
  Through the optional Digital Asset Management module, Unica Plan provides centralized management, secure storage, and web-based access for digital assets.
- Setting up accounts
  An account in Unica Plan represents a specific corporate General Ledger (GL) account that is established by a finance department to track and control expenditures and cash flows. Accounts are a feature of the optional Financial Management module.
- About advanced topics
  This chapter provides information about advanced customization options for the Unica Plan interface.
- Unica Plan Rest API
  The Unica Plan REST API is a façade that provides a client view of a running Unica Plan instance.

Localized object types

To localize user interface labels and text strings for object types, you edit .xml and .properties files for the objects.

If your organization supports multiple locales, the user interface labels and text strings for marketing object types can be translated into the language of each locale. To localize these labels and text strings for your organization, you follow the procedure to rename an object type. You edit the sysmodules.xml, sysmenu.xml, and UMOConfigurationMessages_<locale>.properties or UMOMktObjectConfigurationMessages_<locale>.properties files for each supported locale.

For standard marketing object types, Unica Plan supplies a properties file for each locale. This file contains a set of properties that define user interface labels and strings for each standard marketing object types. These files are the <Plan_Home>/messages/com/ibm/umo/ext/UMOConfigurationMessages_<locale>.properties files.
The first time that you create a custom marketing object type, Unica Plan creates another properties file for each locale. This file contains properties that define labels and strings for the custom marketing object type. Each time that you add a custom marketing object type, the system adds a set of properties for it to these files. These files are the <Plan_Home>/messages/com/ibm/umo/ext/UMOMktObjectConfigurationMessages_<locale>.properties files.

In these files, the list parameters define labels and text strings for the page that displays when users select the menu item for the object type. The ui parameters define labels and text strings for the pages that display data for a single instance of that object type.

For example, for the project marketing object type, this parameter defines the label for the "Owner" column on the project list page:

projectlist.columnList.PROJECT_OWNER.header

In the English language properties file, the value for this parameter follows:

projectlist.columnList.PROJECT_OWNER.header=Owner

In the German language properties file it follows:

projectlist.columnList.PROJECT_OWNER.header=Besitzer

For more information, see Renaming marketing object types.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.