Workflow searches not recorded in history

Permanently deleted user

February 10, 2015 05:52

I have several search workflows and I notice that none of them are being recorded in histories!  Is there a way to do this?

0

• 

  Permanently deleted user

  March 23, 2016 21:09

  Still wanting to know if this is possible....

  0
• 

  Permanently deleted user

  March 23, 2016 21:31

  >recorded in histories.

   

  Do you mean 'System Log' file for the Log activity you added on the Worklow?

   

  If then, check what the LogLevel you set up on the Log activity, and check what System Log Level you set on your Essential Manager  - Application System Log Level.

   

  If 'Essential manager' setting is lower than what your workflow Log activity Log level and then still System Log file is not populated, then check 'App_Data/Log' folder's permission so that Esential app_pool identity user has to have a Written permissionon that folder.

   

  All workflow Log is logged to the server (Systerm Log file), other than client activity logging, which is on the browser.

   

  Munhwan

  0
• 

  Permanently deleted user

  March 24, 2016 23:22

  Hi Jacqueline,

   

  Are you referring to the search history in the Silverlight viewer?

   

  A workflow search is effectively no different than a search or identify done within the viewer itself; a FeatureSetCollection is passed to the Results module either way. However, for a particular FeatureSetCollection to be listed as a unique entry in the search history, it needs to have a unique name. If your search workflow results are in a FeatureSetCollection that uses a literal (like 'parcelSearchResults'), that entry in the history will be overwritten every time that search is invoked -- you'll have one result called parcelSearchResults, and it will always display the results from the last time it was run.

   

  Searches (and queries and identifies) performed in the viewer itself always give their resulting collection a name based on a time stamp, which is why they each appear sequentially in the history. You could do the same thing in your workflow by naming your collection DateTime.Now.toString(). Note that this won't work if, for whatever reason, you need your collection to be named something specific (say, in order for it to reused within your workflow).

   

  Also, none of what I've said will apply to the HTML5 viewer, as it does not have any concept of a search history.

   

  Is that helpful at all?

   

   

  0

Please sign in to leave a comment.