1 / 4

introduction

introduction. This design doc will cover creating/editing attributeList , filterList , pseudoAttr One thing in common for them is that system needs to synchronize all property (except for displayName ) changes to all configs and the source.

cloris
Télécharger la présentation

introduction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. introduction • This design doc will cover creating/editing attributeList, filterList, pseudoAttr • One thing in common for them is that system needs to synchronize all property (except for displayName) changes to all configs and the source. • These config components can be created/edited at source or a derived config, but behind the scene, it should be always done in the source first then propagate to derived configs that expose it. • The other thing in common is that they can not be imported to other source as pointers.

  2. Creating/editing attributeList Allow users to enter values at creation: Available attributes: List all usual attributes (no attributeList, no pseudoAttr) in source that are not already in the left here. Double click to add to the left list Attribute list: List chosen attributes here. Cancel OK For creation: MC should create this attributeList in the source, then if this creation was initiated from a derived config, MC will create it in that config as well just like if it was drag & drop from source to that config (this may involve importing attributes that were not in the derived config For editing, ie, add or delete attributes in the list, update should happen it the source, then propagate that change to derived configs that import this attributeList. NOTE: if attribute removed from the list, do NOT remove the actual attribute.

  3. Creating/editing filterList • The workflow should be the same as that of the attributeList. One extra thing needs to take care is to ensure attributes that the filters are based on are copied to derived config if they were not already in a config

  4. Creating/editing pseudo attribute Allow users to enter values at creation: Display only User input Cancel OK For creation: MC picks up a new column in partition table to store the actual value of the pseudo attr. The table presented to the user is actually part of partition table. Create in the source first, then if the creation is initiated from a derived config then import it to there For editing, no extra thing to do NOTE: right-click (pXcY) will bring up this partitiontable editing dialog

More Related