1·Tip: Don't be afraid to link one sub item to a totally different agenda item.
小技巧：别不敢把一个次要项目联向一个完全不同的议程项目。
2·First, we must focus on the work item itself, taking no account of its sub work items.
首先，我们必须关注工作项本身，不要考虑它的子工作项。
3·This lists how many, of what components, are needed for each item (part, sub assembly, final assembly, finished product) of manufacture.
这个清单列出制造每个项目(零件，组件，总装，成品)所需要的原料数量和种类。
4·The values of the inner data set's parameters are from the link table's SOURCE_ITEMID column because a work item can find its sub - work item's WI_ITEMID by retrieving the data from Links table.
内部数据参数的值来自于联系表格的source_itemid列，因为一个工作项可以通过从Links表格中获得数据，来找到其子工作项的WI_ITEMID。
5·But at this moment we cannot calculate the work item status because it may contain sub-work items, so we need to declare two global variables to store these values.
但是此时，我们不能计算工作项的状态，因为它可能包含了子工作项，这样我们需要声明两个全局变量，以存储这些值。
6·As mentioned earlier, the work item is loaded earlier than its sub-work items and they display the result later than its sub-work items.
正如前面所提到的那样，工作项要比子工作项更先载入，但是显示的结果要比其子工作项更晚一些。
7·The reason for this is that we do not know how deep of its sub work item levels are before the report builds.
这样做的原因就是我们并不知道构建报表之前，子工作项的层次有多深。
8·With this design, the inner table retrieves only one work item at a time, so that as the sub-work items count increases, it takes an increasingly longer time to build the report.
有了这个设计，内部表格一次只获取一个工作项，这样随着子工作项数量的增加，构建报表就需要花费更长的时间。
9·To add emphasis, the color and font weight is changed for this list item and any sub-level list items within it.
为了增强效果，我们修改了这个列表项和其中任何子列表项的颜色和字体粗细。
10·Implement the Item Connector client by referring to the seven steps in the "Item Connector client" sub-section of the "Item Connector components" section.
通过参考“项目连接器构件”部分中“项目连接器客户端”章节的七个步骤来实施项目连接器客户端。