ProblemConsider the following scenario:
- An RES Workspace Manager application building block is edited to specify a different application icon according to the Administration Guide article "Specifying a different application icon, Outlook signature or Registry setting"
- The custom icon file is present in the same folder as the building block xml file.
- The building block is imported with the option "Import Workspace Manager Objects with:" set to "New GUIDs (creates new objects)
When importing the building block no icon or a legacy icon will be displayed in the RES Workspace Manager console instead of referenced icon file in the building block.
CauseDue to a coding error the .ico file, referenced in the building block, is not being imported when using the "New GUIDs (creates new objects) " setting despite that the .ico file is present in the same folder as the building block xml file.
SolutionThis issue is resolved in RES Workspace Manager 2014 SR2.
In case the Service Release is not (yet) available or in case the Service Release cannot be installed, a revision containing this update is available on request at RES Support.
IMPORTANT: A revision contains multiple fixes. Only apply this revision when you are experiencing a specific problem. Unless you are severely impacted by this specific problem, RES Software recommends that you wait for the next service release containing these fixes.
When RES Workspace Manager 2014 SR1 Revision 1 (188.8.131.52) or later is installed specify the exact path to the .ico file.
Import the applications building block with the setting "Import Workspace Manager Objects with: ", set to "New GUIDs (creates new objects) make sure that you have specified the exact path to the location of the .ico file in the building block at:
<icon32x256 filename="folder path\icofile.ico"></icon32x256>
In this example the folder path is the exact path to the .ico file, icofile.ico must be replaced with the correct filename of the used .ico file.