Download presentation
Presentation is loading. Please wait.
Published byJaclyn Strudwick Modified over 9 years ago
1
Rosario Linking OM Framework Naren Datha
2
Rosario link types Customizable work item link types with rich query abilities and rules to represent topologies Comes with built-in link types such as – Parent/Child for tree hierarchy links – Predecessor/Successor link types
3
Link type topologies Topology assigns a set of rules to link types. Network Link types of this topology have essentially no rules and no directionality. You can have circular relationships, and the link looks the same from both sides. Directed Network Link types of this topology are like Network links, except there is directionality. You can specify a name that appears at each end of the link. In other words, the link looks differently depending from which side you view it. Dependency Link types of this topology are like Directed Network links in that they have directionality, but an additional constraint to prevent circular relationships. Tree Link types of this topology are essentially trees, it enforces a one-to-many relationship and doesn’t allow circularity.
4
Creating new Link Types Decide which topology to use New WitAdmin utility. Link options: – ExportLinkType – ImportLinkType – ListLinkTypes – DeactivateLinkType – ReactivateLinkType Create xml file for linktype definition. Example: <LinkType ReferenceName=“MyCompany.LinkTypes.MyTree" ForwardName=“My Child" ReverseName=“My Parent" Topology="Tree" /> Run “WitAdmin ImportLinkType”
5
Getting work item linktypes in OM Work item link types are defined per server WorkItemStore.WorkItemLinkTypes has list of registered linktypes
6
Accessing links in a workitem Each work item has 2 collections: WorkItemLinks for current links and WorkItemLinkHistory for add/remove history Important properties of Link object: – SourceId, TargetId – AddedDate, RemovedDate
7
Creating and Deleting links
8
Querying links from UI
9
Query for links - WIQL SELECT [System.Id], [System.Links.LinkType], [System.Title] FROM WorkItemLinks WHERE mode(MustContain) ([Source].[System.TeamProject] = @project) And (System.Links.LinkType = 'System.LinkTypes.Related') And ([Target].[System.WorkItemType] = 'Task')
10
Running link query Use query class in object model
11
Using results of link query TargetIdSourceId 1 111 11111 121 12112 12212 131 _ _ Output from results Tree representation of results Hierarchical data is returned as SourceId, TargetId pairs. TargetId is id for the result, and SourceId is source of link such as Parent. Below diagram shows how tree can be visualized from result list results on the left
12
How the tree is constructed on VSIP client? Target Id Source Id 1 111 11111 121 10112 10212 131 ind ex Parent index Lev el 00 111 2112 311 4122 5 2 610 1 11 111 12 121 122 13 From Server Computed in clientDrawing on paint event
13
Result list view
14
Paging work items Our result list can handle large number of items because it pages the items from server as user scrolls “Query” function in WorkItemStore can be used for paging specified Ids and specified Fields from server. Example Usage:
15
Customizing Links Control -Multiple links controls can be hosted in a form with each control showing specified set of link types -Links control now can show customized columns -Links are grouped by link types
Similar presentations
© 2024 SlidePlayer.com Inc.
All rights reserved.