RE: Adding Links to WorkItems using WorkItems.xml

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks for your patience, Steve.

After confirming with product team, the <Hyperlink> tag is not supporting
to link to SharePoint document. $$WSSSITE$$/$$PROJECTNAME$$ are only
supported in <Field> tags. But hopefully, for your situation, I have found
one workaround.:)

Work item supports using an HTML field as a rich-text box. By using this
feature, we could put hyperlinks into HTMLFieldControl. Just like that we
have a webpage with links to SharePoint documents. Here are the way to
implement it.

Defining a new field in work item type definition. For example, in
task.xml, we define a new field named "MyLinks", refname is "My.Links" and
type is "HTML" instead of "PlainText".
<FIELD name="MyLinks" refname="My.Links" type="HTML">
</FIELD>
Note that we must keep refname as a new name instead of existing field such
as "System.Description". Since we are not able to change the existing
fields' type, for example, "System.Description" is defined as "PlainText"
originally.

After defining the new field, we need to add a HTMLFieldControl associated
with it. In the example, we wrap it in a tab control.
<Tab Label="My Links">
<Control Type="HtmlFieldControl" FieldName="My.Links" Label="My Links:"
LabelPosition="Top" Dock="Fill"/>
</Tab>

Now we can assign initial HTML value to My.Links field in workitems.xml.
<FIELD refname="My.Lists" value="&lt;P&gt;&lt;A
href='$$WSSSITE$$/$$PROJECTNAME$$/Process%20Guidance/Supporting%20Files/Brai
nstormScenarios.htm'&gt;Service Requirement&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A
href='$$WSSSITE$$/$$PROJECTNAME$$/Project%20Management/Issues.xls'&gt;Issues
&lt;/A&gt;&lt;/P&gt;" />

The value has been replaced by escape character such as "&lt;", "&gt;"
because it is defined in an xml document. The target HTML value looks like:
<P><A
href='$$WSSSITE$$/$$PROJECTNAME$$/Process%20Guidance/Supporting%20Files/Brai
nstormScenarios.htm'>Service Requirement</A></P>
<P><A
href='$$WSSSITE$$/$$PROJECTNAME$$/Project%20Management/Issues.xls'>Issues</A
</P>

$$WSSSITE$$/$$PROJECTNAME$$ will be replaced by its real value in work item
<Field> tags.

This is a quite simple sample for your situation. You could enrich the HTML
value by yourself.

Please try the workaround above, and let me know if it works for you.
Thanks.

Regards,
Hongye Sun (hongyes@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

This posting is provided "AS IS" with no warranties, and confers no rights.


.

Relevant Pages

  • Re: vs2008 problems
    ... uppercase tags flag as errors although the table still runs. ... As for the VS 2008 html designer, it has been redesigned from the original ... Microsoft MSDN Online Support Lead ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Adding Links to WorkItems using WorkItems.xml
    ... to link to SharePoint document. ... Defining a new field in work item type definition. ... Now we can assign initial HTML value to My.Links field in workitems.xml. ... Microsoft Online Community Support ...
    (microsoft.public.vsnet.enterprise.tools)
  • Re: How is Java typically invoked from HTML? And Java Permissions question...
    ... Also using param tags this way ... I believe it was MS that insisted on the removal of the applet tag from HTML 4. ... Apparently MS doesn't want to support standard HTML that ...
    (comp.lang.java.programmer)
  • ANN: VMS Mosaic 4.0
    ... tables and frames), animated GIFs, cookies, secure connections, etc. ... It does not support Java, ... Support for additional HTML tags and attributes ... Added preference and menu option to enable/disable tooltip help ...
    (comp.os.vms)
  • Re: Issue Getting Suckerfish Dropdown Menu Working in IE6
    ... The `script' element is supported since HTML 3.2, ... This requires support for the Web standards W3C DOM Level 2 Core and HTML. ... This requires support for a proprietary property on a host object. ... This also requires support for a proprietary property on a host object. ...
    (comp.lang.javascript)