When migrating a customized Workspace ES application to LiveCycle ES8.2 server, toast messages no longer appear when you recompile in the LiveCycle ES 8.2 development environment. When you create your adobe-workspace-client.ear file in the 8.0.x development environment and deploy the EAR file to LiveCycle ES 8.2, toast messages function as it did in the earlier releases.
In LiveCycle ES Update 1, toast notifications are replaced with message notifications. If you recompile your customiziations in the LiveCycle ES 8.2 development environment, toast messages nolonger appear.
In earlier releases of LiveCycle Workspace ES, session messages appeared as toast messages in the bottom-right corner of the user's web browser. In LiveCycle Workspace ES (8.2), toast messages have been replaced with message notifications. Message notifications appear Messages link in the header within Workspace ES.
Custom applications that you developed in the Workspace ES API for LiveCycle ES 8.0.x are supported on the server where LiveCycle ES 8.2 is installed. The recommended solution is to reuse the custom EAR file that you created in 8.0.x and deploy it on the server where 8.2 is installed. The custom EAR file that you create must use the development environment described in the Customizing the LiveCycle Workspace ES User Interface (8.0.) guide and must be compiled using Flex 2 SDK, hotfix 2 or later. Because the custom EAR file was created in the 8.0.x development environment, toast messages are displayed in your custom version of Workspace ES.
Customized Workspace ES applications do not need to be recompiled with Flex 3 because they are binary compatible, but if you choose to leverage new Workspace ES features or fixes, you must recompile your code using Flex 3 in the LiveCycle ES 8.2 development environment as described in the Customizing the LiveCycle Workspace ES User Interface (8.2) guide. When you recompile your code, toast notifications are no longer available for session messages. Instead, session messages appear as message notifications that are visible if your code uses the HeaderPane component, which is part of the Desktop component. If you are using other components such as the ToDo component and want session messages to appear to your user, you can include the HeaderPane component in your custom application as a workaround. You must also define a model to bind user interface elements links to log out and display help. You must also create a new model component using ActionScript that extends the NavigationSupervisorModel class and implements the IBookmarkTarget and IHelpSource interfaces. For an example, refer to the Desktop.mxml and DesktopModel.as files in the Workspace ES source code.