Typical Task Workflow

The task execution sequence described below represents a typical workflow that can be created and tested using the Task Processor Administrator application.

1. Invoke the projects task to gather project information.

   You can enter either a specific Intelligence Server machine or omit it entirely. The result is an XML structure that contains the following information for each project:

   • Project Name (name)

   • Project ID (id)

   • Project Description (desc)

   • Intelligence Server hosting the project (server)

2. Use the login task to create a session in one of the projects whose information was gathered in the previous step.

   Copy the value of the session-state element into the Clipboard for use in the next step. 

3. Use the folderBrowse Task to view the contents of this project.

   Use the value of the session-state element (that you copied to the Clipboard in the previous step) as the value for the sessionState parameter. You can enter values for the other parameters, but they are optional. The result is an XML structure that includes for each object:

   • Object Name (n)

   • Object ID (id)

   • Object Description (d)

   • Object Type (t)

   • Object Subtype (st) 

   With these values, you can browse to a folder containing a report or document that you want to execute.

   If you supply only the sessionState parameter and no other parameters, it simply returns the contents of the Shared Reports folder.

4. Use the reportExecute task to execute a report in one of the folders.

   You need the object ID of the report that you want to execute. For the name of the style, you can use the name of any existing report style in the Style Catalog Configuration file. For example, you can use the "ReportDataVisualizationXMLStyle", which is the name of a style that is used to generate report XML for the Visualization Framework. 

5. Use the RWExecute task to execute a document in one of the folders.

   You need the object ID of the document that you want to execute.  For the name of the style, you can use the name of any existing document style in the Style Catalog Configuration file. For example, you can use the"ResultSetStatusStyle" to display information about the executed document. This XML includes information such as:

   • Object ID

   • Message ID

   • Whether the document is prompted or not

   Alternatively, you can use the "RWDataVisualizationXMLStyle" to display document XML in the form used by the Visualization Framework.

6. Finally, use the logout task to close the previously opened session on MicroStrategy Intelligence Server.