Customization Points

Table 1. <primaryAttachment> tag attributes
Parameter	Default Value	Possible Values	Req?	Description
allowFile	true	True/False	no	Allows the Local File option to be displayed.
allowUrl	true	True/False	no	Allows the URL Link option to be displayed.
allowExternal	true	True/False	no	Allows the External Storage option to be displayed.
fixedFilePath	null	Valid file path	no	Renders the file path specified instead of allowing the user to choose the file. If fixedFileUpload param on this tag and the forceApplet param on the fileSelectionAndUpload Applet tag are both set this can be used to force the specified file to be uploaded and attached to the object.
forceApplet	False	True/False	no	Determines if we should force the applet to be rendered regardless of the upload mechanism preference

In order to hide primary content for an object you will need to do the reverse of the above five procedural steps by removing those entries from the wizards, jsps, and the action model. You will also need to modify \codebase\netmarkets\jsp\wip\checkin_step.jsp and remove the “if” block included for the FormatContentHolder interface associated with the page (leave the “getRespectiveNonFormatContentHolderPage” included there).

For documents only (not other FormatContentHolders) you will find similar entries in the wizard jsps but they may slightly vary by referring to an MSOI tag which extends the attachments tags. Removing these tags will remove primary attachments from documents but it will also render desktop integration useless since desktop integration depends on having file primary attachments. You will also need to remove the createMulti action from all action models since it depends on primary content.

On the primaryAttachment tag you may set the allowUrl and allowExternal attributes to false. In the event that you wish to disable url and external data options for documents only you can modify the following file.