The DM_ Prefix

You can use the DM_ prefix in front of the following bookmark names:

Bookmark with Prefix Explanation
DM_DocHeader_Project Project ID Code with mask
DM_DocHeader_ProjEntity DM_DocItemTask_ProjEntity Cost Code with mask

 

The RR_ and RC_ Prefixes

You can use the RR_ or RC_ prefix in front of any bookmarks that include the following aliases (ex: RR_DocItemTask_GLSub or RR_SPRLineDetails_ItemNumber.

Note: The RR_ and RC_ prefixes often include prefix extensions.

RR_CIAllocSummary_
RR_CICost
RR_CIDetail_
RR_CISummary_
RR_DocAddr_
RR_DocAlert_
RR_DocCompliance_
RR_DocDates_
RR_DocInclusion_
RR_Inclusion_
RR_Exclusion_
RR_LegalAtt_
RR_OtherClause_
RR_DocInstruction
RR_DocItem_
RR_DocItemComment_
RR_DocItemTask
RR_DocMeetingAttendee_
RR_DocRevision_
RR_DocRevisionList_
RR_DocRevItem_
RR_DocRoute
RR_DocRouteTransmittal
RR_SPRLineDetails_
RR_SubcontractLineIdleDetails_

 

DV_ Bookmarks for Internal Data

Use the DV_ prefix in front of the following bookmark names to retrieve the following information.

Bookmark with Prefix Explanation
DV_DocAttachedFile_CatType The type according to an attached file’s Properties or the Doc type of an attached document.
DV_DocAttachedFile_CheckOutUser The name of the person who last checked out an attached file.
DV_DocAttachedFile_ContainerKey The folder (if any) containing an attached file.
DV_DocHeader_DocTypeKey The site-given name of the Doc Type.
DV_DocHeader_Priority The priority level of a document
DV_DocHeader_ProjectCompany The company/division code on the Project Setup
DV_DocHeader_ProjectCompanyname The internal company/division name associated with the Project Setup
DV_DocHeader_ProjectPO The purchase order number (for integrated sites only)
DV_DocHeader_ProjEntity

DV_DocItemTask_ProjEntity

Description of the Cost Code
DV_DocHeader_Source Description of the Source Code
DV_DocHeader_Status Description of the Status
DV_DocHeader_Subcontract

DV_DocItemTask_Subcontract

The title of the commitment
DV_DocHeader_SubcontractVendor The Vendor ID
DV_DocHeader_SubcontractVendorCompany The Vendor Company name
DV_DocHeader_SubcontractExpenseAmount The amount of the commitment
DV_DocHeader_SubcontractStatus The Commitment status code
DV_DocHeader_SubType Description of the Subtype
DV_DocItem_Drawings Description of the Item’s Drawings field
DV_DocItem_FieldMockup Description of the Item’s Mockup field
DV_DocItem_Guarantee Description of the Item’s Guarantee field
DV_DocItem_ItemStatus Description of the Item Status
DV_DocItem_ItemSource Description of the Item Source
DV_DocItem_ItemType Description of the Item Type
DV_DocItem_MixDesign Description of the Item’s Design field
DV_DocItem_ProductData Description of the Item’s Data field
DV_DocItem_Samples Description of the Item’s Samples field
DV_DocItem_Schedule Description of the Item’s Schedule field
DV_DocItem_TestReport Description of the Item’s Reports field

 

Tags:

Related Post

Compliance TypesCompliance Types

During implementation some Compliance requirement types may be configured as requirements for certain Doc Types such as Commitments, Pay Requests, and Vendors. Other Compliance types may be set up as