Latest Contributions by XiaomengZheng

When running the step, the start and end dates are automatically populated. This is not something being defined in the step configuration. However, you can configure the step to run on a schedule. More details are in the technical blog. Also if you try to limit the interaction in your workflow, you also can set the step to run automatically. Due to the step duration needs to be calculated accurately based on start_date and end_date, we do not offer the capability of defining the end_date manually.    ... View more

Gianmaria, Workflow Manager only allows you to associate the job with the feature layer by using the linked field configured in the job template. In Update Job Properties step, by entering the linked field value, the job is associated with the corresponding record in the feature layer. You will not be allowed to edit any other fields in the feature layer than the linked field. I hope this help clarify your questions. Thanks, Meggie ... View more

hi Gianmaria, Let me know if my understanding of your question is correct. You have configured the extended property table in your job template and you are trying to configure the Update Job Properties step in diagram, correct? Your step should configured the properties to be edits in this format: [ext table name].[property name]. Updating the extended property table should occur in running this step in the job, not in the diagram. Last but not the least, if your extended table is 1- M, you need to use the Update 1-M Job Properties step type to match the relationship of extended table in your job template. Hope this help. Please let me know if you have any further questions.   Thanks, Meggie ... View more

Hello Gianmaria, Yes you can configure the Feature service as extended property table in your job template and parse the property values in the path expression. The configuration of using the Feature service extended property table in Update Job Properties step is similar to regular extended property table. More info is available at here   Thanks, Meggie ... View more

Hello Rino, Thank you for your question.  I understand that you would like to extend the job template to retrieve the linked job properties. Based on the error you get, are you having the path configured with arcade expression of extended properties? This is not implemented until 10.9.1 and not supported in earlier version. In earlier version, the path can only be evaluated with the expression using $retVal and more info is available here. Please let me know if you have any further questions or concerns. Thanks, Meggie ... View more

Hello Heather, Here are the differences in sharing Workflow Manager Package, Export/import configuration and Export/import Job data. 1. Workflow manager package is being used to share workflow manager elements including Job Types, Workflows, and Step Types. It does NOT contain job data from the workflow manager repository. 2. Export/import Configuration - The exported .jxl file contains all the configuration from the workflow manager repository but does NOT contain job data. 3. Export/import Job Data Geoprocessing tool - The exported .jxl file contains all the configuration information for the repository as well as information about all the jobs.  So if you would like to migrate your job data, you will need to use the Export/import Job Data Geoprocessing tool and they can be accessed in Pro Geoprocessing Workflow Manager Toolbox or ArcCatalog Workflow Manager Toolbox. Hope it help. Thanks, Meggie ... View more

I don't seem to be able to reproduce this issue. Could you please contact Esri Tech Support and they will work with you to look deeper into this issue. They may ask you to provide the data that you are using and try to reproduce this issue.  ... View more

What version of Pro are you using? I can give it a try. ... View more

Yeah I do not find anything in your log either. Just curious, how many jobs out of the 302 jobs in your current job query having AOI? I noticed your current job's (2018-02120) location is quite small. What if you zoom in and can you see the AOI?  ... View more

It seems to be a map loading issue for me. I see you have totally 302 jobs in the current job query and your AOI map should be just loaded properly. Any error in your log? You probably need to update the log level from default 3 to 5 to capture details. Thanks, Meggie ... View more

Hello, Pro shall work the same way as the Workflow Manager client.  The AOI function is still supported in Pro with the same configuration in the Workflow manager administrator. Would you please check your job's bookmark in Pro and see if the AOI bookmark existing?  Thanks, Meggie ... View more

The answer is Yes. You can configure a pagX to allow the Workflow Manager to open the layout in Pro. The pagX is required to be uploaded to your organizational Portal. You can follow the steps in below: 1. Upload the layout view as pagX in Portal. You can do it by accessing portal web page and choose Add Item - From your computer.  2. Configure the "LaunchArcMap" step in your workflow. 3. Configure a map for your job type and choose "Portal" as Storage type and enter the pagX Url hosted on your portal. (Hint: the url is the pagX item url,  see the example we provide in the configuration dialog, also consider to share the pagX to your users group who will access it in Pro) 4. You can also configure the pagX as alternative map in certain LaunchArcMap step, in case you have the step configured with existing MXD already. Noted that Opening PagX in Pro cannot zoom to the location defined in your job. However the job location's bookmark is available so that you can zoom to it. I hope this help and let me know if you have any further questions. Thanks, Meggie ... View more

Hi Dharma, Do you use Pro or 10.x? Here are some information regarding where we store the jtc file and it might help you find a workaround. If you use Pro, we store the jtc file in the project and you can try to navigate to the project folder. If you use 10.x, once you add the connection in Workflow Manager Administrator, the jtc file gets stored at \ProgramData\ESRI\WMX\10.7\Database. You can also make a copy of the jtc file else where. Hope it help. If you would like to share more information regarding how you pass on the jtc file path, I'm more than happy to discuss with you for other possible solutions. Thanks, Meggie ... View more

Hi Dharma, Do you try to retrieve the workflow manager database connection? The arcpy.wmx.Connect() can establish the connection to the workflow manager database. You will need to provide the jtc file path to be able to retrieve the connection. Or if you have had a wmx connection in Pro project the path is not required. Unfortunately we do not have existing python API to only retrieve the workflow manager database path. Thanks, Meggie ... View more