The following are upgrade considerations and product changes for Managed Reporting:

• Saved Parameter reports created from HTML Composer do not support -HTMLFORM !IBI. options that retrieve dynamic content because a Save Parameter Report created by the HTML Composer contains the HTM that is the result of running the procedure (FEX) containing the -HTMLFORM command. See the Developing Reporting Applications manual for information on the -HTMLFORM command and !IBI. options to return dynamic content.
• As of Version 7 Release 7, Microsoft Java VM is no longer supported for Managed Reporting Applets. This is to adhere to the Microsoft MSJVM June 30, 2009 end of life date as per the Microsoft Web site in the article entitled, Transitioning from the Microsoft Java Virtual Machine. For more information, see the WebFOCUS Applet Interface Support Statement for Java Virtual Machine (JVM) on the Customer Support Web site.
• As of Version 7 Release 7, new MR user roles named MR Security Object Manager, MR Group Authorization Manager, and No Privileges are available by default. If you migrate from Version 7.1.x or Version 7.6.x to Version 7.7 and had created a custom role with the same name as one of the new Version 7.7 release roles, you may receive an error message. Refer to load.log in the ibi\WebFOCUS directory for assistance and contact Customer Support Services if load.log contains a Found a Custom Role with the same HREF message.
• As of Version 7 Release 7, the Standard Report property Show on User’s List has been changed to Do not show on User’s list. This property appears in the Dashboard and Developer Studio Standard Report Properties dialog box, and in the report development tools create and save dialog boxes that include this property option.

  In addition, when creating a new Standard Report in Version 7 Release 7, the Do not show on User’s list property is selected by default, which makes the report unavailable to end users when it is created. You can change the Do not show on User’s list property before saving the report in those save dialog boxes that include this property, or after it is created by right-clicking the report and selecting the Properties option.

• As of Version 7 Release 7, Managed Reporting Saved Parameter reports created from an HTML form that was created with HTML Composer have the Restrict Developer Access property enabled because Saved Parameter reports should not be edited due to their internal structure.

  Note that Saved Parameter Reports saved to a Domain Standard Report folder also have Do not show on User’s list by default. Developers will only be able to view the properties of a Saved Parameter report created from an HTML form created with HTML Composer because it has both the Restrict Developer Access and Do not show on User’s list properties selected, which specify that Developer users do not have authority to modify or run the HTML form. Developers should save their Saved Parameter report created with HTML Composer as a My Report.

  Even though Managed Reporting Administrators can edit Saved Parameter reports, we recommend that they not because changes to these reports could render them unusable.