Publishing locations

Specify the publishing paths in the DOCUMENT.ATTACHMENT File Location.

• The @DFLT entry is optional. It defines the default location for all published attachments.
• You can designate separate publishing paths for different objects and Doc codes.
• Use object .@DFLT (for example ITEM.@DFLT) to place the attachments for all function codes for an object in one directory.
• Use object.functioncode (for example FORMULA.CHANGES) if a function code requires its own directory.
• Avoid using mapped drives. Use UNC file paths instead.

When you save the attachments in the object’s form, those attachments are published. They are published to the file location that is designated in DOCUMENT.ATTACHMENT.

In this example, the Formula attachments for the CHANGES Doc code are published to this server location: \\us-sbo-qa8\docs. In Windows Explorer, you can see a timestamp for these files. The timestamp keeps the update versions unique. The version number is not visible to Optiva users, but it is visible in the publishing location.