Design Layer is used to control designing of field (like hidden, label etc). This is in between bsp view and bol layer. This way we can control similar fields in different views at a time.
SPRO -> CRM -> UI framework -> Design Layer
For LORD ERP, see 'Define eference Design objects'
In the UI framework, some Design relevant settings can be made. These settings have to be made per view (context nodes and their attributes), which is not always what user wants: If a single field occurs on many views, the settings should be made once and then influence all views carrying this field.
The purpose of the design layer is to define a layer which is logically positioned between the BSP view layer and the BOL layer to make UI relevant settings for many view in one go.
- Field visibility
- Field labels
- Mandatory field
- Disabled field
- Select an object type. Please note that this object type is not necessarily the same object type used by the application controllers and multilevel configuration. This means that this object type could be a generic object type for use with the design layer.
- For an object type maintain design objects, which define the design layer settings. The assigned BOL entity is used to determine the possible attributes.
- For each design object assign the design settings: This can be done for ALL attributes of the given BOL entity and for specific exceptions to this with a specific BOL attribute name. Select whether fields using this design are hidden, mandatory or disabled and what field label they have.
2. If used on attribute level, you may enter a BOL attribute name, if it differs from the context nodes attribute name.
No comments:
Post a Comment