Renaming Text Type Objects

In AssetWise, you can specify what text to display. Text may be one of the following four types:

Text Type	Use
All lowercase display text	For text within sentences
Normal display text with each first letter capitalized	For labels
Header display text	For text used in headers; this text is usually singular
Lowercase header display text	For text used in some labels and headers; this text is usually singular

Tag -> Asset

In object.types.json, the "Tag" becomes "Asset" in ALIM.

{
   "id": "assets",
   "displayText": "ASSETS",
   "displayTextLowercase": "ASSETS_LOWERCASE",
   "headerDisplayText": "ASSET",
   "headerDisplayTextLowercase": "ASSET_LOWERCASE",
   "objectType": 212,
   "baseClass": "Tag",
   "subHeaderProperties": "ClassName,Name",
   "dynamicDisplay": {
     "useHierarchy": true                
   },
   "gridId": "eB_Tag", ...
}

Note: Code above is abbreviated, and is for example purposes only.

Value	Details
ObjectType	Represents a numeric value that is assigned to asset types. It is a WUIF concept. The complete list of objectType unbers for the eB.WUIFPlugin may be found in eB.enums.ts.
dynamicDisplay.useHierarchy	for turning on and off the Hierarchy tree view. Because "assets" can be hierarchy of instances and ALIM should have a tree view available when showing instance details. The dyanmicDisplay.useHierarchy property is typically true.
SysType	an optional configuration property that is used to sub-classify an object type.
gridId	the unique id for the grid to use for this object type. For example, suppose ALIM queries for assets. The list of assets returned from the datasource will be presented in a grid. Which grid? Because the object type being queried is Tag and the objectType is 212, the default grid that will be used to present the results to the user will be the "eB_Tag" grid. Grids are defined in a separate file, grids.json.
isSearchLookupDisabled	set to true will prevent the object type from being searched by the application. The object type will still be usable throughout the application, however, it will be excluded from any search features, for example, the quick search dropdown.
foreignKeys	class-specific configuration for any foreign key controls used on forms for that class. The ellipsis button opens a model in which the user chooses an instance of the foreign class.

TaskOrder

Task order is object type #341. Task order can have an association with Commercial Contract and Budget. The form builder needs to know how to build the foreign key elements and what class is being displayed.

For example, the following code

"foreignKeys": [
        {
          "parameter": "eB:CommercialContract",
          "keyId": "ContractId",
          "format": "{{properties.Name}}",
          "schema": "$CUSTOMER_SCHEMA",
          "gridId": "eB_ContractSelection",
          "fkRouteId": "eB_ContractEdit"
        },
        {
          "parameter": "eB:Budget",
          "keyId": "DefaultBudgetId",
          "format": "{{properties.Code}}",
          "schema": "$CUSTOMER_SCHEMA",
          "gridId": "eB_BudgetApprovedSelection",
          "fkRouteId": "eB_BudgetEdit"
        }
      ]

results in: