Configuring Document Management for Drawings

An ARCHIBUS Administrator may need to review the following material to configure ARCHIBUS Document Management for Drawings:

Configuring the Folder where Drawings and Enterprise Graphics Are Stored

If Document Management for Drawings is enabled, then the system stores drawings and enterprise graphics in a central location (the Web Central Drawing Files folder), which is specified in the webapps\archibus\WEB-INF\config\drawing-management.properties file.

To set this folder, edit these settings in the drawing-management.properties file.

drawingManagement.drawings.folder=$Path{WebAppPath}/projects/hq/drawings
drawingManagement.enterpriseGraphics.folder=$Path{WebAppPath}/projects/hq/enterprise-graphics

All drawings for all projects are stored in the same folder.

If Document Management for Drawings is enabled, the System Administrator can stop the sharing of the Smart Client Drawing Files folder (such as, \aiprojects\hq\drawings) since the team will not use this folder; instead, they use the Web Central Drawing Files folder. For information on how to stop sharing, see the following topic in ARCHIBUS Help:

Smart Client User's Guide/Setup/Start of Stop Sharing your Workstation

Using Virtual-Private ARCHIBUS Settings on the Drawing List

CAD Managers often divide responsibility for certain drawings in the drawing set by building or site, with each building or site being managed by a different CAD specialist or drafting team. In this scenario, the ARCHIBUS Administrator will establish a Virtual-Private ARCHIBUS restriction on the Drawing List (afm_dwgs) table. Each CAD specialist or team sees only the files that they are responsible for in the Drawing List.

To establish such restriction::

Open the Administration / ARCHIBUS System Administration / ARCHIBUS Administrator / Add or Edit User Roles view.
Select CAD Specialist role.
Enter the appropriate restriction in the VPA Restriction field.

The HQ sample project has a sample role, Z-VPA-DWGS, that restricts to drawings for building HQ, such as HQ17.DWG, HQ18.DWG, and so on. This example is below. Use this format when you have a separate role for each building:

<restriction
type="forFields"
sql="#ASQL_VPAField() LIKE 'HQ%'">
<title translatable="true">Fields-Named Restriction on dwg_ name</title>
<field name="dwg_name"/>
/restriction>

Alternately, you can use a single role for CAD Specialists. To do so, enter the building names for which each specialist has access in each of the VPA Options fields of the ARCHIBUS Users (afm_users) record:

<restriction
type="forFields"
sql="#ASQL_VPAField() LIKE #ASQL_ GetAfmUserCachedValue('vpa_option1') OR
#ASQL_VPAField() LIKE #ASQL_GetAfmUserCachedValue('vpa_option2') OR
#ASQL_VPAField() LIKE (#ASQL_GetAfmUserCachedValue('vpa_option3'))">
<title translatable="true">Fields-Named Restriction on dwg_name</title>
<field name="dwg_name"/>
</restriction>

If the deployment does not have a naming convention for drawing files, use the Building Code in the Space Hierarchy fields. The Building and Floor Code are separated by a semi-colon in this field. In Oracle, the VPA restriction would be:

<restriction
type="forFields"
sql="SUBSTR(space_hier_field_values,1,INSTR(space_hier_field_values,';')-1)=’HQ’”
<title translatable="true">Fields-Named Restriction on dwg_name</title>
<field name="dwg_name"/>
</restriction>

See Also:

In ARCHIBUS Help, Web Central User's Guide/CAD Manager/Overview

ARCHIBUS Administrator/Advanced Application Security/VPA Security