blob: b899ac40013ae642ff70e4a8a4abd96b6dcb8d83 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
<html>
<!--
Copyright (c) 2004, 2007 Boeing.
All rights reserved. This program and the accompanying materials
are made available under the terms of the Eclipse Public License v1.0
which accompanies this distribution, and is available at
http://www.eclipse.org/legal/epl-v10.html
Contributors:
Boeing - initial API and implementation
-->
<head>
<title>Work Widget Definition Artifact</title>
<LINK rel="stylesheet" type="text/css" href="../../osee.help/html/style.css">
</head>
<body>
<h1>Work Rule Widget Artifact</h1>
<h2>Purpose</h2>
The Work Widget Definition artifact specifies a single widget, via xml, that will be
displayed on the state page in the ATS Workflow Editor.
<h2>How to do it - Artifact Editor</h2>
On the Common branch in the Artifact Editor, Expand "Action Tracking System" expand
"Work Widget" and double-click any existing Work Widget. Edit the following attributes and relations
accordingly.<br><br>
<li>Attributes</li>
<ul>
<li>Name:[unique name matching Work Id below]</li>
<li>osee.wi.Work Id:[unique id]</li>
<li>osee.wi.Work Description:Simple description explaining what widget is.</li>
<li>osee.wi.Work Data: XWidget=[XWidget xml specifying widget]</li>
</ul>
<li>Relations</li>
<ul>
<li>Work Item.Parent: Relate to any Team Definition or Work Page Definition artifacts as appropriate.</li>
</ul>
</body>
</html>
|
