Latest Contributions by deleted-user-7uOyUeQXbkI0

Hello, I'm trying to find a better way for some remote users to connect and work with their teams Workflow Manager and I'm exploring the option of using the Workflow Manager JavaScript Web Viewer to do this.  I'm curious if others have successfully integrated using the Web Viewer into their teams processes, especially when it comes to remote users. I am currently working on setting up a test viewer to try and answer some of these questions myself, but it is taking longer than I initially thought it would and would love to get some feedback on whether it is worth continuing to pursue this option or whether I should be looking for a different solution. Below are some of the questions and concerns I have about the web viewer.  I would greatly appreciate feedback from anybody that has worked with it themselves, especially if you have successfully incorporated into your teams processes. Step execution speed via Web Viewer vs. Step execution speed via desktop One of the big reasons we are looking into this is because it is very slow for our remote users to connect directly to our WMX database and execute steps or make updates.  This is partly because all of our internet traffic is routed to our corporate offices and then back out to our sites, therefore we have pretty high latency between the two offices.  I am hoping that executing the steps via the web viewer can at the very least be an improvement for them, and hopefully comparable to speeds experienced by users who work on site.  What have others seen in this regard?  Also, does anybody know what are the main factors in how quickly a step will execute via the web viewer?  Executing steps in workflows I know that not all steps will be executable via the web viewer.  Particularly anything in the JTXDesktopSteps group of custom step objects, like JTXDesktop.LaunchGPTool.  However, we have setup quite a few Executable Steps where we are launching python.exe directly rather than using ExecuteGP.  I haven't seen anything in the documentation that implies this shouldn't be possible and it seems as long as the file path to python.exe is available on the server and the filepaths to the referenced scripts are available on the server, then it should be able to execute the script.  Has anybody else been able to run Executable steps that run an executable on the server, i.e., python.exe or cmd.exe?  If not, do you just use JTXSteps.ExecuteGPTool instead to run tools/scripts? Can steps executed via the web client reference/access data that is stored on the users workstation or does all data need to be in a location the server can access? This is particularly important in our situation because our users are working with file geodatabases stored on their local workstation. Any other challenges, tips, or tricks, you came across that weren't specified in the documentation that you think would be helpful for others to know about? Thank you in advance for all responses. I will greatly appreciate them. ... View more

We have an extended property that stores a date in a date field type.  In a subsequent step we use a token to pass along that date as an argument to run another tool, but we are getting errors saying input is not in the proper format.  Is this because the token passes it along as a string and not as a date? ... View more

I have an ExecuteGPTool step in my workflow that I want to run immediately after job creation.  This step is running a custom script that will use the JOB_ID to select the Job AOI and use a select by location to select a feature in another feature class that contains attributes that I want to put into my jobs extended properties table(s).  Once the properties are populated it then renames the job based upon those properties. What I have found though is that this step will not execute properly while the same session of Workflow Manager that created the job is open. No matter what I have tried, I must close and reopen Workflow Manager before this step will work properly.  All of the below scenarios have failed: Workflow is set to auto execute upon job creation and steps auto execute during job creation. Workflow is set to auto execute upon job creation, but doesn't because the job is not assigned to the person creating the job. After the job is created, and assigning it to the user, the step still won't successfully run Workflow is NOT set to auto execute upon job creation.  After manually starting the workflow, the step still returns failure code. In all three scenarios, if I closed and reopened WMX and then ran the step, it completed successfully.  Any idea what is going on? ... View more

I have created a WMS and it worked just fine the other day, but then I made it private.  It took me a while to get a token to work, but I finally did by creating one for the referer IP, so I can finally connect to the WMS. When I load it in ArcMap though, none of the features show up.  I can see in the table of contents that it is still reading things like my scale ranges for when to draw certain features, but there is nothing there. I just tried creating a new service with the exact same data and it too worked fine while I had it set to public, but when I made it private, I could no longer see the features. What is going on? ... View more

I am trying to setup a production system using ArcSDE and Workflow Manager.  We want to use the AOI editing restriction to keep people from editing data outside of their assigned AOIs.  In order for people to modify and create feature geometry though I have to give them CREATE, DELETE, INSERT, and UPDATE privileges from the dbo user.  When I do this, the AOI restrictions are no longer having any affect.  How can I remedy this?  It seems like it shouldn't be working this way. Technical stuff WinXP ArcGIS 10 SP3 WMX 10 SP3 ArcSDE 10 SP3 SQL Server 2008 R2 ... View more