Select to view content in your preferred language

Using existing services with Workflow Manager

116
0
04-01-2025 11:14 AM
MaxCushner
Emerging Contributor

I am new to Workflow Manager and have reviewed a lot of the trainings and posts here, but I still need some guidance on specific parts of my teams requirements. 

Using Enterprise 11.4 and Pro 3.4. Workflow Manager Server has been deployed and all team members have Workflow Manager Extension licensed on Pro.

  1. My team is responsible for asset creation via heads-up digitization. I have an existing ETL workflow in FME that runs a delta report between what we have in our deployed feature service vs. new sets of non-gas data we're delivered internally. Let's assume that delta report identifies roughly 1000 points that my team then has to go and create in an existing feature class. This is currently done via editing on a branched version from a feature service. 
    • What's the best way for me to bulk-create a separate job for each of the 1000 points that need to be created? I did some light experimentation with this FME Custom Transformer, but I think my Web Adaptor settings are preventing me from exploring it further.
      https://hub.safe.com/publishers/sashal/transformers/workflowmanagerjobcreator
    • When creating each job, how else could I pass other attributes from the delta report to these new jobs in bulk?
    • If my analysts are doing all of the work in ArcGIS Pro rather than the Web UI, how can I configure the job (or job template) to verify that the feature has been created on the branched version?

  2. Our current process is that we have a large excel based tracking sheet on Sharepoint, and analysts will track work there when it's complete. In Workflow manager, when the jobs are created, could all 1000+ jobs be presented in a list so that analysts could just pick any job and start digitizing? Or would we have to batch the jobs in increments and assign multiple to a particular analyst?

  3. If the job on the analyst's end literally just "create this one point feature", would the actual creation job be as simple as [start/end] -> [define location]? Or would there have to be more steps involved? Let's assume that the branch version creation would take place either before Workflow Manager starts, or as part of a parent job to each individual feature

  4. When a new workflow is created, multiple workflow feature layers are created with it. Does any location definition or heads up feature creation task need to interface with these layers? If not, what are these layers for?

Thanks in advance for any help you can offer! If I can get this working, it will streamline and improve my team's performance immensely 🙂

0 Kudos
0 Replies