Mapping Attributes - trillium_discovery - trillium_quality - Latest

Trillium Control Center

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Discovery
Version
Latest
Language
English
Product name
Trillium Quality and Discovery
Title
Trillium Control Center
Copyright
2024
First publish date
2008
Last updated
2024-10-18
Published on
2024-10-18T15:02:04.502478

After copying a library project into a Quality project and adding a new input, you then use the Schema Editor to map the input attributes of the new input entity onto the output attributes that have been copied from the library. If the mapping is not performed, then the columns in the output entity will be empty.

Guidelines

Note the following when mapping input attributes to output attributes:

  • You map attributes in the Schema Editor for the first process in the copied workflow.
  • You do not have to map all attributes, only the ones you need. Any output attributes that are not mapped to an input will contain no values in the output data.
  • You do not have to map the attributes that already exist in both the input and the output schema.
  • If you insert library processes to the middle of an existing workflow, you must map attributes twice--once to the new input and again to map back to the existing process. This links the new workflow to the existing workflow. Think of it as mapping from the existing schema, to the library schema for the reused processes, and then mapping the final library process to the next real process. The next real process must have its Regenerate Output Schema > Edit Schema option enabled in the Schema Editor to allow mapping the library processes back to the existing process flow.