Each asset in dScribe is of a specific type. The asset type indicates the purpose of the asset and comes with its own properties and layout settings.
Asset Types can be managed in the Admin Portal > Asset Types.
Asset Properties
Each asset comes with various properties to provide users with more information on that asset. There are 3 categories of properties:
Standard Properties
Standard Properties
These properties are available by default and cannot be changed. They include the following information:
Asset type The type as defined in dScribe (e.g. Dataset, Report, etc.)
Name The name of the asset. If the asset was crawled from a source system, the name cannot be changed.
Documentation A rich text field which can be used to describe the asset. Can include links, images & more.
Followed The possibility to show favourites on the home page or easily search through these in the search page.
Validation Status The validation status of the asset.
Discovery Policy allowing to restrict read access of asset (For more information, see Organisation)
Source If crawled via a connector, the name of the source.
Created On When the asset was created or loaded for the first time in dScribe.
Updated On Who last changed the asset in dScribe.
Author who created the asset in dScribe (user or process user).
Last editor Who last changed the asset in dScribe.
Source Properties
Source Properties
These Properties available by default for assets that were automatically crawled from a source system. They include additional information retrieved from the source. The information available varies from the sources crawled. Below listed some potential (non exhaustive list) of properties:
Created by in source Who created the asset in the source system.
Created in source on When the asset was created in the source system.
Updated by in source Who last changed the asset in the source system.
Updated in source on When the asset was last changed in the source system.
Additional source-specific properties For example: 'Workspace' for Power BI assets, 'Schema' for SQL Server assets, etc.
Custom Properties
Custom Properties
Additional custom properties can be added to each asset type to further enrich the type of information you can document.
Custom properties are created and linked to specific asset types via the Properties page.
Layout
The layout of each asset type can be configured according to your needs.
General documentation or descriptions are always displayed on every asset on top.
Other documentation (properties) can be organised in (conditional) sections.
Step 1 - Creating sections
Step 1 - Creating sections
New sections can be simply added and reorganised by using 
or 
.
Optional settings for sections
Optional settings for sections
Sections can be made conditional, allowing for a more flexible setup without needing to create custom asset types. A common use case is adding technical documentation to non-technical asset types. The technical section will only be displayed when a specific condition is met.
Example: If the asset documents a definition that is not relevant to Salesforce, the section containing technical information from Salesforce will not be shown.
Step 2 - Adding properties to sections
Step 2 - Adding properties to sections
Properties can easily be added to section by using the 
situated to the right of the enabled property.
Tips:
Not finding a property? Make sure the property is enabled (activated) on your asset type. For more information see Custom Properties.
Drag and drop the property if you would like to reorder within a section or if you would like to move it to another section.
Optional settings for properties
Optional settings for properties
Properties can be set up as mandatory when creating an asset. To do so, switch on the Required toggle. This toggle becomes available only when you hover over the section in the application.
Once a property is made mandatory, you can define specific conditions under which it applies. For example, if the asset being documented is a Metric, it may be required to include a formula explaining how the KPI is calculated.
Click on
(more options) and select "Add a Condition" to define the specific condition under which the property should be mandatory. This ensures the property is required only in the relevant context.
