Education & Training
Services & Support
to create and rate content, and to follow, bookmark, and share content with other members.
Project Storyboard - cop_storyboard.rod - where can I find the datasources
Question asked by
on Mar 1, 2010
on Mar 2, 2010 by Owen_R
Show 0 Likes
hi all,I am trying to amend the cop_storyboard.rod file, and cannot see where the report gets its data from?It has several sections.Can anyone point me in the right direction so I can see what queries are behind the data?Regards,Matt
No one else has this question
Mark as assumed answered
This content has been marked as final.
Show 3 comments
(Required, will not be published)
Mar 1, 2010 1:13 PM
Hi, This kb article will help you to understand the report
Show 1 Like
Mar 2, 2010 3:52 AM
Thanks for the link, Sundar, most helpful :-) now, I have a couple of further questions.I'm clicking around the design and trying to find where/how the project parameter gets passed into the various queries? also, the sections have labels with the text like 'ProjectDescriptionKey'how does the report/Actuate translate that to just read 'Project Description' when the report it run? Regards,Matt
Show 0 Likes
Mar 2, 2010 7:07 AM
Take a look at the query sources that are in the cop_storyboard.rol file that comes with the design. If you look at the ObtainSelectStatement method override on SQLMaintextQuery that there is dynamic SQL: SelectStatement = SelectStatement & " AND p.id = " & NewReportApp::param_project param_project is the value passed from Clarity. If the MainText Query finds a row then the project ID from the row is stored as a global variable within the report via the OnRead method of the SQLMainRow data row: NewReportApp::global_project_id = project_id I haven't looked but I'd guess that global variable is then used to filter data further down the report. As for the labels, this is to do with the support for multiple languages in Clarity. Basically it gets the values for the label text in each language in the TransReport section by querying CMN_RPT_Labels_V. The label class then has a call on its start method to translate the key value into whatever language you're using. So ProjectDescriptionKey then displays as Description in English, Description du projet in French etc. Take a look at the function TranslateValue in the NikuUtilities BAS file to trace what it does.
Show 0 Likes
Retrieving data ...
Custom Assertion accessing request/response headers
CA ITSM - Ask a Question, Get an Answer (November 16 - November 23)
CA Service Catalog widgets and Kentico portal
Try Out CA Service Virtualization 9.0 for Free for 30-days
Where would you like us to offer a 30-day free trial?