Workflow to EMail a map

Permanently deleted user

29. Februar 2012 02:44

Good day,

I'm trying to build a workflow to send an email containing a map to someone. I'm currently still trying to figure out how to tackle this task. This workflow would be launched from a flex viewer through code so input arguments will be provided for the email parameters (To, From Subject, Body). The map has to be the full extent of the currently visible map in the viewer.

My first question is, what is the better activity to generate the report? Template Report or simply Report. My feeling is theTemplate Report since it seems to offer a way to generate a report from a template that doesn't not have to associated to a layer through the REST Manager (Using the report URI instead of the report Id).

Second question, what is the correct way of sending the input arguments from code. When I use the WorkflowControllerProxy.startWorkflow function, the third parameter is simply described as an array (in flex). My guess is that it is a dictionary type array where :

arg["input param name"] = value

Third question, what should the dataset value be in the Template Report activity? Do I have to convert my map into a DataSet and send it as an input parameter or something to this effect?

Any help and suggestions will be greatly appreciated,

 

 

0

• 

  Ethan Granger

  8. März 2013 06:13

  Andrea,

  I too would like to create an html formatted email with some attribute information and a map. Did you ever figure out how to go about this?

  Thanks

  0
• 

  Permanently deleted user

  8. März 2013 18:40

  Hi Ethan, Andrea

  See http://support.geocortex.com/SupportForums/Thread.aspx?thread=47152&mid=2&pageid=0&ItemID=20&pagenumber=1#post140297

  @Andrea: Template Report is a server-side activity where you specify the physical location of the report template RPX file and have to manually construct the DataSet that feeds into the report (i.e. you would have to download the map image and other resources such as data links etc and create tables to hold that information within the DataSet). This activity is useful when you need fine-grained control over the inputs of a report but it is more complex than using the Report activity.  

  On the other hand, the Report activity  triggers a report to run on the client. The URL returned by the report activity is a short-lived URL (5 minutes from time of most recent access). It should not be emailed or stored for later use as Ralph mentioned earlier. The trick here is to use a WebRequest activity in workflow to download the report and attach it to an email message. This approach is demonstrated in the linked post above.

  Regards,

  --Alejandro

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.