Adobe Workflow Server 6.2 Patch 6.2.129 Readme

Copyright Adobe Systems Incorporated 2004. All rights reserved.


Purpose of this Patch

This patch resolves the following issues:

Using processes in Test mode when e-mail notifications are sent causes work items to stall.

After you install this patch, you may be required to modify your Form Client or Form Server forms that include radio buttons. For more information, see Modifying Your Form Client and Form Server Forms.

When using native PDF forms, field values with a value of 'X' are not persisted. When a value of 'X' is entered in a field on a native PDF form, or if the value 'X' in field data is merged with a native PDF form, the fields that are to hold 'X' instead hold no value.

For non-English versions of Workflow Server, and for English versions that are installed in non-English Windows locales, the Participant::className property of the JScript extensions does not properly store the values 'User' and 'XMLDestination'. This issue affects English versions that are installed in the following locales, and the following language versions of Workflow Server:

For these languages, the values 'User' and 'XMLDestination' for Participant::className are translated in the respective language, but the values should be the English text 'User' and 'XMLDestination'. For more information, see Changing Your Scripts.

When used in a subprocess, the WorkItem::startRendezvous method of the WorkItem object of the Workflow Server JScript extensions does not affect the behavior of WorkItem objects.

In the PDF version of the General Request sample form, the Reset Form button does not clear the form of data that the user enters. This patch replaces the General Request form with a version that does not include the Reset Form button.

The native PDF form of the General Request application does not properly persist form data when submitted using e-mail.

After applying patch 6.2.122, the Routing Slip sample application always routes work items back to the originator after completion. This behavior occurs even when the "No Notification" option is selected.

SQL errors have been observed in some clustered configurations of Workflow Server. The error appears in the Microsoft SQL Server event log, and in the Workflow Agent log. The error causes Workflow Agent to suspend processing for less than one minute.

In Administrator, date values appear in English regardless of the language version you installed, or the Windows locale that you used. This patch causes dates to appear in the correct language in all areas of Administrator, except in the Properties dialog box for applications.

The German translation for the Web Access column named Completed By is changed to a more suitable word.

When used in conjunction with Adobe Form Server, Web Access provides validation messages in English regardless of the language version you installed, or the Windows locale that you used.

If field names on native PDF forms use double-byte characters, the field data is not persisted in work items.

For the Japanese version of Workflow Server, and for the English version installed in the Japanese Windows locale, work Item attachments do not persist when attachments are given the access property of 'Update'. When a Web Access user attaches a file and sets the access property to 'Update', the next work item in the workflow does not include the attachment.

In a Japanese environment, Web Access does not properly interpret the Yen symbol when it appears in a field on native PDF forms.

For the Japanese version of Web Access, the Yen symbol does not appear correctly to end users in their Web browsers.

Note: The updated file WebAccess.css that fixes this issue apples only to the Japanese version of Workflow Server. Do not install this file if you are using the English version of Workflow Server.

The Agent::createPDF method of the Workflow Server JScript extensions causes errors when field data includes Japanese characters.

To resolve these issues, install this patch. You may also be required to modify your forms and your Workflow Server scripts:


Installing the Patch

The files in this patch are replacements for older versions that are installed with Adobe Workflow Server 6.2. Before you install the patch, you should create backup copies of the older versions that are currently installed.

You install some of the files in this patch on the Workflow Agent computer, and some on the Web Access computer. For files that are installed on the Workflow Agent computer, you must install the files on each computer that belongs to your Workflow Agent cluster. Before you install the files, Workflow Agent or Web Access must already be installed on the target computer.

To install the patch:

  1. Extract all the files in the Zip file to your hard disc.
  2. Copy each file that you extracted to the appropriate installation folder, according to the table below.

After you install the patch, you may be required to make changes to your forms and to your Workflow Server scripts. For more information, see Modifying Your Form Client and Form Server Forms, and Changing Your Scripts.

The files that this patch provides are packaged in a ZIP file. The following table provides information about the location of the files when you extract them, and the location where you must copy the files to install them:

File Name Extracted Location Target Computer Installation Folder
wfWorkitem.dll

wfDataMerge.dll

AXScriptOM.dll

itADM.dll

wfObjects.dll

ePSDKOL.dll

wfWorkitem.pdb

wfDataMerge.pdb

AXScriptOM.pdb

itADM.pdb

wfObjects.pdb

ePSDKOL.pdb

<Extracted Location>

(The folder where you extracted the zip file.)

Workflow Agent <install directory>\Adobe Workflow Server
Scripting.jsr <Extracted Location>\StringResources Workflow Agent <install directory>\Adobe Workflow Server\StringResources
Routingzettle.jwf <Extracted Location>\Intrinsics\processes\de Workflow Agent <install directory>/Intrinsics
Routing Slip.jwf <Extracted Location>\Intrinsics\processes\en Workflow Agent <install directory>/Intrinsics
Fiche de circulation.jwf <Extracted Location>\Intrinsics\processes\fr Workflow Agent <install directory>/Intrinsics
Routing Slip.jwf <Extracted Location>\Intrinsics\processes\ja Workflow Agent <install directory>/Intrinsics
Attachment.asp

FdfGetPdf.asp

SubmitForm.asp

WorkOnTask.asp

<Extracted Location>\Web Access\Web Web Access <install directory>\Adobe Workflow Server\Web Access\Web
WebAccess.jsr <Extracted Location>\Web Access\Strings Web Access <install directory>\Adobe Workflow Server\Web Access\Strings
JfITEnvelopeCtrl.cab <Extracted Location>\Web Access\CabFiles Web Access <install directory>\Adobe Workflow Server\Web Access\Web\CabFiles
Multiple versions of the following files, for different languages, and different formats (PDF, Form Server, Form Client):

GenReq.xft

RSlipPar.xft

RSlipRes.xft

RSlipSer.xft

RSlipSt.xft

<Extracted Location>\WebAccess\Web\forms\<Format>\<Language>

where:

<Format> is the form format.

<Language> is the abbreviation for the language of the form.

For example, the German form template for Form Client is located in the folder <Extracted Location>\WebAccess\Web\forms\Form Client\Forms\de.

Web Access The format of the form determines the installation folder:

PDF forms:

<install directory>\WebAccess\Web\Forms/PDF

Form Client forms:

<install directory>\WebAccess\Web\Forms\Form Client\Forms

Form Server forms:

<install directory>\WebAccess\Web\Forms\Form Server\Forms

Process Instances.rpt

Work Items.rpt

<Extracted Location>\WebAccess\reports\Ja Web Access <install directory>\WebAccess\Reports\Ja
Note: Install the following file, WebAccess.css, only if you use the Japanese version of Workflow Server. Do not install this file if you use the English version of Workflow Server.
Webaccess.css <Extracted Location>\WebAccess\Web Web Access <install directory>\Adobe Workflow Server\Web Access\Web


Modifying Your Form Client and Form Server Forms

You may need to add script to your Form Client and Form Server forms to enable data to merge properly from form to form:

For example, your Adobe Workflow Server solution provides a form in native PDF and Form Client format. The form includes radio buttons. You must modify your Form Client form to ensure the data can be routed to any user, regardless of the type of form they use.

Your forms may require extra script to accommodate different conventions that different types of forms use for naming radio button objects, and for establishing groups of mutually exclusive radio buttons:

The following table includes example values of the GroupName, Name, and Value properties of radio buttons to show their relationship across different form types. The example values are for a set of 3 mutually exclusive radio buttons:

Form Type GroupName Radio Button Names Value
Form Client or Form Server RadioGroup1 FFRadioButton1
RadioGroup1 FFRadioButton2
RadioGroup1 FFRadioButton3
PDF or HTML
RadioGroup1 FFRadioButton1

RadioGroup1 FFRadioButton2

RadioGroup1 FFRadioButton3

To modify your form, you must insert a hidden field for each group of radio buttons, and add new scripts. You must also alter the field binding properties of each radio button.

Note: If you use only Form Client forms, you do not need to alter your Form Client forms.

You use a different procedure to modify your Form Client forms than to modify your Form Server forms .

To modify your Form Client forms:

  1. Open your form in Adobe Form Designer.
  2. For each radio button group, create a hidden field that has a name that is unique to the form. This field will store the name of the selected radio button for the group.
  3. For each radio button, add script to the OnClick event that sets the value of the associated hidden field to the Name property of the radio button. For example:

    if (this.Enabled){

    <HiddenField1>.Value = this.Name; /* sets the field value to the name of the selected radio button. */

    }

    Where <HiddenField1> is the value of the Name property of the hidden field you created in step 2.

    Note: If you send form data to Adobe Central, radio buttons must have a value of "X" when enabled, and must have no value if it they are not enabled.

  4. For each radio button, right-click the radio button and click Object Properties.
  5. On the Field Binding tab, clear Automatically bind to field data source check box, and click OK.
  6. For the OnCalculate event of the hidden field you created for the radio button group, add script that sets the correct value for each radio button when the form loads. For example:

    Form.Find(this.Value).Value = Form.Find(this.Value).OnValue;

  7. For each radio button object and hidden field object that you added, ensure that Run script on client is selected so that the script runs on the client.
  8. Save and deploy your form.

To modify your Form Server forms:

  1. Open your form in Adobe Form Designer.
  2. For each radio button group, create a hidden field that has a name that is unique to the form. This field will store the name of the selected radio button for the group.
  3. For each radio button, add script to the OnCalculate event that sets the value of the associated hidden field to the Name property of the radio button. For example:

    if (this.Value != 0){

    <HiddenField1>.Value = this.Name; /* sets the field value to the name of the selected radio button. */

    }

    Where <HiddenField1> is the value of the Name property of the hidden field you created in step 2.

    Note: If you send form data to Adobe Central, radio buttons must have a value of "X" when enabled, and must have no value if it they are not enabled.

  4. For each radio button, right-click the radio button and click Object Properties.
  5. On the Field Binding tab, clear Automatically bind to field data source check box, and click OK.
  6. For the OnCalculate event of the hidden field you created for the radio button group, add script that sets the correct value for each radio button when the form loads. For example:
  7. if (this.Value != ""){

    Form.Find(this.Value).Value = "<OnValue>"

    }

    Where <OnValue> is the value of the OnValue property of the radio button.

  8. For each radio button object and hidden field object that you added, select the object and clear Run script on client so that the script runs on the server.
  9. Save and deploy your form.

Changing Your Scripts

If you use a non-English version of Workflow Server 6.2, or if you install the English version in a Windows computer that uses a non-English locale, you may have to modify the scripts in your process definitions and role definitions after you install this patch.

This patch changes the values that are valid for the Participant::className property of the Workflow Server JScript extensions. If you use script that retrieves the value of Participant::className and evaluates that value, you must change your script.

After the patch is installed, the valid values for Participant::className are:

Previously, the valid values were the translated word for the English words 'XMLDestination' and 'User'.

If your scripts use the translation of the English words 'XMLDestination' or 'User', then you must change them to use the values XMLDestination and User. For example, your script may use the value of Participant::className to make decisions about what the script should do next, similar to:

if (oParticipant.className == "User") {

//code to execute if the participant is a user

}

else if (oParticipant.className == "XMLDestination") {

//code to execute if the participant is an XML destination object

}


Readme File

Adobe Workflow Server 6.2 Patch 6.2.129
March 2004

3/15/2004  08:13 AM