Development Object URLs

Each development object, property, and script container has a unique URL that can be used for navigation purposes. The URL consists of a hierarchical chain of segments that identify each object in the chain, starting from the main development object. The last segment in the path can be a position in a script container.

Type:Object{/Type:Object{/Type:Object}}{/prop:propId{/pos:Line{,Col}}}

For example: 

ent:ENTITY.MODEL
cpt:COMPONENT
libsnp:LIBRARY
cpt:COMPONENT/ent:ENTITY.MODEL/fld:FIELD/prop:USCRIPT/pos:4,25

Argument

Description

Type

Abbreviation identifying the type of development object.

Object

Name of the development object.

For entities, the name must include the model name. For fields, only the field name is specified.

Types of Object

A URL segment that specifies a main development object is valid on its own, but all other URL segments form part of a hierarchical path that begins with the main object. For example, the following URL specifies the component field of a component entity:

cpt:ORDER/ent:ORDERLINE.SALES/fld:LINE_TOTAL
Object Types
Type:Name Remarks/Example
prj:ProjectName prj:MyTempProj
ent:EntityName The entity name must include the model name: ENTITY.MODEL

ent:Orders.Sales

Note: When specifying entity segments, you only need to specify the target entity. If it is an inner component entity or a modeled subentity, there is no need to specify the hierarchical path of outer entities or modeled super entities.

For Subtype entities, you can enter ent:Subtype.Model to open the editor of the Supertype.

For component entities, you can enter cpt:Component/ent:Entity to open the component editor with the target entity selected.

fld:FieldName The field name must not be qualified with the entity and model name.

ent:Orders.Sales/fld:Order_Num
lbl:LableName ent:Orders.Sales/lbl:Order_Num
key:KeyNumber ent:Orders.Sales/key:1
rel:OneEntityName The complete URL of a relationship is specified as ent:ManyEntity/rel:OneEntity

ent:Orderline.Sales/rel:Orders.Sales
cpt:ComponentName | ModeledComponentName For components and component templates, the object type can be cpt or a code that specifies the type of component:
  • cpt: for any type of component or component template
  • cptdsp for Dynamic Server Pages
  • cptfrm for Forms
  • cptrpt for Reports
  • cptsvc for Services
  • cptesv for Entity Services
  • cptssv for Session Service
  • cptusp for Static Server Pages
libsnp:SnippetLibraryName libsnp:MyLibrary
libinc:IncludeProcLibraryName libinc:MyLibrary
libprc:GlobalProcLibraryName libprc:MyLibrary
snp:SnippetName libsnp:MyLibrary/snp:vtable.html
inc:IncludeScriptName libinc:MyLibrary/inc:errorHandler
prc:GlobalProcScript libprc:MyLibrary/prc:calcVat
prop:LiteralName Literal object property name. For properties representing code containers, you can also specify a position.

Property names for code containers are:

  • UDECLARATIONS—Declarations container for defining constants
  • USCRIPT—Script container for writing ProcScript modules
  • UCOLL_SCRIPT—Collection Script container; only for entities
  • UOCC_SCRIPT—Occurrence Script container; only for occurrences
  • HTMLSKELETON | LAYOUT—HTML layout of dynamic or static server page
  • UTEXT—Script container for IncludeScripts and Global ProcScripts

For example: ent:ORDERS.SALES/prop:UCOLL_SCRIPT
pos:Line,Column Position in a code container. For example:

cpt:ORDERFRM/ent:ORDERS.SALES/fld:BTN_ADD_LINE/prop:USCRIPT/pos:3,4

Related Topics