Artifacts
In objectiF RM, you can define your own element types using so-called artifacts. These custom artifacts can be used in the same way as the element types included in the tool by default. You can create revisions and variants, view the history, and define evaluations. You can share them, generate them in your MS Word documents, and exchange them between projects.
Several steps are required to make custom artifacts available for use in projects:
Create user-defined artifact types
If you need elements in your project that are not included in objectiF RM by default, you can define your own artifact types.
Artifact types specify:
- what type of element an artifact represents
- which properties it has
- where it is used in the project
This step forms the basis for all subsequent steps.
Create user-defined artifact relationships
To link custom artifacts with existing or other custom artifacts, you must create artifact relationships. Without defined artifact relationships, links between elements cannot be created.
Artifact relationships:
- describe which relationships are established between artifact types
- are created and defined manually
- enable two artifact types to be linked
Artifact relationships are created in the same way as artifacts.
Creating forms
To create and edit new artifacts, at least one form must exist in the project.
Forms
- are a prerequisite for creating and editing new artifacts
- specify which properties of an artifact are visible and editable
- determine how these properties are arranged and displayed in the form
An artifact type without a form cannot be used in the project.
Creating a state machine
Once you have created artifacts, artifact relationships, and forms, it is advisable to create a state machine.
A state machine enables you to:
- map the workflow of an artifact
- use defined states
- specifically control state changes in the project
State machines allow artifacts to be processed consistently in the project and the processing state to be tracked transparently.