Layer filter workflows

Are Layer Filter Workflows supported for the GVH 2.5? When I try to apply one to one of my layers I get a window that says, "Error Loading Map Services: There was a problem loading one or more map services. The following map services may be unavailable: <map service name>."

It's easy enough to use a startup workflow that runs a Set Layer Definition, but I thought I'd check to make sure this isn't a bug?

There's really nothing to the workflow; it's just a single assign activity to assign the where clause value to the where output argument:

<Activity mc:Ignorable="sads sap sap2010" x:Class="ActivityBuilder"

xmlns="http://schemas.microsoft.com/netfx/2009/xaml/activities"

xmlns:eac="clr-namespace:ESRI.ArcGIS.Client;assembly=ESRI.ArcGIS.Client"

xmlns:eacg="clr-namespace:ESRI.ArcGIS.Client.Geometry;assembly=ESRI.ArcGIS.Client"

xmlns:eact="clr-namespace:ESRI.ArcGIS.Client.Tasks;assembly=ESRI.ArcGIS.Client"

xmlns:gce="clr-namespace:Geocortex.Core.Extensions;assembly=Geocortex.Core"

xmlns:gfc="clr-namespace:Geocortex.Forms.Client;assembly=Geocortex.EssentialsWpfApi"

xmlns:gfci="clr-namespace:Geocortex.Forms.Client.Items;assembly=Geocortex.EssentialsWpfApi"

xmlns:gr="clr-namespace:Geocortex.Reporting;assembly=Geocortex.Reporting"

xmlns:gwa="clr-namespace:Geocortex.Workflow.Activities;assembly=Geocortex.Workflow"

xmlns:gwa1="clr-namespace:Geocortex.Workflow.Activities;assembly=Geocortex.Workflow.Activities"

xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"

xmlns:mva="clr-namespace:Microsoft.VisualBasic.Activities;assembly=System.Activities"

xmlns:s="clr-namespace:System;assembly=System.Core"

xmlns:s1="clr-namespace:System;assembly=System"

xmlns:s2="clr-namespace:System;assembly=mscorlib"

xmlns:s3="clr-namespace:System;assembly=System.ServiceModel"

xmlns:sa="clr-namespace:System.Activities;assembly=System.Activities"

xmlns:sads="http://schemas.microsoft.com/netfx/2010/xaml/activities/debugger"

xmlns:sap="http://schemas.microsoft.com/netfx/2009/xaml/activities/presentation"

xmlns:sap2010="http://schemas.microsoft.com/netfx/2010/xaml/activities/presentation"

xmlns:scg="clr-namespace:System.Collections.Generic;assembly=mscorlib"

xmlns:sco="clr-namespace:System.Collections.ObjectModel;assembly=mscorlib"

xmlns:sl="clr-namespace:System.Linq;assembly=System.Core"

xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">

<x:Members>

<x:Property Name="where" Type="OutArgument(x:String)" />

</x:Members>

<mva:VisualBasic.Settings>

<x:Null />

</mva:VisualBasic.Settings>

<sap2010:WorkflowViewState.IdRef>ActivityBuilder_1</sap2010:WorkflowViewState.IdRef>

<TextExpression.NamespacesForImplementation>

<sco:Collection x:TypeArguments="x:String">

<x:String>System.Activities.XamlIntegration</x:String>

<x:String>System.Activities.Validation</x:String>

<x:String>System.Activities</x:String>

<x:String>System.Activities.Statements</x:String>

<x:String>System.Activities.Expressions</x:String>

<x:String>ESRI.ArcGIS.Client</x:String>

<x:String>ESRI.ArcGIS.Client.Geometry</x:String>

<x:String>ESRI.ArcGIS.Client.Tasks</x:String>

<x:String>Geocortex.Core.Extensions</x:String>

<x:String>Geocortex.Forms.Client</x:String>

<x:String>Geocortex.Forms.Client.Items</x:String>

<x:String>Geocortex.Reporting</x:String>

<x:String>Geocortex.Workflow.Activities</x:String>

<x:String>Microsoft.VisualBasic.Activities</x:String>

<x:String>System</x:String>

<x:String>System.Activities.Debugger.Symbol</x:String>

<x:String>System.Collections.Generic</x:String>

<x:String>System.Linq</x:String>

<x:String>System.Windows.Markup</x:String>

</sco:Collection>

</TextExpression.NamespacesForImplementation>

<TextExpression.ReferencesForImplementation>

<sco:Collection x:TypeArguments="AssemblyReference">

<AssemblyReference>System.Activities</AssemblyReference>

<AssemblyReference>ESRI.ArcGIS.Client</AssemblyReference>

<AssemblyReference>Geocortex.Core</AssemblyReference>

<AssemblyReference>Geocortex.EssentialsWpfApi</AssemblyReference>

<AssemblyReference>Geocortex.Reporting</AssemblyReference>

<AssemblyReference>Geocortex.Workflow</AssemblyReference>

<AssemblyReference>Geocortex.Workflow.Activities</AssemblyReference>

<AssemblyReference>System.Core</AssemblyReference>

<AssemblyReference>System</AssemblyReference>

<AssemblyReference>mscorlib</AssemblyReference>

<AssemblyReference>System.ServiceModel</AssemblyReference>

<AssemblyReference>PresentationFramework</AssemblyReference>

<AssemblyReference>WindowsBase</AssemblyReference>

<AssemblyReference>PresentationCore</AssemblyReference>

<AssemblyReference>System.Xaml</AssemblyReference>

</sco:Collection>

</TextExpression.ReferencesForImplementation>

<Assign.To>

<OutArgument x:TypeArguments="x:String">[where]</OutArgument>

</Assign.To>

<Assign.Value>

</Assign.Value>

</Assign>

<sads:DebugSymbol.Symbol>d6gBQzpcUHJvZ3JhbSBGaWxlcyAoeDg2KVxMYXRpdHVkZSBHZW9ncmFwaGljc1xHZW9jb3J0ZXggRXNzZW50aWFsc1xHRTE1MDhcUkVTVCBFbGVtZW50c1xTaXRlc1xDaXR5Vmlld19EZXB0X0VuZ2luZWVyaW5nXFZpcnR1YWxEaXJlY3Rvcnlcd29ya2Zsb3dzXEZpbHRlcl9XYXRlclBvaW50cy54YW1sBEsDVQ4CAQFMBVMOAgECUTBRTgIBBU4xTjgCAQM=</sads:DebugSymbol.Symbol>

</Sequence>

<sap2010:WorkflowViewState.ViewStateManager>

<sap2010:ViewStateManager>

<sap2010:ViewStateData Id="Assign_1" sap:VirtualizedContainerService.HintSize="242,60" />

<sap2010:ViewStateData Id="Sequence_1" sap:VirtualizedContainerService.HintSize="264,184">

<sap:WorkflowViewStateService.ViewState>

<scg:Dictionary x:TypeArguments="x:String, x:Object">

<x:Boolean x:Key="IsExpanded">True</x:Boolean>

</scg:Dictionary>

</sap:WorkflowViewStateService.ViewState>

</sap2010:ViewStateData>

<sap2010:ViewStateData Id="ActivityBuilder_1" sap:VirtualizedContainerService.HintSize="304,264" />

</sap2010:ViewStateManager>

</sap2010:WorkflowViewState.ViewStateManager>

</Activity>

Permanently deleted user

October 09, 2015 15:38

I haven't tried implementing layer filters yet, but before I do I'd like to know if they work! Also, is it better to set up a startup Set Layer Definition or use a Layer Filter workflow? I'm unclear on which I should be using to replace my ArcMap definition queries. I don't have security set up for any sites yet, which it sounds like you need to do to use the latter. Any experience would be helpful.

John Nerge

October 12, 2015 14:15

They aren't currently working in GE 4.4 with the GVH 2.5. I hadn't tested layer filter workflows since GE 4.1 using the GVS, so I don't know about in between versions.

In general, I've found that layer filter workflows are good if you want to permanently restrict access to certain records in a map layer for one or a group of users. However, I've seen a performance hit when applying too many of them in one site.

Set layer definition is great for running in startup workflows, and you can do the same things you can with a layer filter workflow by using the same workflow activities. However, the advantage of set layer definition is that it's run as part of the viewer instead of on the layer at the site level, which means you can write other workflows that update the layer definition after the app has launched.

I use this second method for some of our city inspectors. When the viewer first opens, a startup workflow runs that filters the open inspections layer to show only that inspectors inspections (using the Get Current User activity). But I also put a Show All Inspections tool in the I Want To menu so an inspector can change the definition to view all inspectors' inspections as well.

November 24, 2015 19:00

If you're trying to restrict access to certain records in a layer using Layer Defintions, you need to be careful that the user does not have access to the Filter button (under the Find tab in the lastest Silverlight Viewer) otherwise they'll be able to view any layer defintions that have been applied via your workflows. They can then simply remove the definition if desired to view all data in the layer.

Layer Definitions are applied on the Client after the map service has loaded, so the client needs locking down to prevent further access. In contrast, Layer Filter Workflows are applied on the Server, before the request returns to the client from ArcGIS Server, so there is no opportunity for the user to intercept and modify the result - they get the pre-filtered data only.

This is an important distinction if you are looking to use Filtering for secure services.

BTW did you get the Layer Filtering working in GVH 2.5?

If not, you might want to look at your In Arguments - there have to be 3 very specific args according to the Help guide and I can only see 1 defined in your workflow above.

December 04, 2015 14:45

Great catch, Ewan. Unfortunately, while creating a new layer filter workflow that includes all of the arguments successfully filters the layer, it also causes a startup error message saying that the map service with the workflow applied is unavailable. The map layers from that service are available and can be used in the viewer, but a false error message every time the viewer loads clearly isn't acceptable.

Layer filter workflows

Comments

Didn't find what you were looking for?