Using the Report Generator in Workflow

Created: 23 Sep 2012 | Updated: 24 Sep 2012
reecardo's picture
Login to vote
0 0 Votes
Symantec single video player.

This is a how to video on using the Report Generator in Workflow. In this video, you will see how to generate a component against an existing SMP report and use the generated component in a workflow.

For more information, please see the guide at the following location:
www.symantec.com/docs/DOC4824

Filed Under

Comments

Nonos's picture
Nonos
Partner
24
Sep
2012
Votes
0

Really nice video, but be

Really nice video, but be adviced that the default SMP Reports (7.1 SP2) are not working as stated in the video.

So only user created reports will work as expected.

I opened a case about that a couple of months ago.

 

Regards,

 

Cédric DUBIE

reecardo's picture
reecardo
Symantec Employee
25
Sep
2012
Votes
0

What issue were you having

What issue were you having with the default reports? Is it certain variables behaving badly?

Hopefully, in 7.5, you have a little more flexibility because you can exclude certain parameters from being shipped off to the ReportManagment web service (using the Include * in Parameters properties)

Nonos's picture
Nonos
Partner
26
Sep
2012
Votes
0

It seems the schema that is

It seems the schema that is given to the Generator doesn't correspond to the parameters awaited by the SMP.

Check Case 418-883-395.

 

Regards,

 

Cédric DUBIE

reecardo's picture
reecardo
Symantec Employee
26
Sep
2012
Votes
0

Basically the

Basically the RunReportsWithParameters method in ReportManagement on the SMP has 2 parameters: a report GUID, and a delimited key value pair set that gives the parameters and the values to run the report with. It'll look like this: <parameter a>=<value a>;<parameter b>=<value b>;etc.

I know there was an issue recently fixed that dealt with the parameter names being shipped off. We weren't preserving the original name of the parameter (if it had spaces) and tried to "cobble" it back together before the service call; that's been fixed for 7.5.