Localizing the Share Queue Request form (queuesharing.swf file)

In Livecycle Workspace ES, a user can request access to another user’s (say Alex Pink’s) task queue. This initiates a queue sharing process and a Share Queue Request form appears in the Alex’s To Do list. The Share Queue Request form is a Flex application provided with LiveCycle Process Management ES and is available in LiveCycle Workbench ES in the queuesharing.swf file.

In earlier releases of LiveCycle ES, the source code for the Share Queue Request form was not provided with the rest of the LiveCycle Workspace ES source code, therefore, if you localized Workspace ES to another language, such as Spanish, the Share Queue Request form would still appear in English. In LiveCycle ES Update 1 SP 1 (8.2.1.1), the source code for the Share Queue Request form is now available in the LiveCycle ES SDK so that you can localize it. However, before you can localize the for, you you must configure your development environment for customizing Workspace ES as described in Customizing the LiveCycle Workspace ES User Interface and complete the localization customization.

To localize the Share Queue Request form:

  1. Copy the adobe-workspace-src.zip file, which is in one of the following two locations, to a folder in your development environment, such as testwssource:
    • [installdir]/LiveCyle_ES_SDK/misc/Process_Management/Workspace, where [installdir] is the location that LiveCycle ES is installed on the server.
    • [installdir]/LiveCyle_ES_SDK/misc/Process_Management/Workspace, where [installdir] is the location that LiveCycle Workbench ES is installed.
  2. Extract the contents of the adobe-workspace-src.zip file. You should see two subfolders:
    • Workspace: Includes the source code and files that you use to create your own custom version of Workspace ES.
    • LCAs: Contains the source code for the Share Queue Request form.
  3. In Flex Builder, select File > New > Flex Project.
  4. In the New Flex Project dialog box, in the Project name field, type a name for your project, such as ESQueueSharingForm.
  5. Deselect Use default location and click Browse.
  6. In the Select Project Location dialog box, go to the folder where you had extracted the Share Queue Request form in step 2. For example, /testwssource/LCAs/queuesharing.
  7. Delete the default MXML file that is created for you when you create a new Flex project.
  8. Right-click the folder of the language located under the locale folder that you want to localize the text from and select Copy. For example, right-click the en_US folder.
  9. Right-click the locale folder and select Paste.
  10. In the Name Conflict dialog box, type the locale code of the language you are localizing to.For example, es_ES for Spanish.
  11. Open the queuesharing.properties file from the folder that you created in the previous step.
  12. Modify the text in the right-hand side of each property-value pair and when you are done your changes, save the file.
  13. Open the build.xml file and at each approximate line number indicated below make the following changes:
    • Line 28, for the location attribute, put the location where you installed the Flex SDK compatible with LiveCycle ES. (See “Installing the Flex SDK” in the Customizing the LiveCycle Workspace ES User Interface guide.)
      <property name="flex.sdk.home" 
      location="C:\Program Files\Adobe\Flex Builder 3\
      sdks\3.0.1.lc"
      />

    • Line 29, specify the location of the LiveCycle Workspace ES SWC file:specify the location of the LiveCycle Workspace ES SWC file:
      <property name="workspace-runtime.swc"
      location="C:/Adobe/LiveCycle8.2/LiveCycle_ES_SDK/
      misc/Process_Management/Workspace/
      workspace-runtime.swc"
      />

    • Line 73, add your new locale:
      <arg value="-locale=en_US, de_DE, fr_FR,
      ja_JP, es_ES"/>

    • Line 192, add your new locale to compile options:
      <compiler additionalCompilerArguments=
      "-services "${root}/common/services-config.xml"
      -locale en_US fr_FR de_DE ja_JP es_ES
      -source-path+=${basedir}/locale/{locale}"
      copyDependentFiles="true"
      generateAccessible="false"
      strict="true"
      warn="true"
      htmlGenerate="true"
      htmlPlayerVersionCheck="true"
      htmlPlayerVersion="9.0.0" htmlExpressInstall="true"
      htmlHistoryManagement="true" outputFolderPath="bin"
      outputFolderLocation="${gateway.hot-deploy.client}/
      flexform"
      rootURL="${gateway.hot-deploy.url}/flexform"
      sourceFolderPath="src">

  14. In a command line, navigate to the root folder of your Flex project, and type ant to compile the project. You must use the ant command and not the builder that comes with Flex Builder.
  15. In the export folder, which is created after you run the ant command, you will see the queuesharing.swf file. Start LiveCycle Workbench ES and drag the queuesharing.swf folder to the Process Management > Workspace folder and update the existing QueueSharing.swf file in the Resources view. You may need to click Refresh to see the version number increment. The QueueSharing process uses the more recent version of the queuesharing.swf file for all new processes.

To test your updated Share Queue Request form, in a web browser, select the locale that you want to test in the languages settings, such as International Spanish (es_ES), and confirm that when you view the Share Queue Request form in Workspace ES, the localized version of the form is seen.

Note: Before you can test your localized Share Queue Request form, you must localize and deploy the custom Workspace ES application in the same language as you are localizing the Share Queue Request form. The custom Workspace ES application is a separate instance (EAR file) that you can deploy on the LiveCycle ES server. (See Customizing the LiveCycle Workspace ES User Interface.)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

2 Responses to Localizing the Share Queue Request form (queuesharing.swf file)

  1. Nice information on Queue Sharing. What do you mean by Workspace ES application in the same language??

  2. Gilbert Yu says:

    “Workspace ES application in the same language” means that to see your localized form, such as a Spanish one, you must customize Workspace ES to Spanish before you can see the custom form. Your custom Workspace ES is actually a new EAR file that you create and deploy to the application server. You will also access it using a custom workspace such as http://hostname:port/customworkspace instead of the default URL. There are further details about this in the Customizing the LiveCycle Workspace ES User Interface guide.