Workflow/Viewers in Site inheritance

Todd Sales

June 19, 2013 00:29

Greetings & thanks in advance for any insights anyone can add...

Trying to build an advanced viewer inheriting a basic viewer that has a number of workflow searches. I've read the section of the admin guide that explains the unique nature of viewer inheritance.

So I'm trying to deal with the fact that, when the Basic map service has a numeric value (ID= 0), the site inheritance causes the Map Service ID to get renamed & workflow to not be available / work. I modified my workflow GetMapServiceID activity to pass an argument (which works successfully for the parent viewer), thinking I could pass the distinct ID reference to each viewer in a properties value. But that doesn't resolve the workflow name (rename) reference issue in the 'I Want to Menu' config. If I change it there, it breaks the source viewer (as the documentation warns).

I thought that I could maybe circumvent that issue by modifying the Map Service ID to a unique name (vs. default numeric value). So I modified the ID in the site.xml file. Quick checks showed a couple of the searches to work but appears to complete ignore/undo the hours of layer/attribute/results configuration for the site.

Guessing I'm missing something basic in either of these 2 approaches..???..

Insights on what I may be missing?

 

 

 

0

• 

  Todd Sales

  June 20, 2013 22:02

  May be helpful for me to ask a more direct question here - Have others encountered this problem, and if so, what approach did you use to address it?

  Thanks!

  0
• 

  Tom Neer

  June 22, 2013 02:39

  Ran into this problem a while back. According to Malcolm @ LG there is no viewer inheritance only site inheritance. 

  What we end up doing is setting up our parent site and viewer. Once we are happy with the site and viewer, we backup the viewer and then delete it from the parent site. This is important as if you have a viewer in the parent site, it gets messy really quick. We then manually copy over parent viewer into the child site and make appropriate edits to integrate with the child site.

  Hopefully viewer inheritance will be coming.

  0

Please sign in to leave a comment.