Latest Contributions by BrianDemers

Hi Sue, I believe that you'll need to have versioning and geodatabase archiving enabled on your geodatabase in order for the transaction/history tools to work. When I've used them in the past, I would: Create an editing version with the "Create Version" step Make my data edits on that version Use the "Workflow Manager Custom Post" tool (briefly described here) to post these edits back to the default version. If you have GDB archiving enabled, it's this custom post that links your job to that specific group of edits.  (...and you can't do a post unless you're doing versioned editing.) One important clarification: you only want versioning/archiving enabled on your *data* tables and feature classes, not your Workflow Manager tables/FCs. I hope that helps, Brian D. ... View more

Hi Ashley, Try looking for the ID in the JTX_JOB_STEP table (under STEP_ID?).  If the ID shows up there, I think you can use the "STEP_TYPE_ID" field to figure out what step type to check in the "JTX_STEP_TYPE" table. Not sure offhand what the problem might be, but hopefully this will shed some light on things...?  Good luck, Brian D. ... View more

Hi Patrick, To my knowledge, you can't reuse job IDs like you're describing. As an alternative, you could set up an extended property for your jobs -- an alternate ID/number, really -- and then maintain its value however you wish. I hope this helps, Brian D. ... View more

Hi, Just a thought about this one: I don't think you could do this with the name field itself, since the job names are set as soon as a job is created (before the AOI is even assigned, I would guess). However, that said... instead of using the job name field for your application, could you use an extended property field instead?  You can set extended properties at any time, and it should be pretty straightforward to set up a model or script that populates an extended property based on your AOI or some attribute of a specific feature.  And you could obviously make the value look like a job name. I hope that helps. Brian D. ... View more

Hi Hadas, The Database folder (and a few others) moved relatively recently, I think due to permissions changes on Windows Vista/7.  It's now typically found under "C:\ProgramData\ESRI\WMX" or "C:\Documents and Settings\All Users\Application Data\ESRI\WMX" (on XP). If you don't find it in either of those places, try running the Workflow Manager Advanced Settings Tool to see how your system is configured. I hope this helps... Brian D. ... View more

Ah, I see.  In that case, no, the administration utilities most likely won't help you. There's definitely a REST interface for deleting jobs, though I don't have a code example at the ready.  I'm not sure if the Flex sample viewer includes an object/class for managing jobs.  However, even if it doesn't, I'd at least expect the behavior of "DeleteJobs" to be consistent with that of the other calls you're making to Workflow Manager Server. ...not sure if that helps...? ... View more

Hi, If you're coding in ArcObjects, then the C# version will look something like: int jobId; // Set your job ID to the ID of the job to be deleted IJTXJobManager jobManager = m_ipDatabase.JobManager; jobManager.DeleteJob(jobId, true); There's also a "DeleteJob" GP tool included with the Workflow Manager Administration Utilities, if you'd like to do this from a Python script. I hope that helps. Brian D. ... View more

One thing to look at might be the sample WMX Flex viewer available on the resource center (see here).  The source code is included in the download, and there are a handful of source files that seem to be related to uploading and managing attachments. Additionally, there's a link to one deployed instance of this viewer (click on the "Related Link" on the page above), and it seems to support embedded attachments.  If the sample viewer is behaving the way you'd like, maybe it will be some help...? ... View more

Hi Scott, Unfortunately, I couldn't find a way to do what you describe.  I was hoping that it would be possible to use a token like [SYS:CUR_DATE] in the report title, but the token wasn't being expanded out for me when I tried that. Sorry for the bad news; hopefully someone else has a better answer... Brian D. ... View more

Hi, It might be worth trying to add an attachment directly through the REST endpoint using a web browser; that could help narrow down whether there's an issue with the Flash application or with your WMX Server configuration. The REST API documentation will be installed on the machine where WMX Server has been installed, and should be accessible by going to "Start | All Programs | ArcGIS Workflow Manager | Developer Help | Workflow Manager Server REST Services Help".  From there, you can find the complete details about how to add an attachment using the REST interface. For convenience, I attached an example from the help is below (...I also added an extra space after the "http:" to keep the forums from hiding the full link): [INDENT] Example 1: URL for adding a linked attachment to job ID 5 in the "Workflow" service on sampleserver. http: //sampleserver/arcgis/rest/services/Workflow/WMServer/jobs/5/attachments/add?user=cjones&storageType=1&filePath=C:\Documents\Job_Guidelines.pdf[/INDENT] You may also want to use a tool like Fiddler or Firebug to see what URL the web application is using to add the attachment (and to ensure that the application is even getting that far). I hope that helps; good luck... Brian D. ... View more

Hi Ray, Jumping in to try to shed some light about the date/time issue: WMX stores its times internally as UTC times, which I think is what's causing the differences you're seeing.  So, for example, if you're located in New York and your system's time zone is set to eastern time, you could expect to see a time in the database that's either 4 or 5 hours ahead of the "current" time (depending on whether it's daylight savings time or not... and assuming I did my math correctly!). Like you noted, the point of confusion seems to be that there are certain cases -- like report generation -- where WMX doesn't convert the time in a date field back to local time before it's displayed.  I'll submit this as an enhancement request. Anyway, hopefully that at least explains what you're seeing...? Brian D. ... View more

Hi, I'd be curious to see if/how anyone else has done this, but I don't believe Workflow Manager's out-of-the-box notification mechanisms can be used with Gmail.  WMX notifications require access to an unsecured SMTP server -- presumably under your control on your internal network -- whereas Gmail introduces a host of authentication and encryption requirements. Additionally, while not a technical issue, I suspect that such usage could violate Gmail's terms of use.  I'd recommend looking into this before proceeding too far down this path. I hope this helps... Brian D. ... View more

Hi, Just a guess, but if you used one of the database vendor's tools to delete the "JTX_" tables and feature classes, this may have corrupted the SDE system tables and introduced the error you're seeing below.  In general, it's a best practice to only use ArcCatalog, ArcMap, a GP tool, etc. to create/delete items in an SDE geodatabase. Regardless of how the tables were deleted, a simple test would be to create a new database and run the WMX post-install on that DB.  If this is successful and there's other (non-WMX-related) information in the old DB that you need to preserve, you could try copying only those feature classes & tables to the new DB using ArcCatalog, or restoring the old DB from a backup. I hope this helps; good luck! Brian D. ... View more

No problem; glad that it worked. 🙂 For anyone looking for more info about WMX notifications (and to give credit where credit is due!), have a look at this link. ... View more