Adobe Workflow Server 6.2 Patch 6.2.134.0 Readme

Copyright Adobe Systems Incorporated 2004. All rights reserved.


Contents


Purpose of this Patch

This patch resolves the following issues:

Installing the Workflow Server patch 6.2.129 causes the time values that appear in Administrator to be for the GMT time zone, causing the time values to be wrong by a number of hours. After you install this patch, the time values will be for the time zone that your computer uses.

Without this patch, the Participant::className property of the JScript extensions does not properly store the value 'User'. This issue affects only the Japanese language version of Workflow Server.

The value 'User' for Participant::className is translated in Japanese, but the value should be the English text 'User'. After you install this patch, the value is in English text. For more information, see Changing Your Scripts.

Without this patch, the Directory.findAllUsers method of the Workflow Server JScript extensions does not return any participants when the same key name is used to specify more than one search criteria. For example, the following script always returns no participants:

var key = new Array();

var value = new Array();

key[0] = "DisplayName"; value[0] = "Mark Smith";

key[1] = "DisplayName"; value[1] = "George Jones";

oParticipants = Directory.findAllUsers(key,value)

After you install this patch, Directory.findAllUsers functions correctly. For more information about the Directory.findAllUsers method, see the Scripting for Workflow Agent with JScript guide.

Without this patch, the file name of forms must not exceed a certain length. With long file names, work items that use the form cannot be opened from Personal Data. After you install this patch, the maximum length of file names for forms is 255 single-byte characters.

Without this patch, you cannot use Administrator to create new Workflow Server applications with long names. The length of the application name is restricted to 36 single-byte characters. When you attempt to specify a long name for a new application, the error An application with this name already exists. Application names are not case sensitive. Therefore you must specify a different name appears. After you install this patch, the maximum length of file names for applications is 255 single-byte characters.

Without this patch, Workflow Agent inserts the values of several email header fields, such as the values of the To, From, and Date fields, into the email messages that it sends. The email is successfully delivered to the recipient. This behavior occurs only when Workflow Agent uses SMTP mail. For example, when Workflow Agent sends a participant an email to notify them of a new work item, the body of the email contains the header information. After you install this patch, this behavior does not occur.

Without this patch, when Web Access users attempt to search for work items or processes in which they participated, an error may cause the web server to stop running. Also, end users receive a Page Cannot Be Displayed error. Depending on the web server, these searches can cause a stack overflow on the web server. After you install this patch, Web Access users can search without causing errors.

Without this patch, when using parallel routing in subprocesses the flow of information can return to the parent process prematurely.

The following rules govern the behavior of parallel routing and subprocesses:

Without this patch, when parallel routing is used in subprocesses, the subprocess returns to the parent when the first parallel route completes at a task, regardless of whether the other parallel routes are still active. After you install this patch, subprocesses return to the parent only after all active routes in the subprocess are either complete or encounter a return action.

Without this patch, the Terminate method of the Process object of the Workflow Server JScript extensions returns an error when used with processes that you migrated from a previous version of Workflow Server. This method is used to terminate process instances. Process::Terminate is useful when you want to stop parallel routes from running after one of the routes has finished.

After you apply this patch, Process::Terminate behaves as expected for all processes.

Without this patch, Workflow Agent synchronizes the Workflow Server User Directory with Active Directory at 12:00 AM GMT every 24 hours. After you install this patch, the default synchronization time is 1:00 AM for the time zone that your Workflow Agent computer uses.

Synchronization should occur when your system typically experiences low usage. If a time other than 1:00 AM is more suitable for your environment, you can customize the time that synchronization occurs. For more information, you can contact Adobe Customer Support. Technical support for Adobe enterprise products are available at the Adobe Systems corporate web site at http://www.adobe.com.

Without this patch, Workflow Server and Adobe Form Manager 6.0 do not integrate properly. You must install this patch so that you can use Workflow Server with Form Manager 6.0. Form Manager imposes specific design requirements on your new and existing forms and processes. For more information, see Requirements for Integrating with Form Manager 6.0.

For more information about integrating Workflow Server and Form Manager 6.0, see the Form Manager Installation and Configuration Guide.

back to contents


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.

Note: This is not a cumulative patch. Before you install this patch, you must install the previous patch 6.2.129.

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. Stop each Workflow Agent computer in your cluster.
  3. Copy each file that you extracted to the appropriate installation folder, according to the table below.
  4. Restart each Workflow Agent in your cluster.

Note: The files in the extracted location <Extracted Location>\FormServer51 are required only if you are integrating with Form Manager. For more information, see Requirements for Integrating with Form Manager 6.0.

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 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

agent.jsr
Scripting.jsr

<Extracted Location>\StringResources Workflow Agent <install directory>\Workflow Server\StringResources

AcroformWorkflowFields.pdf

AXScriptOM.dll
AXScriptOM.pdb

ePSDKOL.dll
ePSDKOL.pdb

itADM.dll
itADM.pdb

jfApp.dll
jfApp.pdb

jfbpop.dll
jfbpop.pdb

wfBackGround.dll
wfBackGround.pdb

WfDataStore.dll
WfDataStore.pdb

wfEmail.dll
wfEmail.pdb

wfObjects.dll
wfObjects.pdb

wfServices.dll
wfServices.pdb

wfWorkitem.dll
wfWorkitem.pdb

<Extracted Location>

(The folder where you extracted the ZIP file.)

Workflow Agent <install directory>\Workflow Server
trackadvsql.inc
trackingsql.inc
trackprocinstsql.inc
<Extracted Location>\Web Access\Inc Web Access <install directory>\Workflow Server\WebAccess\Inc

itodbc32.dll
itodbc32.pdb

<Extracted Location>\system32 Workflow Agent <Windows install location>\WINNT\System32

back to contents


Changing Your Scripts

If you use the Japanese version of Workflow Server 6.2, you may have to modify the scripts in your process definitions and role definitions after you install this patch.

This patch changes one of the values that is 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 may need to change your script.

After the patch is installed, one of the valid values for Participant::className is User, instead of the Japanese translation for the English word 'User'.

If your scripts use the translation of the English word 'User', then you must change them to use the value 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

}

back to contents


Requirements for Integrating with Form Manager 6.0

After you install this patch, if you are integrating Workflow Server and Form Manager 6.0, you need to perform other tasks to complete the integration:

Copying Additional Files

To integrate with Form Manager, you must copy additional product files to your Workflow Agent computers. If you have not already updated the other product files, you should do so now. For information, see Installing the Patch.

  1. Stop each Workflow Agent in your cluster.
  2. Copy each file from the folder FormServer51 to the appropriate installation folder, according to the table below.
  3. On each Workflow Agent computer, run the BAT file FsRegisterDlls.bat that you copied to the <install directory>\FormServer51 folder.
  4. Restart each Workflow Agent in your cluster.
    File Name Extracted Location Target Computer Installation Folder

    AppContext.dll
    FSInterfaces.dll
    FsRegisterDlls.bat
    FSSoapClient.dll
    FsUnRegisterDlls.bat
    FSWireTransfer.dll
    IoCom.dll
    RequestObject.dll

    <Extracted Location>\FormServer51 Workflow Agent <install directory>\FormServer51

    (You need to create this folder.)

back to Requirements for Integrating with Form Manager 6.0

Configuring Workflow Agent email properties

When you integrate with Form Manager, you must configure the email properties for the Workflow Agent cluster. This configuration allows Workflow Agent to use email only when integrated with Form Manager.

On a Workflow Agent computer, start Configuration Wizard and use it to change the current e-mail configuration. You need to specify the following connection parameters for Form Server:

Note: the name of the wfForms folder is a property you can change in Form Manager. You should ensure that you have the correct name for this folder. For more information, see the Form Manager Installation and Configuration Guide.

back to Requirements for Integrating with Form Manager 6.0

Migrating XFT forms for use with Form Manager

When you integrate Workflow Server with Form Manager, to use your legacy .xft forms you first need to modify them:

back to Requirements for Integrating with Form Manager 6.0

Using XDP forms with Workflow Designer

Workflow Designer cannot read .xdp form files that are created in Adobe Designer 6.0. Previous versions of Adobe Designer saved forms in the .xft file format, which Process Designer can read. This patch does not update Workflow Designer to read .xdp files.  Because Workflow Agent supports XDP files, you can use XDP forms in your processes.

With supported form types, Workflow Designer automatically populates the Search Fields tab of the process properties dialog box with field names. For XDP forms, Workflow Designer does not populate the Search Fields tab. To specify fields to use for searching on XDP forms, use the Custom Field Name box on the Search Fields tab. You can type any field name in the box. If the field with this name is on your XDP forms, Workflow Agent will use the field for searching. The field name is case-sensitive.

Note: when you specify an XDP file as a start form, a message appears that indicates that Workflow Designer could not find any search fields on the form.

For more information about specifying start forms and search fields, see the Using Workflow Server Designer guide.

back to Requirements for Integrating with Form Manager 6.0

Start forms must be specified in process definitions

In Workflow Designer, to work with Form Manager you must specify the start forms to use for a process, and in Form Manager the start forms must be associated with the process. If you do not specify the start forms in the process definition, Workflow Server is unable to locate the appropriate form to use in the Form Manager repository.

Also, to improve performance, in Workflow Designer you should specify the Form Name property of start forms to be the same as the file name of the start form (without the file name extension). For example, if you specify the file GeneralRequest.pdf as a start form, the Form Name property should be GeneralRequest. This configuration minimizes the number of queries that Workflow Server performs to locate the form in the Form Manager repository, and maximizes performance.

back to Requirements for Integrating with Form Manager 6.0

Designing subforms for use with Form Manager 6.0

Forms that include subform objects can prevent Workflow Server from accessing form data. If you want to use forms that include subforms, the subform objects must use the default value for their Name property (untitled_Subform). If a subform object has a different name, Workflow Agent cannot read any data in that subform, or beyond the subform.

Form data is represented internally by using the Adobe XML Forms Architecture (XFA) Data DOM model. The XFA Data DOM uses a tree structure to represent data, where each node in the tree represents an object on the form.

For more information about subform objects, see the Adobe Designer 6.0 Help.

For more information about the XFA Data DOM, see the Data Handling for Workflow Server guide.

back to Requirements for Integrating with Form Manager 6.0

Configuring binding of workflow objects on forms

If you are creating workflow forms in Designer 6.0 to use with Form Manager 6.0, you must modify the properties of some of the objects in the Workflow Server Fields library. The value for the Default Binding property of the following objects must be changed to Global:

You must set the Default Binding to Global to ensure that form data is properly passed from task to task in the workflow.

For more information about using Designer, see the Adobe Designer 6.0 Help.

back to Requirements for Integrating with Form Manager 6.0

Creating native PDF forms to use with Form Manager

Native PDF forms must include specific fields to work with Workflow Server and Form Manager. Your native PDF forms must include the following three fields:

Field Name Type Description
JFWF_ACTION Combo box Lists the actions available for completing the work item. This field also includes a calculation script that initializes the form.

If the task provides only one action, you can hide this field.

Submit Button Submits the form to Workflow Agent.

If your PDF form already has a submit button, modify the existing button to include the script from this button. This new script should be processed last.

FSTARGETURL_ Text field (hidden) Used by Form Manager and Workflow Agent to store information required for routing.
JFWF_CHOICE Text field (hidden) Used by Form Manager and Workflow Agent to store information required for routing.
FSAPPLICATIONDATA_ Text field (hidden) Used by Form Manager and Workflow Agent to store information required for routing.

You can copy the fields from the file AcroformWorkflowFields.pdf that is included in this patch. The fields in this document include the required script. You must use Adobe Acrobat Professional, version 5.0 or later, to copy the fields into your PDF form.

Note: A similar file is installed with Workflow Server 6.2, named NativefPDFFields.pdf. You should still use the fields from that file if you are using Workflow Server without Form Manager.

To deploy your forms, you publish them in the workflow forms directory of the Form Manager repository. The default name of this directory is wfForms.

back to Requirements for Integrating with Form Manager 6.0

Support for Adobe Reader Users

To allow Adobe Reader users to view form data that has been merged with native PDF forms, you need to apply usage rights to the form with Adobe Reader Extensions Server. You need to apply the following usage rights to your native PDF forms:

Also, you should set the draft level to Final so that the Draft watermark does not appear on the form.

back to Requirements for Integrating with Form Manager 6.0

Migrating users to Form Manager

Web Access cannot read the new format for packaging data that Form Manager uses. When you integrate with Form Manager, end users cannot use Web Access to process work items. Opening work items in Web Access that originated from Form Manager results in the loss of data.

Process administrators should still use Web Access to run reports. Form Manager does not provide a reporting tool.

Also, when using Form Manager, if you are using a legacy Workflow Server database, end users cannot search for work items or process instances that they processed using Web Access. End users will see the work items that were in their Worklist, as well as in their Personal Data, and work item history:

back to Requirements for Integrating with Form Manager 6.0

Create duplicate forms to start multiple processes

Form Manager requires that you specify the workflow process that a form is associated with. Although Adobe Workflow Server allows one form to start several workflow processes, Form Manager supports associating a form with only one process.

If you want to associate a form with more than one process, you need to save the form using different file names and associate each file with a different process. To deploy your forms, you publish them in the workflow forms directory of the Form Manager repository. The default name of this directory is wfForms.

back to Requirements for Integrating with Form Manager 6.0

Store forms in the Form Manager Repository

All forms for processes must be stored in a specific directory in the Form Manager repository. The default name of this directory is wfForms.

You can change the name of this directory if desired. For more information, see the Form Manager Installation and Configuration Guide.

back to contents


Readme File

Adobe Workflow Server 6.2 Patch 6.2.134.0
July 2004

7/21/2004  04:05 PM