Business Layers

A business layer represents the Web access point, or a feature service of a specific geometry context. A geo object can have single or multiple business layers. The framework UI shows a business layer as one logical layer on the map, which you can toggle on or off and change its transparency.

Note

Feature service is a REST service based on specifications provided by Esri.

The following section provides detailed explanations of all the fields and options that you’ll need to define:

Business Layer ID: Displays the ID of the business layer assigned to the geo object.
Geo Object ID: Enter ID of the parent geo object the business layer is assigned to (display only field).
Geometry Context ID: Enter geometry context ID used for the business layer. It is used as a geo filter (business layer has an additional filter condition, for example, “Context=3”) for queries in addition to the filters in the Filters node. If a context is specified, only geometries with that specific context will be displayed on the layer on the map.

For more information on filters, see the corresponding section under Geo Objects.
Edit Indicator: If checked, it is used as an edit relevant layer for its parent geo object. If a business layer is marked as edit relevant, it is used for create, update and delete operations for the geo object. You cannot maintain an edit layer in the UI Customizing of the business layer group hierarchy and it does not appear on the business layers on the UI.

Note
Only one edit relevant layer per geo object is allowed.

It is recommended that you create a legend which distinguishes this layer from others so that it is easier to recognize it on the map. It is not recommended to maintain a geometry context for this layer as you’ll not be able to create, update or delete other contexts besides the one that has been maintained.
Search Indicator: If checked, it is used as a search relevant layer for its parent geo object in the Geo Explorer and the Geo Editor. If a business layer is marked as search relevant, it is used for searching geo objects.

Note
Only one search relevant layer per geo object is allowed.

It is recommended (but not mandatory) that you create a legend which distinguishes this layer from others so that it easier to recognize the found objects on the map. It is not recommended to maintain a context for this search layer as you’ll not be able to find geometries that belong to other contexts than the one that has been maintained in the search layer.

In certain conditions it may be relevant to only see the geometries from a certain context in a search result and therefore, a context may be specified. This will, however, prevent display of geometries with other contexts in all search functions. For example, if the geo object only has “default” and “redlining” contexts, you may wish to exclude redlining geometries from all searches by using a business layer with the default context specified as the search layer.
Description: Enter a meaningful description of the business layer. For edit and search layers, it will be shown in the legend.
Query Externally: If checked, the business layer is flagged to support “Query” capability. This flag is for external tools only.
Create Externally: If checked, the business layer is flagged to support “Create” operation. This flag is for external tools only.
Delete Externally: If checked, the business layer is flagged to support “Delete” operation. This flag is for external tools only.
Update Externally: If checked, the business layer is flagged to support “Create”, “Delete”, and “Update” operations. This flag is for external tools only.
Note The Edit capability will be included if Create, Delete, or Update is enabled for a feature service.
Available in Catalog Service: If checked, the business layer is published in the catalog service. This flag is for external tools only.

Fields

Business layers use a subset of attributes (fields) of the fields of its parent geo object. If you maintain fields, they will be populated and exposed as attributes of the feature service. Some fields are mandatory and will be included by default. Mark one of the fields as a header field – it will be displayed as a default geometry label and header in the popup window. All the defined fields will be available to other ArcGIS tools.

Note Maintain the field label only if you want to see this attribute (field) in the popup window on the map UI. Care is recommended when labeling technical fields, as they may not be understood by the business users.

It’s also possible to indicate if a field is nullable (mandatory) or editable. This can be done by checking off the corresponding flags in the Customizing.

Note The information will be published and is for external tools only.