The information in this article applies to product: e-Work 6.6.3
Issues Resolved by This Release
- The Designer does not open if .NET framework Version 2.0 is installed on the same computer. (PF26742)
- In an XEP file, if a new script has the same name as an existing script, the contents of the existing script are overwritten. (SR21231, SR21208, PF26290)
As a result of this fix, note the following changed behavior:
The following characters are no longer allowed in script names: \\ : \* ? " < > | /
Pressing the Insert key in the Scripts dialog launches the Add Script dialog.
Process designers are prevented from creating scripts with duplicate names in maps and forms. It is possible to create scripts with duplicate names in Common provided that one is a procedure client script and one is a procedure server script or that a script with that name already exists in a used library.
Process designers are not able to drag and drop scripts if it would allow scripts with duplicate names.
- Using a backslash in a script name can cause the script reference to be lost. (PF26279)
- Using the Insert key followed by another keystroke in the Scripts dialog causes an error. (PF26517)
- Running a JScript .NET script on an Engine server that has .NET framework Version 2.0 installed results in an error. In addition, if the Engine is installed after the .NET framework, the Engine fails to start. (PF26743)
- External forms cannot be used as login dialogs. (SR21980, PF26698)
