Description
✍️ New repository attributes are assigned on the Object Type, where you also provide a default value.
The default attributes in Build.One are handled using inheritance. For example, if a Instance object lacks an explicit value, it inherits from the Object Master level, and if the Object Master level also lacks a value, it then inherits the attribute value defined on the Object Type level. For a graphical representation please also see the above graphic.
Attributes
✍️ If the entry is an object type that has attributes, you can add here the list of them in the next table
Attribute | Description | Example/Values |
... | ... | ... |
... | ... |
How to use it
✍️ When creating a new screen we should always create an Object Master. This will allow us to use the widget(Object Master) in multiple screens without having to redefine all attributes.
Use Cases
✍️ When creating new screens we should always create object masters for our components in order to be able to reuse them in different screens.
✍️ When we require a default value for our component we can always define the default attribute value on the Object Type level.
Best Practices
✍️ When creating new components to be used in our screens, we should always create an object master and assign it’s attributes on the Object Master level.
Back to 
Documentation
Back to Home Page