The information in this article applies to product: e-Work 6.x
Issue
On Windows Server 2003 and Windows XP SP2, file permissions are not always retained on a procedure file when it is saved.
For example, e-Work procedures are stored in a directory named Procedures. A Windows group named Developers is given Modify, Read, ... permissions to this directory. The permissions are applied to the folder and all sub-folders and files.
From the Designer, a procedure is saved to the Procedures directory. Go to Properties --> Security for the .XEP or .EPC file that was just saved. Note that the group Developers is not listed.
Resolution
This behavior has been observed on Windows Server 2003 and some installations of Windows XP SP2. The effective file permissions on the procedure file are determined by the permissions set on the Temp directory of the Windows user logged in on the machine.
For example, if user jjones is logged in, the group Developers would need to have the appropriate permissions added to this directory: C:\\Documents and Settings\\jjones\\Local Settings\\Temp. These permissions would then be applied to the procedure when it is saved to the Procedures directory.
