Known limitations
This table contains known limitations in HCL® Marketing Operations version 10.0.
| Issue | Issue ID | Description |
|---|---|---|
| Multiple scroll bars for dashboard portlets | 3066 | If you reduce the size of the browser window, dashboard portlets can display with two scroll bars. Both Marketing Operations and Marketing Platform add the scroll bar control. |
| Unable to add forms with accented characters. | 8027 |
Users cannot add forms with accented characters in the form name or table name fields. This issue is now fixed. |
| 5000 error occurs on Oracle when form attribute string is too long. | 175488 | The Oracle database limits the form attribute string to 30 characters. Exceeding this length causes a 5000 error. |
| Incorrect asset URLs | 177613 | Adding forms to asset templates can cause errors on URLs. |
| Projects and subprojects must be cleared manually | 5817 | When you request the Project Health (Monthly) report, you can select the Projects and Sub Projects to include. If you select a value in either of these lists, and then want to make other selections, you must clear all of the projects or subprojects before you make your other selections. |
| Relevant products related to offers from Campaign are not migrated over to Marketing Operations | 62333 | Campaign offers have a relevant products feature, Marketing Operations offers does not have this feature. Therefore, relevant products are not migrated from Campaign to Marketing Operations. |
| Exception when comments exceed the defined limit | DEF062980 | A database exception occurs when a user enters a text string into a field that exceeds the limit imposed by the database. For example, on a system that uses a DB2® database, an attempt to save a project description of longer than 1,048,576 results in an error. This limitation is imposed by the database server. |
| Safari browser downloads data migration files directly to downloads folder | DEF063699 | When you perform a data migration import while using Marketing Operations with the Safari browser, you are not prompted for a destination folder. Imported files are downloaded directly to the folder designated for downloads in Safari. |
| Users cannot add marketing objects in languages other than English | DEF057079 | Marketing Operations does not allow multibyte characters in the marketing object type name. |
| Unable to add forms or templates with non-English characters in the form name, form attribute name, or table name fields | DEF057100 | Form and template fields with non-English characters cannot be saved. |
| The task pane allows users to edit the Summary tab even if the project is canceled or completed | DEF057121 | If a project is canceled or completed on the Summary tab while the task pane is open at the right side of the page, you can continue to edit project forms in the task pane, even though it is no longer active. |
| Primary key violation when a legacy metrics template is mapped to new template | DEF057563 |
In Marketing Operations version 8.5.0, the external metrics editor was moved into the application. Metrics templates created in version 8.5.0 must specify a type, which corresponds to plans, programs, or projects. Although Marketing Operations keeps legacy metrics templates for use with plan, program, or project templates created before version 8.5.0, these legacy metrics templates cannot be used in new object templates because they do not have this type information. When creating new plan, program, or project templates, users must select a metrics template that has the same type. If users need to use a legacy metrics template in a new object template, they must recreate it using the new internal metrics configuration feature. |
| Default dates on the grid do not always localize correctly | DEF057605, DEF040170 | The date selection control for grids is not localized for non-English locales, so the default value for a grid date attribute is not always populated for some non-English language locales (such as Japanese). |
| A reviewer who has not yet responded cannot continue an "On Hold" Approval from right task pane | DEF057650 |
If a reviewer has not responded to an approval in the On Hold state, then the task pane on the right cannot be used to continue that approval. The Approve, Approve w/changes, and Deny buttons display for the approval in the task pane, but the continue and cancel buttons do not display. In contrast, an approver who has already responded to the approval can continue it from right pane. This scenario occurs because the buttons on the right pane are driven by the role of the user: Approver or Approval owner. If the approver and the owner are the same user, approver actions take precedence. |
| Formulas for computing metrics must be in English | DEF057660 | When adding metrics to metrics templates, the user can specify them as Planned or Rollup. If the user enters a formula in the Computed by Formula field, the formula must be in English. An error results if a user enters a translated string instead of ROLLUP. |
| Metrics formulas are not validated | DEF057726 | If an invalid formula is specified for a metric, an exception error results when Marketing Operations finalizes values entered on the Tracking tab of an object instance that uses the metric. Please see the product documentation for information about valid operators and operands. |
| Groups do not upgrade in custom forms with database table names that use uppercase | DEF058551 | This limitation applies to installations that upgrade from 7.5.x to 8.5 and then to 9.0 (a two-step process). Custom forms that include attributes in custom groups and that include an uppercase character in the form table name do not upgrade correctly. The custom groups are deleted and the attributes are moved to the default group. |
| Offers are not available in the Marketing Object Type dropdown when adding a SSOR/MSOR attribute | DEF059340 | Marketing Operations version 8.5 has a default marketing object 'Offers' (uap_sys_default_offer_comp_type) for integration with the offer management in Campaign. If a single-select object reference attribute referring to the marketing object type "Offers" is created with the auto-create option, it causes problems since some essential fields (for example: Campaign offer code) are not generated with the auto-created offers. To avoid these subsequent problems, the SSOR and MSOR attributes are not allowed to refer to Offers. Offers are not made available in the 'Marketing Object Type' dropdown while adding a SSOR/MSOR attribute. |
| Limitations in importing offer templates | DEF059793 | Offer templates are not imported in the following cases.
|
| Require reason for denying an approval feature cannot be disabled | N/A | When Marketing Operations is configured to require a reason when users deny an approval, users must select a value for the deny reason. After users begin to use this feature, the system cannot be re-configured to disable this feature. |
|
Marketing Operations single URL configuration does not support the analysis tab for plans and programs |
172856 |
If the analysis tab for a plan and program object is configured as single URLs, after clicking these URLs the user interface does not display the tabs to navigate to other parts of the plan or program objects. |
| In Marketing Operations- Campaign integrated systems, the single URL feature has limited functionality | 177309 |
For a single URL configured campaign project, the implementation tab is not visible. The single URL feature is not implemented for campaign tabs |
| Marketing Operations approvals on mobile IOS systems have layout problems | 178600 | The post-complete response button and file names are difficult to see on IOS devices. |
AcquireLock API does not throw an exception even if a user has opened the
people tab and other tabs in edit mode. |
166474 | When using the IBM Marketing Operations API, it is not possible to acquire a tab level lock on an object. The API only allows object level locking, whereas the GUI allows tab level locking. |
| Form creation, publishing, and usage does not work when DB2 owner and user different | 19733 | This issue occurs only when the user mentioned in the data source is not the one who has created the database tables. |