Changing the Mobile Workflow Package Icon for Android

Modify the Workflow package application icon.

You cannot add new icons to the folder, but you can replace the existing icon images, using the same file name. The Workflow application icons are named ampicon<index>.png, where <index> is a number between 30 and 116. The icon ampicon48.png is the default Workflow application icon. Any Workflow application that has not had its icon specified uses this icon. This is also the icon that is shown on the menu item that shows all the Workflow applications.

Each Workflow icon has two associated image files that contain images for processed and unprocessed messages. The files have the names ampicon<index>.png and ampicon<index>p.png. The second file, with the additional "p" in the name, is the processed message icon, while the other is for unprocessed messages. Processed means the message has been submitted to the server.

When you build the Hybrid Web Container with custom icons, the original icons still appear in Sybase Control Center and in Sybase Unwired Workspace. You must remember the original icon, so you can select it in Sybase Unwired WorkSpace and in Sybase Control Center.

  1. Identify the image currently used by the Mobile Workflow Package that you want to replace. To find the image that is currently used by the Workflow:
    1. Log into Sybase Control Center.
    2. In Workflows, select the Workflow package for which to replace the image.
    3. Click the General tab.
      The icon is shown in Display icon.
  2. Go to the …\HybridWebContainer\res\drawable\ folder and find and replace the ampicon<index>.png and ampicon<index>p.png image files with the new images.
    Note: The new image files must use the same name as those you replaced, including the file extension, and they must have the same resolution as the original images.

    If you do not want to overwrite the icon entirely, make a copy of it using another name and move it out of the folder. Having extra files in the drawable folder may interfere with the indexing of the resources.

  3. Rebuild the Hybrid Web Container.