What is it?
OpenBOM developed a mechanism to support the way in which customers lay out data and control the availability of information to different types of users.
Such a mechanism, along with user-defined and team views, allows customers to slice and dice their data, sets of properties (attributes), access levels, and filters. As a result, every OpenBOM object (items, BOMs, orders, etc.) can be scoped to a specific access level.
Why do you need it?
The user-defined view is a very useful mechanism. It simplifies data access for each user, meaning that users do not have to view data that does not apply to them. This can also be considered a safety feature as it means that users do not see any data that they are not authorized to view. User-defined views are used as team views to protect information assets and to make data available only to a certain group of users (internal and external).
Why is OpenBOM different?
OpenBOM’s user-defined and team views provide a superior level of flexibility when defining sets of information and configuring visualizations and accessing levels. Combined with an equally flexible data model, customer needs can be better satisfied with OpenBOM.
How does it work?
A typical process includes the definition of properties (attributes), user-defined views, and team or role associations for specific users. Each user-defined view (or team view) includes:
- List of attributes (properties)
- Access levels (read-edit)
- User-view association (for “By View” access)
Viewing support for data sharing when an individual object, such as a BOM, is shared
Data is shared automatically. Users can even select a user-defined view to change the way the data is presented. In the case that a restriction applies, the user can only access the data (or a portion of the data) by adhering to said restriction.