Adapt Query/select workflow if layer order changes
I have 10 different applications all of which are nearly identical. Each app is specific for various areas of the country, so each has a different map data service. Within each data service is a layer of available properties. I've created a workflow to search then select this available property layer, however that layer may have a different layer ID for each data service. How do i create a single workflow that can be used in all 10 applications and still allow for different Query Service Url, Map Service Id and Layer Id?
-
Hi Ethan
have you thought about setting arguments to your workflow so that you can configure the workflow by site?
Thanks
Ralph
0 -
I thought that might be possible, but I wasn't sure how to go about it. Can you give me a starting point?
0 -
Hi Ethan
you will need to create arguments (not variables) on your workflow for those items you wish to set to be different per site.
When you add the workflow to a site you then need to set properties on it where the name of the property including case needs to match what you set in the workflow.
The value needs to be set appropriately.
Have a go at the above with a workflow that just reports the Property that you set in the Site.
Hope that makes sense. If it doesn't then let me know and I will attempt to be clearer
Regards
Ralph
0 -
Ralph, thanks. I managed to do it with a simple alert like the below XML. I'll try it in the QueryTask and SelectFeatures next. Note: when setting up the property in restmanager, use quotes around the value (for strings anyway).
<Activity mc:Ignorable="sap" x:Class="{x:Null}" 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:sap="http://schemas.microsoft.com/netfx/2009/xaml/activities/presentation" xmlns:scg="clr-namespace:System.Collections.Generic;assembly=mscorlib" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
<x:Members>
<x:Property Name="testProp" Type="InArgument(x:String)" />
</x:Members>
<sap:VirtualizedContainerService.HintSize>274,250</sap:VirtualizedContainerService.HintSize>
<mva:VisualBasic.Settings>Assembly references and imported namespaces serialized as XML namespaces</mva:VisualBasic.Settings>
<Sequence sap:VirtualizedContainerService.HintSize="234,210" mva:VisualBasic.Settings="Assembly references and imported namespaces serialized as XML namespaces">
<sap:WorkflowViewStateService.ViewState>
<scg:Dictionary x:TypeArguments="x:String, x:Object">
<x:Boolean x:Key="IsExpanded">True</x:Boolean>
</scg:Dictionary>
</sap:WorkflowViewStateService.ViewState>
<gwa1:Alert sap:VirtualizedContainerService.HintSize="212,86" Text="["The property is " + testProp]" Title="Test Property" />
</Sequence>
</Activity>0 -
Hi Ethan
pleased to hear of the success. I am surprised to here your comments about quotes. I haven't needed to do that at all so far.
What was the error or the circumstance that brought you to that conclusion?
Ralph
0 -
I think you are correct about the quotes being unnecessary.
I have a new twist. It looks like I'm going to need to create several workflows in the same app that access the same map service ID. Can i set the map Service ID property at a level where all of the workflows can access it?
0
Please sign in to leave a comment.
Comments
6 comments