The section describes known issues in version 11.2 of Tools and Frameworks.

(18816983) BCC user segment not appearing in Experience Manager

If you create a Business Control Center (BCC) user segment in the RepositoryGroup folder and then move it to the UserProfiles folder, the segment ceases to appear in Experience Manager. Note that this only applies to environments where the BCC user segments are enabled in Experience Manager.

Workaround: Delete the Business Control Center user segment from the RepositoryGroups folder and create it again in the UserProfiles folder.

(18780298) Cartridge example causes error

The ColorConfig cartridge example found in ToolsAndFrameworks/<version>/reference/cookbook/AccessingCartridgeConfiguration causes an error when added to a page.

(18895941) New user segment not appearing in list

When creating a new user segment, if you go into Experience Manager and attempt to preview the application with that new user segment, you may not see it in the "User Segments" drop down.

Workaround: Log out of Workbench and log back in and then the new user segment will appear in the "User Segments" drop down in Preview.

(21363913) Renaming and moving pages are not updated in Experience Manager projects

In Experience Manager, if you rename or move a page the modification date does not get updated as it would for other edits. You can see this behavior reflected in the timestamp in the project contents list and the page's edit view. In both cases the timestamp is not updated, The rename or move, however, still shows up in the project contents list and can be reverted like any other change

(21502844) Renaming and saving a site page produces "Page not found" error

If you rename a top level site page in Experience Manager and then save and preview the page, you see "Page not found" in the page contents. The rename operation is technically a move operation in Experience Manager, so the old path no longer exists. Although "Page not found" is the correct behavior, a more informative message should appear.

Moreover, renaming a site page that is associated with the search service can hinder your search capabilities -- for example the browse page in the sample Discover Electronics application. Oracle does not recommend letting non-administrators edit this page.

Workaround: In the navigation tree, right-click on the renamed site page and select Preview.

(21649751) Authoring assemblers are not being updated correctly after importing Workbench content

In 11.2.0, after you run import_site.sh|bat to import Workbench content, authoring assemblers are not updated correctly. When you view the authoring version of your Assembler Web application, for example, Discover Electronics reference application, an error message is displayed.

Workaround: After you run import_site.sh|bat to import Workbench content, from the control directory of the deployed EAC app, run the following command to update all authoring Assemblers:

runcommand.bat IFCR deployContent "Authoring"

(21657293) Error message/out of sync message is displayed after renaming a rule

In Experience Manager, when you rename a rule and do not save it, and then click on another rule, you get a Save or Discard dialog on the first rule as expected. But when you click Save, you see an out-of-sync message. Repeated operations on the rule generates this message: "There was a problem with your request: javax.jcr.PathNotFoundException: Unable to locate workspace node for rule-and-path"

In this release, renaming a page, folder or rule is treated as a move. Therefore some actions on the renamed asset might generate the above types of messages.

Workaround: Save your renamed asset before you navigate away to another asset.

(21671840) Renaming a folder displays misleading error message

If you are not an administrator and try to rename a top-level folder under Rules in Experience Manager, you get a misleading message: "Error message: Error saving changes. Authentication may have timed out. "

Although the user cannot rename the folder, the message should indicate that the user does not have permission to do so instead of the misleading message.

(21801912) Preview does not refresh after adding content

In Experience Manager preview, if you click Keep Editing, update content, and then click Save and Preview, the preview panel does not refresh with the updated content.

Workaround: Preview the page from navigation tree, or reload the page from navigation tree and then preview it.

(21822985) Increase and decrease icons are missing

In Experience Manager, when you right-click a column in the Project Contents panel and select Resize - Width, the increase and decrease buttons on the Resize Width dialog do not show icons to identify which button increases or decreases the width value.

Workaround: You can adjust the width by dragging the column dividers. You can also use the up and down arrow keys on your keyboard to increase and decrease the value or type in a new value.

(21824187) Intermittently cannot add new rule using Internet Explorer

If you are using Experience Manager in Microsoft Internet Explorer and you try creating a rule, sometimes the rule editor displays the toolbar but not the header and body of the editor. This issue happens intermittently.

Workaround: Reload the browser window. If this issue persists log out and then log back in, again.

(21832913) Find All and Folder list panels can take a long time to load with rules

If you have lots of rules in Experience Manager, the Find All and Folder List panels can take awhile to load. Oracle tested with 5000 rules and it took over 2 minutes to load these panels.

(21864376) Cannot export an application when a folder name is changed from upper to lower case

This issue is specific to Microsoft Windows deployments of Tools and Frameworks.

If you change the case of a folder name in Experience Manager but do not change the name itself, the application cannot be exported. This issue occurs because a rename is technically a move in Experience Manager and a moveSource and moveTarget cannot have the same name. Windows file systems do not recognize differences in case. Only one asset can exist at a location with the a given name. This issue only occurs in Windows because its file system is not case sensitive.