Latest Contributions by SamWest1

Hello! It sounds like Step scheduling should help out with your use case. You can set a step to wait a period of time, and then have it automatically release the hold and run the step. For the manual approval case, the hold will need to be released as part of that approval process, as it also blocks the running of the step until that scheduled time. Hope this helps you out, and be sure to let us know if you have any further questions ... View more

Glad to hear it! ... View more

Unfortunately there is not a way to pass a schema in to the array and have the system process it for you, however that is a neat use case that I'll pass on to the rest of the team for consideration. You'll have to handle that preprocessing of the array yourself with either a Send Web Request step to update the job or by updating each of those properties with the Update Job Properties step. You could also override the defaults through our other APIs such as REST and Python when creating the jobs, but that would require more customization. ... View more

Hi Hector, it is possible to pass an array of details for each job you wish to create. This could be an array of json objects or an array of arrays containing the details you wish to update. Your best bet will be to use Create Job per Array like you mentioned to create a job for each change, and then as preprocessing for each of those jobs, update the corresponding job or extended properties using Arcade expressions for the output values with the Update Job Properties step. If you're using the Extract Changes endpoint, and there's anything you aren't able to include from that response, it may be worth querying the feature service as well in each job for those additional details based on the object ids with changes. If there's any information in the scheduled job that you wish to be accessible within the newly created jobs, you can also make use of the parent-child relationship to pull that information. Hopefully this helps get you on track, but if you need further support be sure to let us know. For anyone at 11.1 and using either a hosted feature service or non-versioned referenced feature service this process is a bit easier. We have introduced the ability to create jobs with feature service webhooks that should cover this use case without needing a scheduled web request. This blog helps outline how to get started with those: Using the Feature Service Webhook Extract Changes Option in ArcGIS Workflow Manager ... View more

Hello, This is tricky with the way the overlap settings work, and I don't see an ideal solution that would prevent child jobs from having their AOIs outside of the parent while still allowing them to overlap. It sounds like you'd like your system to: Have AOI restrictions between jobs Allow child jobs to overlap their parent job AOI, but not be defined outside of it Allow child jobs to overlap each other. Disallow by Job Type doesn't allow overlap between the same job type, so that doesn't work with the third requirement, and the other two options don't fit the requirements either. Your best bet is to keep the Disallow setting, and instead grant the users who define the child AOIs the 'AOIOverlapOverride' privilege while defining the locations. Unfortunately, this will allow them to define the AOI outside of the parent job, but this is the only current way of maintaining AOI restrictions in general while also allowing the child jobs to overlap.  I've passed along your use case for consideration in future design. Let me know if you have any other questions, and I hope this helps you move forward. Thanks! Sam ... View more

I don't have any examples for the FME Cloud. We generally see people running FME via the data interoperability extension, which you could do as a GP tool from the launch/execute GP step. That may not work with the cloud version of FME, so I'd recommend using the FME Cloud API to write a python script to hit those REST endpoints instead. You should be able to run that script using a custom executable step or wrap it up as a GP tool and run it from the launch/execute GP step in your workflows. Sam ... View more

Hi William, This sounds like an excellent area to automate the boring stuff. I recommend writing a script to iterate through the features using a cursor, and then for each feature download the image, and add it as an attachment for its corresponding job. I'm not sure how you have the hyperlinks stored, but parsing job information and adding the attachment can be handled using our module. I recommend taking a look at the job class for adding the attachment, and whichever class corresponds with how you have the information stored. Here are some recommendations for downloading the images. I hope this gets you up and running! Thanks, Sam ... View more

Hello! This is a duplicate post and the discussion on this topic can be found here. Thanks, Sam ... View more