Checking File Names
The file “Sitedef.ini” found in the root folder in which the site is generated (Intranet is the default) indicates for each object the correspondence between its absolute identifier and the name of the file describing its main page.
For each object in the site, a paragraph like this is created:
[245D261330A3002D]
PageName = 245D261330A3002D
Available = Yes
Object = Sales Department Org-Unit
MetaClass = Org-Unit
Object identifier
The identifier for the object is given inside brackets. This identifier never changes once the object is created, in order to retain all links and properties even if the object is renamed.
File naming rules
The PageName value indicates the name of the main page. When the site for the object with this absolute identifier is regenerated, this string of characters is used to name the HTML files, followed by a letter and then the HTM extension. PageName is used even if the object name has been changed. This ensures that when a site points to another site, links remain valid (the indicated address remains constant).
|
Main page of the object
|
HexaIdAbs of the occurrence
|
|
Menu page of the object
|
HexaIdAbs of the occurrence followed by "_M"
|
|
Contents page of the object
|
HexaIdAbs of the occurrence followed by "_C"
|
|
Diagram page associated with the object (displayed in object page)
|
HexaIdAbs of the occurrence
followed by HexaIdAbs of the diagram
followed by "_D"
|
|
other diagram page (independent of the object page)
|
HexaIdAbs of the occurrence
followed by HexaIdAbs of the diagram
|
The generated HTML pages are built of several frames that are called by the main page. There is an HTM file specifying the contents of each frame. For example, for the object “Sales Department Org-Unit”, the files generated could be “245D261330A3002D.htm”, which is the name of the main page describing the object and is fixed, supplemented for example by “245D261330A3002D_M.htm", "245D261330A3002D_D", etc.Respecting specific naming rules
When specific rules must be followed for naming pages, simply perform an initial generation, modify the file names to comply with the rules, and regenerate the site so that the generated file names are in compliance with the rules in effect. For example, simply modifying the above paragraph to look like this means the HTML files will have the prefix A1_DR instead of DIREC2:
[245D261330A3002D]
PageName = A1_DR
Available = Yes
Object = Sales Department Org-Unit
MetaClass = Org-Unit
The line “Available = Yes” indicates that the object is still present in the site. If the object was included during a previous generation but is no longer part of the site (such as an organizational process now deleted from the project), this line becomes “Available = No”.
As the file “Sitedef.ini” is intended to ensure that file names are retained during successive page generation operations, though an object may no longer be referenced in the site it is still retained in this file. If the object is later reincluded, the page names will remain identical.The object type and name are then indicated in the “Object” line (in the example, “Object = Sales Department Org-Unit”).
Index page naming rules
An index page comprises a menu page (_M) and a content page (_C).
Menu page
|
Naming rule
|
Index page name
|
|---|---|
|
Without naming rule (without SiteDef.ini)
|
ParentPageName_M.htm
|
|
With specific naming rule (with Sitedef.ini)
|
IndexPageIdentifier_M.htm
|
Content page
|
Naming rule
|
Index page name
|
|---|---|
|
Without naming rule (without SiteDef.ini)
|
ParentPageName_C.htm
|
|
With specific naming rule (with Sitedef.ini)
|
IndexPageIdentifier_C.htm
|
When several index pages are specified for the same object type (alphabetical index, index by characteristic, etc.), the index pages are suffixed by an order number (for example, xxxxx_C_PIDX1.htm, xxxx_C_PIDX2.htm).Image naming rules
Images are named as follows:
• HexaIdAbs of described object _HexaIdAbs of diagram_I.png (or .bmp, .svg, .jpg depending on image format)