The custom roads capability of StreetMap Premium was initially released last year. Now with the addition of the final two regions, Asia Pacific and Latin America, it’s available globally! StreetMap Premium for ArcGIS Custom Roads allows organizations to combine roads that they … Continue reading
Combine your own custom roads with StreetMap Premium for a single routable street network. Streetmap Premium for ArcGIS provides ready-to-use geocoding, routing, and map display content for use within ArcGIS Desktop and ArcGIS Server, behind your firewall. Today Esri announces … Continue reading
In part 1 of this blog series I wrote about interactive geoprocessing (GP) steps in ArcGIS Workflow Manager. Now, in part 2, we’ll move onto automated GP steps and wrap up the discussion from there.
At the end of part 1, you’ll recall we had pre-populated all of the required parameters for a GP tool.
And I was wondering why, with all of a tool’s arguments pre-populated, do we still need to show a dialog box to the user?
Right. And the answer is that we don’t. If all of the parameters have been correctly pre-populated, there are a number of alternate ways that you can run a GP step without prompting a user for anything. These include:
In my previous blog I introduced you to the different types of custom steps available in ArcGIS Workflow Manager including those that make use of Geoprocessing (GP) tools. Today, we’ll explore using GP steps in a Workflow Manager workflow.
Okay. How do I get started?
Geoprocessing steps use the same tools, models, and scripts that you can access through an ArcGIS toolbox. The easiest way to set up a GP step is with the out-of-the-box JTXDesktopSteps.LaunchGPTool custom step. Refer to the online help for more information about how to create step types.
The notion of “custom steps” in ArcGIS Workflow Manager can be confusing. Many people hear “custom” and think immediately of software development. With Workflow Manager, the reality is that a workflow designer will create and configure many different step types by using the Workflow Manager Administrator application. Even steps available out-of-the box – including special purpose steps called “Custom Step Objects” – will likely be customized in Workflow Manager Administrator to your organizations specific environment.
This blog post will discuss step customization (somewhat), Custom Step Objects (mostly), and how they can help in your workflows. If you remember nothing else, just remember that using custom steps in Workflow Manager doesn’t necessarily equate to writing custom code!
In a previous blog we discussed how to automate your data validation workflows by integrating ArcGIS Data Reviewer with ArcGIS Workflow Manager. We also discussed some of the basic functions you can perform with the Reviewer
Custom Steps. For this blog I’d like to take it a step further and describe other ways in which you can use the custom steps. I’ll also introduce additional functionality in Workflow Manager that you might find useful when integrating
with Data Reviewer.
Working with Reviewer sessions
Reviewer sessions are a way of filtering records in the Reviewer workspace to show only those records you are interested in. Last time, we outlined how to use tokens with the Create a Reviewer Session custom step to create unique sessions for each job based on the Job ID. There are other ways you can create sessions depending on your workflows. For example, if you have unique sessions that already exist for each user, you can use tokens like the [JOB:ASSIGNED_TO] in the Run Reviewer Batch Job custom step to write the errors to the existing sessions.