Skip to main content

Display Hyperlink not repsonding

Permanently deleted user
I am using the display hyperlink activity in my workflow. I have the properties set to the URI location of the file on our network. The container displays correctly with what looks to be a hyperlink, however when I click on the link nothing happens. If I right click and select open in a new tab, I get a tab with about:blank. If I right click the hyperlink and select copy link url, I am then able to paste it in a new tab and display the link. Does anyone know why the hyperlink won't open correctly? Thanks. <?xml version="1.0" encoding="utf-16"?><ClipboardData Metadata="{x:Null}" Version="1.0" xmlns="http://schemas.microsoft.com/netfx/2009/xaml/activities/presentation" xmlns:gcx="http://apis.geocortex.com/2009" xmlns:gwa="clr-namespace:Geocortex.Workflow.Activities;assembly=Geocortex.Workflow.Activities" xmlns:sap2010="http://schemas.microsoft.com/netfx/2010/xaml/activities/presentation" xmlns:scg="clr-namespace:System.Collections.Generic;assembly=mscorlib" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"><ClipboardData.Data><scg:List x:TypeArguments="x:Object" Capacity="1"><gwa:DisplayHyperlink DisplayName="Display Download Hyperlink" VirtualizedContainerService.HintSize="330,245" HyperlinkText="Address Assignment Report" Message="[sMessage]" Target="_blank" Title="Report Ready" Uri="[&quot;file:\\nas3\yeonshared\PUBLISH\GIS\TestGeocortexReport\&quot;+strCaseNum+&quot;.pdf&quot;]" WorkflowContainerName="Default"><gwa:DisplayHyperlink.Buttons><gcx:FormButton CausesValidation="False" IsDefault="False" Label="Continue" Value="Value" /></gwa:DisplayHyperlink.Buttons></gwa:DisplayHyperlink></scg:List></ClipboardData.Data></ClipboardData>
0

Comments

2 comments

Date Votes
  • Permanently deleted user
    **Update** I am only having this problem when using Chrome.
    0
  • Zack Robison
    My first guess would be that this is an issue with chrome browser settings or extentsions.  I know that AdBlockers have caused a similar issue for me in the past.  Do you know that this behavior is consistent accross different users?  If not, I would try opening the app in Chrome's "incognito" mode (which doesn't access cookies) with no extensions running (chrome://extensions/) before continuing to debug.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post