Latest Contributions by KOliver

In Workflow Manager, I have a user that is having continual problems with opening a mxd via WMX and having the layers within the mxd flip to his database user name.  After much troubleshooting, I would like to delete and recreate this user both in the Workflow Managers users list and from ArcSDE. This user still has many open jobs with steps assigned him, as well as closed jobs that contain steps with the username. The user would be recreated with the same username in both ArcSDE and Workflow Manager. Are there are recommended steps for removing (and recreating) a user from Workflow Manager and also ArcSDE?  Are there any risks associated with user ids stored on internal tables within Workflow Manager? ... View more

We have noticed that when using the Flex web viewer, our Job Filters are not being recognized in the drop down when creating a New Job.  For example, if a user is only permitted to create Job Types A and C, they still see Job Type B even though it is not included in their filter.  If they try to create a job of Type "B", an error message does appear stating that the user does not have permission. Is there a way to hide the job types that the user cannot create from the Web Viewer (similar to the Desktop)? ... View more

In Workflow Manager 10.2.2, we have a workflow where every step is checked as "Step cannot be skipped" in the step properties. We are seeing some unexpected behaviour.  When the workflow is executed, the user can pick any step in the workflow (for example, the third or forth) and right-click to select "Set as Current Step".  Once the step is set to the current step, the step can be run successfully.  All of the previous steps have been skipped but no warning or error message appears.  Has anyone else experienced this?  Thanks! ... View more

We are currently upgrading our implementation of Workflow Manager and are exploring the use of Parent-Child jobs.  While we have easily set up auto-creating a child job, we are having trouble getting the child job to auto-execute as we would have expected. Configuration: Job “A” creates a workflow with a series of steps.  The last step in the workflow uses the Developer Sample step “CreateChildJobsAdvanced” to create a child (Job “B”). Job “B” – Within the Job Type parameters, the Workflow is set to “Auto-execute workflow upon job creation”.  The first step of this workflow uses the step “ExecuteSQL”.  The step is set to “Automatically execute when reached”. Scenario: 1.       Job A is created and steps completed. 2.       At the last step of Job A, the CreateChildJobsAdvanced is executed. 3.       Job B is created successfully as a child of Job A. 4.       The first step of Job B does not automatically execute when the job was created. Further information to the above.. If we create a new job of type "Job B" (not a child of Job A), the first step auto-executes as intended.  It appears to be not executing when the job is creating via a step in the parent job. Has anyone else been successful with a similar set up?  Thanks! ... View more

I am using ArcGIS 10, SP3. I have a model that performs a number of tasks successfully.  I would now like to add a step at the beginning where the user selects a polygon from the map, and then the model runs only using the selected feature. It is ok if the user just clicks on the polygon (using the standard Select tool) and then runs the model.  OR, if the model itself prompts the user to click on the polygon.  Either way would be fine. What is the easiest way to use a feature selected from the map as the input to a model? Thanks! ... View more