Verify relationships so that appropriate results are returned in reports% set a!!re!ate rules so that some data in reports is avera!ed rather than totaled% spe$ify the default date prompt behavior hen $reatin! a prompt pa!e in report #tudio% and add s$reen tips and des$riptions.
Verify relationships so that appropriate results are returned in reports% set a!!re!ate rules so that some data in reports is avera!ed rather than totaled% spe$ify the default date prompt behavior hen $reatin! a prompt pa!e in report #tudio% and add s$reen tips and des$riptions.
Verify relationships so that appropriate results are returned in reports% set a!!re!ate rules so that some data in reports is avera!ed rather than totaled% spe$ify the default date prompt behavior hen $reatin! a prompt pa!e in report #tudio% and add s$reen tips and des$riptions.
Demo 1: Verify Relationships and Query Item Properties
Purpose: We have imported database metadata into our GO Operational model. We must no prepare the model to meet reportin! re"uirements. #pe$ifi$ally% e ant to verify and modify relationships so that appropriate results are returned in reports% set a!!re!ate rules so that some data in reports is avera!ed rather than totaled% add $urren$y formattin!% spe$ify the default date prompt $ontrol behavior hen $reatin! a prompt pa!e in Report #tudio% and add s$reen tips and des$riptions. On$e e have implemented these $han!es% e ill re&publish the GO Operational pa$'a!e and vie the results in Report #tudio. Task 1. Verify property settings. 1. Start Framework Manager, click Open a project, and navigate to C:\Edcognos\C88152\C8FM-04- Prepare_Metadata_in_Frameor!_Manager\"tarting Point Mode#. 2. Open the $O Operationa#%cp& and log on using admin as the user ID and Ed'cation1( as the password. 3. In the ro!ect "iewer, e#pand $O Operationa# Mode#, )ata "o'rce *ie, gosa#es, and CO+,-./. $otice that ISO%&'())%*)&&)(%+OD), ISO%&,O%*)&&)(%+OD), and ISO%&'())%DI-I&%+OD) are not set as identi.ers. &hese items are all strings and are not inde#ed in the data/ase. I0 we 0elt that report authors would .lter on these items regularl1, we could ask the data/ase administrator to inde# them in the data/ase. (eport authors could also use +O2$&(3%+OD), which is inde#ed, as the lookup value, and would not need to inde# the other items. 4. )#pand 0,*E,-O./_1E*E1", and then click C1O"0,$_0,*E,-O./. 5. In the roperties pane, scroll down to the (egular 6ggregate propert1. $otice the value is set to sum. +*OSI$-%I$")$&O(3 is a non7additive value and there0ore, in the ma!orit1 o0 cases, should not /e aggregated. I0 authors re8uire a certain t1pe o0 aggregation 0or the +*OSI$-%I$")$&O(3 values, the1 can set the aggregation t1pe in 9uer1 Studio or (eport Studio as re8uired. :. +lick in the /o# to the right o0 the (egular 6ggregate propert1, and then 0rom the list, click +ns'pported. ;. )#pand O.)E._)E-201", click +,0-_CO"-, and then +trl<click +,0-_P.0CE and +,0-_"21E_P.0CE. roperties 0or all three items are displa1ed in the roperties pane. =. In the roperties pane, scroll to the right until the (egular 6ggregate propert1 is in view. >. +lick in the /o# at the intersection o0 the 2$I&%+OS& row and the (egular 6ggregate column, and then 0rom the list, click 23erage. C O G N O S 8 B I - M E T A D A T A M O D E L I N G P A R T 1 1?. Drag the small /lack arrow /eneath the value downward to change the values to 6verage 0or the other two 8uer1 items. 11. In the ro!ect "iewer, e#pand P.O)+C-, and then repeat step 4 to change the 2sage propert1 value to 2nknown 0or (OD2+&IO$%+OS& and M6(-I$. +urrentl1 we do not know how these values will /e used. 12. In the ro!ect "iewer, e#pand "21E"_"-2FF, and then change the 2sage propert1 to 6ttri/ute 0or M6$6-)(%+OD). &his .eld is an integer in the data/ase /ut was not inde#ed. &here0ore, Framework Manager recogni@ed it as a 0act. &his ma1 /e a good candidate 0or inde#ing in the data/ase and should /e discussed with the data/ase administrator. 13. In the ro!ect "iewer, e#pand -0ME_)0ME,"0O,, and then change the 2sage propert1 to 6ttri/ute 0or MO$&'%A)3, +2(()$&%MO$&', 926(&)(%A)3, +2(()$&%926(&)(, +2(()$&%3)6(, D63%OF%,))A, D63%OF%MO$&', D63S%I$%MO$&', D63%OF%3)6(, ,))A%OF%MO$&', ,))A%OF%926(&)(, and ,))A%OF%3)6(. Task 2. Verify and modify relationships. 1. In the ro!ect In0o view, click )iagram, e#pand )ata "o'rce *ie, and then e#pand gosa#es. &he 8uer1 su/!ects 0rom gosales appear in the o/!ect diagram. 2. In the ro!ect "iewer, e#pand the gosa#es namespace, right7click O.)E._)E-201", and then click 1ocate 0n )iagram. 3. In the diagram, dou/le7click the relationship /etween the O(D)(%D)&6I*S and ()&2($)D%I&)M 8uer1 su/!ects. &he (elationship De.nition dialog /o# appears. ,e can see that the two 8uer1 su/!ects are related through a common 8uer1 item called O(D)(%D)&6I*%+OD). ,e can also see 0rom the (elationship impact that it is a mandator1 relationship, where/1 each O(D)(%D)&6I* has one or more ()&2($)D%I&)M. *etBs test this cardinalit1 to see i0 it is correct. 4. +lick O4. 5. In the diagram, +trl7click O.)E._)E-201_CO)E in /oth O(D)(%D)&6I*S and ()&2($)D%I&)M.. 2 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", P R E P A R E M E T A D A T A I N . R A M E / O R 0 M A N A G E R :. (ight7click O.)E._)E-201_CO)E Cin either 8uer1 su/!ectD, and then click -est. $otice that there are no missing values in either column. ;. +lick C#ose, and then, in the diagram, dou/le7click the relationship /etween O(D)(%D)&6I*S and ()&2($)D%I&)M. =. +hange the cardinalit1 0or ()&2($)D%I&)M 0rom 1..n to 0%%n. &he results appear as shown /elowE >. +lick O4, and then repeat steps 5 and : to re7test. $otice that there are values missing in the second column. &his is /ecause not all orders in our data have returns associated with them, and /ecause users want to report on all orders whether or not the1 have returns. &here0ore, we will leave the relationship as optional. &his is a good test to per0orm on all relationships to see i0 there will /e an impact on the data returned. In some reporting scenarios, e#cluding the e#tra data ma1 /e desired, in which case 1ou would leave the relationship as mandator1. 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", C O G N O S 8 B I - M E T A D A T A M O D E L I N G P A R T 1 1?. +lick C#ose. Fecause users want to report on these sales staG whether or not the1 have sales targets, we will make the relationship /etween S6*)S%S&6FF and S6*)S%&6(-)& optional. 11. In the ro!ect "iewer, under the gosales namespace, right7click "21E"_"-2FF, and then click 1ocate 0n )iagram. 12. Dou/le7click the relationship /etween "21E"_"-2FF and "21E"_-2.$E-. &he (elationship De.nition dialog /o# appears. 13. Modi01 the relationship so that the result appears as shown /elowE 14. +lick O4. 15. Save the pro!ect. 1 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", P R E P A R E M E T A D A T A I N . R A M E / O R 0 M A N A G E R Task 3. Set formatting and aggregate rules. 1. In ro!ect "iewer, in the gosales namespace, under the O(D)(%D)&6I*S 8uer1 su/!ect, +trl<click the +,0-_CO"-, +,0-_P.0CE, and +,0-_"21E_P.0CE 8uer1 items. 2. In the 2$I&%+OS& row o0 the Format column, click 5C#ic! to edit6. &he Data Format dialog /o# appears. 3. In the Format t1pe list, click C'rrenc7, in the +urrenc1 row o0 the roperties section, select 89+"): - +nited "tates o& 2merica; do##ar, and then click O4. 4. Drag the small /lack arrow /eneath the value downward to change the 0ormat to currenc1 0or the other two 8uer1 items, 2$I&%(I+) and 2$I&%S6*)%(I+). 5. +lick O4. Task 4. Define the default behavior of a prompt control. 1. In the gosales namespace, e#pand the -0ME_)0ME,"0O, 8uer1 su/!ect. 2. +lick the )2/_)2-E 8uer1 item, and then in the list o0 properties in the roperties pane, e#pand the Prompt 0n&o propert1. 3. +lick in the /o# ne#t to the rompt &1pe propert1, and then in the list, click "e#ect )ate. &his will create a prompt with a calendar onl1 instead o0 a calendar and time selection. Task . !dd descriptions and screen tip. 1. )#pand the O.)E._<E2)E. 8uer1 su/!ect, and then click the O.)E._,+M=E. 8uer1 item. 2. In the roperties pane, in the Description row, t1pe ->e order n'm?er 'ni@'e#7 identiAes eac> order, and then press Enter. 3. In the Screen &ip row, t1pe Order ,o, and then press Enter. 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", C O G N O S 8 B I - M E T A D A T A M O D E L I N G P A R T 1 4. 6t the /ottom o0 the roperties window, click the 1ang'age ta/. $otice that 0or the $ame, Description and Screen &ip properties, 1ou now see one entr1 0or all languages C)nglish, )nglish CHim/a/weD and FrenchD. 'owever, all entries are in )nglish. 5. In the O(D)(%')6D)( 8uer1 su/!ect, click the .E-201E._,2ME 8uer1 item. &he description and screen tip are /lank 0or all languages. ,e cannot add a French or )nglish CHim/a/weD value 0or either the description or screen tip until we suppl1 a value 0or the primar1 language C)nglishD. :. In the Description section, in the )nglish /o#, t1pe .etai#er ,ame, and then press Enter. ;. +lick the Frenc> /o#. ,e can now add a French value, /ecause we have supplied a value 0or the primar1 language. =. Delete the e#isting te#t, t1pe ,om de )Btai##ant, and then press Enter. >. In the Screen &ip section, in the )nglish /o#, add .etai#er ,ame, and then in the French /o#, add ,om de )Btai##ant. 1?. Save the pro!ect. Task ". #e$publish the model and create a report. 1. (e7pu/lish the $O Operationa# package. 2. In +ognos +onnection, open .eport "t'dio, and then click $O Operationa#. 3. +lick Create a ne report, dou/le7click 1ist, and then in the Inserta/le O/!ects pane, e#pand )ata "o'rce *ie and gosa#es. 4. In gosales, e#pand "21E"_"-2FF, right7click M2,2$E._CO)E, and then click Properties. $otice that the usage o0 this 8uer1 item is set to attri/ute, which is what we speci.ed in &ask 1. 5. +lick C#ose, e#pand O.)E._<E2)E., and then dou/le7click .E-201E._,2ME to add it to the report. 6 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", P R E P A R E M E T A D A T A I N . R A M E / O R 0 M A N A G E R :. )#pand O.)E._)E-201", and then dou/le7click +,0-_CO"-, +,0-_P.0CE, +,0-_"21E_P.0CE, and C+2,-0-/ to add them to the report. ;. +lick the +,0-_CO"- column, and then in the roperties pane, scroll down to the 6ggregate Function propert1, under Data Item. $otice that the value o0 the 6ggregate Function propert1 is set to 6verage rather than &otal. &his is due to the aggregate setting that we speci.ed in &ask 1 0or 2$I&%+OS&, 2$I&%(I+), and 2$I&%S6*)%(I+). =. On the tool/ar, click .'n .eport . &he result appears as shown /elowE &he values in the 2$I&%+OS&, 2$I&%(I+), and 2$I&%S6*)%(I+) columns are averaged and 0ormatted as currenc1, while the 926$&I&3 column is totaled and remains un0ormatted. >. +lose +ognos "iewer. 1?. On the tool/ar, click ,e , and then click ,o to saving the previous report. 11. Dou/le7click 1ist to create a new list report, and then in the Inserta/le O/!ects pane, e#pand -0ME_)0ME",0O,. 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", C O G N O S 8 B I - M E T A D A T A M O D E L I N G P A R T 1 12. Dou/le7click )2/_)2-E to add it to the report, click the )2/_)2-E column, and then on the tool/ar, click ='i#d Prompt Page . 6 prompt page is /uilt automaticall1 that includes controls 0or selecting a speci.c date range rather than a date and time range. &his is due to the prompt control setting that we speci.ed in &ask 4. Task %. &reate a report to verify 'nglish screen tips and descriptions. 1. From the Fi#e menu, click ,e. 2. In the Inserta/le O/!ects pane, e#pand O.)E._<E2)E., and then dou/le7 click O.)E._,+M=E. to add it to the report. 3. In the Inserta/le O/!ects pane, in O(D)(%')6D)(, point to O.)E._,+M=E.. 6 screen tip appears, containing the te#t COrder $oD that we speci.ed 0or the screen tip propert1 in &ask 5. 4. In the Inserta/le O/!ects pane, right7click O.)E._,+M=E., and then click Properties. In the Description row o0 the roperties dialog /o#, the te#t appears that we speci.ed 0or the Description propert1 in &ask 5. 5. +lick C#ose, and then in O(D)(%')6D)(, point to ()&6I*)(%,2ME. 6 screen tip appears, containing the )nglish te#t that we speci.ed in &ask 5. Task (. &reate a report to verify )rench screen tips and descriptions. 1. +lose (eport Studio, and then click ,o to saving the report. 2. 6t the top o0 the page, in +ognos +onnection, click Pre&erences. &he Set pre0erences page appears. 3. 2nder (egional optionsI+ontent language, click +se t>e &o##oing #ang'age, in the list click Frenc>, and then click O4. $otice that the user inter0ace language 0or content has changed to French. 4. 6t the top o0 the page, click .eport "t'dio. &he Select a package page appears. ,e are opening the French version o0 the -O Operational model. $otice that the package name is pre.#ed with C0rD. 5. +lick 9&r: $O Operationa#. 8 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", P R E P A R E M E T A D A T A I N . R A M E / O R 0 M A N A G E R :. +reate a *ist report. (eport Studio opens with the metadata 0rom the C0rD -O Operational model appearing in the Inserta/le O/!ects pane. $otice that all items are pre.#ed with C0rD. ;. )#pand 9&r: )ata "o'rce *ie, 9&r: ,e ,amespace, and 9&r: ,e ,amespace1. =. )#pand 9&r: O.)E._<E2)E., and then point to 9&r: .E-201E._,2ME. 6 screen tip appears, containing the te#t C$om de DetaillantD that we speci.ed 0or the French screen tip propert1 in &ask 5. >. (ight7click 9&r: .E-201E._,2ME, and then click Properties. In the Description row o0 the roperties dialog /o#, the te#t appears that we speci.ed 0or the Description propert1 in &ask 5. 1?. +lick C#ose, close (eport Studio without saving changes. 11. 6t the top o0 the page, in +ognos +onnection, click Pre&erences. 12. 2nder (egional optionsI+ontent language, click +se t>e de&a'#t #ang'age, and then click O4. *eave +ognos +onnection and Framework Manager open 0or the ne#t demo. Results: We performed modelin! a$tivities that prepared the GO Operational metadata model for reportin!. We verified and modified "uery item properties and relationships and republished the GO Operational pa$'a!e. We vieed the results in Report #tudio. 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", C O G N O S 8 B I - M E T A D A T A M O D E L I N G P A R T 1 Demo (: )dd *ultilin!ual #upport for *etadata Purpose: We ant to ensure that users or'in! in lan!ua!es other than +n!lish $an easily use the GO Operational model to $reate reports. ,o this end% e ill enhan$e the model by e-portin! a translation file and modifyin! it so that it $ontains .ren$h and +n!lish strin!s. We ill then import this file ba$' into the model and vie the results. /astly% e ill re&publish the GO Operational pa$'a!e and e-amine the impa$t of implementin! support for multilin!ual metadata in Report #tudio. Task 1. *odify +uery items for multilingual support and e,port a &SV file. 1. In Framework Manager 0rom the ro!ect menu, point to 1ang'ages, and then click EDport -rans#ation Fi#e. &he )#port &ranslation File dialog /o# appears. 2. 2nder the ro!ect *anguages pane, +trl<click Eng#is> and Frenc>, and then click 2dd to move them to the *anguages to /e e#ported pane. 3. $e#t to the )#port languages in this .le /o#, click =rose . &he )#port *anguage &ranslation File dialog /o# appears. 4. In the Save as t1pe /o#, click C"* 9comma de#imited: 9E%cs3:. 5. $avigate to C:\Edcognos\C88152\Prepare_Metadata, in the File name /o#, t1pe $O_2pp#ication_1OC%cs3, and then click "a3e. :. +lick O4. 6 message appears, indicating that the language strings were success0ull1 e#ported. ;. +lick O4, open ,indows )#plorer, and then navigate to C:\Edcognos\C88152\Prepare_Metadata. 10 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", P R E P A R E M E T A D A T A I N . R A M E / O R 0 M A N A G E R =. Open -O%6pplication%*O+.csv in )#cel, and then e#pand the .rst two columns. &he result appears as shown /elowE $otice that each column represents a given languageJ in this case, )nglish and French. &hese are /ased on the language selections we made when we e#ported the model languages in previous steps. >. In the second column o0 row ;, change the French value o0 C0rD +I&3 to *011E. 1?. In the second column o0 row 1?, change the French value o0 C0rD +O2$&(3 to P2/". &he result appears as shown /elowE 11. Save and close the .le. Task 2. -mport a &SV file that contains translated strings. 1. In Framework Manager, 0rom the Project menu, point to 1ang'ages, and then click 0mport -rans#ation Fi#e. &he Import &ranslation File dialog /o# appears. 2. In the ro!ect *anguages pane, click Frenc>, and then click 2dd to add it to the &ranslate into pane. 3. $e#t to the Import translation ta/le 0rom this .le /o#, click =rose. 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", C O G N O S 8 B I - M E T A D A T A M O D E L I N G P A R T 1 &he Import *anguage &ranslation File dialog /o# appears. 4. In the Files o0 t1pe /o#, click C"* 9comma de#imited: 9E%cs3:, and then navigate to C:\Edcognos\C88152\Prepare_Metadata. 5. +lick $O_2pp#ication_1OC%cs3, click Open, and then click O4. 6 message appears indicating that the import was success0ul and the details o0 the properties that were updated in the model o/!ects. :. +lick O4. ;. In the ro!ect "iewer pane, ensure that the gosales is e#panded. =. In the gosales namespace, click CO+,-./, and then in the roperties pane, click the 1ang'ages ta/ i0 it is not alread1 selected. &he result appears as shown /elowE $otice that the French value 0or the $ame propert1 o0 the +O2$&(3 8uer1 su/!ect reKects the change that we made to the translation .le. >. In the gosales namespace, e#pand the "21E"_=.2,C< 8uer1 su/!ect, and then click the C0-/ 8uer1 item. $otice that the French value 0or the $ame propert1 o0 the +I&3 8uer1 item reKects the change that we made to the translation .le. 1?. Save the pro!ect. Task 3. #e$publish the model and vie. the results in #eport Studio. 1. (e7pu/lish the -O Operational package. 2. In +ognos +onnection, at the top o0 the page, click Pre&erences. 3. 2nder (egional optionsI+ontent language, click +se t>e &o##oing #ang'age, in the list click Frenc>, and then click O4. 4. Open (eport Studio using the C0rD -O Operational package, and then create a list report. 5. In the Inserta/le O/!ects pane, e#pand 9&r: ,e ,amespace and 9&r: ,e ,amespace1. $otice that, in C0rD $ew $amespace the name o0 the +O2$&(3 8uer1 su/!ect has /een changed to 63S, which is the value that we imported into the -O Operational 0rom the translation .le. 12 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", P R E P A R E M E T A D A T A I N . R A M E / O R 0 M A N A G E R :. In C0rD $ew $amespace1, e#pand 9&r: "21E"_=.2,C<. $otice that the value o0 the +I&3 8uer1 item has /een changed to "I**), which is the value that we imported into the -O Operational model 0rom the translation .le. ;. +lose (eport Studio without saving. =. 6t the top o0 the page, in +ognos +onnection, click Pre&erences. >. 2nder (egional optionsI+ontent language, click +se t>e de&a'#t #ang'age, and then click O4. *eave +ognos +onnection and Framework Manager open 0or the ne#t demo. Results: We enhan$ed the GO Operational model by e-portin! the model lan!ua!es to a translation file. We modified this file so that it $ontained .ren$h and +n!lish strin!s. We imported the file ba$' into the model and vieed the results. We re&published the pa$'a!e and e-amined the impa$t of implementin! support for multilin!ual metadata in Report #tudio. 0sers $an no be!in to or' ith the GO Operational model in lan!ua!es other than +n!lish. 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", C O G N O S 8 B I - M E T A D A T A M O D E L I N G P A R T 1 Demo (: 1reate #tand&alone .ilters Purpose: Report authors have re"uested re&usable filters for the 1ampin! +"uipment and *ountaineerin! +"uipment produ$t lines. ,his ill ma'e filterin! easier for them as they $reate their reports. We ill $reate stand&alone filters to handle this re"uest. Task 1. &reate stand$alone filters. 1% In the ro!ect "iewer, right7click the gosa#es namespace, point to Create, and then click Fo#der. &he +reate Folder ,i@ard appears. 2% In the Folder name /o#, t1pe Prod'ct 1ine Fi#ters, click ,eDt, and then click Finis>. F% (ight7click the Prod'ct 1ine Fi#ters 0older, point to Create; and then click Fi#ter. &he Filter De.nition dialog /o# appears. 4% In the $ame /o#, t1pe Camping E@'ipment. 5% In the 6vaila/le +omponents pane, e#pand the $O Operationa# Mode#, )ata "o'rce *ie, and the gosa#es namespaces, and the P.O)+C-_10,E 8uer1 su/!ect. G% Drag the P.O)+C-_10,E_CO)E 8uer1 item to the )#pression De.nition pane, and then at the end o0 the e#pression, t1pe H 1. &he e#pression de.nition appears as shown /elowE LgosalesM.L(OD2+&%*I$)M.L(OD2+&%*I$)%+OD)M N 1 I% +lick O4. 8% (epeat steps 3 to : to create a stand7alone .lter called Mountaineering )8uipment, with the 0ollowing e#pressionE LgosalesM.L(OD2+&%*I$)M.L(OD2+&%*I$)%+OD)M N 2 J% Save the pro!ect. 11 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", P R E P A R E M E T A D A T A I N . R A M E / O R 0 M A N A G E R Task 2. Test filters in /uery Studio. 1. (e7pu/lish the -O Operational package. 2. In +ognos +onnection, open 9uer1 Studio. 3. +lick the $O Operationa# package. 4. +reate a report using the 0ollowing items 0rom the gosales namespaceE (OD2+&%*I$) 0rom (OD2+&%*I$) (OD2+&%&3)%)$ 0rom (OD2+&%&3) 6ctual (evenue 0rom O(D)(%D)&6I*S lanned (evenue 0rom O(D)(%D)&6I*S -ross ro.t 0rom O(D)(%D)&6I*S $otice the 6ctual (evenue, lanned (evenue, and -ross ro.t calculations, and the 2SD currenc1 0ormatting 0or each. &hese 8uer1 items were created and 0ormatted in Framework Manager in previous demos. 5. In the report, +trl<click the P.O)+C-_10,E and P.O)+C-_-/PE_E, columns, and then on the tool/ar, click $ro'p . &he report appears as shown /elowE :. From the Insert Data menu, e#pand the Prod'ct 1ine Fi#ters 0older, and then drag the Camping E@'ipment .lter on to the report. $otice the report is now .ltered on +amping )8uipment. 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g", C O G N O S 8 B I - M E T A D A T A M O D E L I N G P A R T 1 ;. On the tool/ar, click 2ndo , and then drag the Mo'ntaineering E@'ipment .lter onto the report. &he report is now .ltered on Mountaineering )8uipment. =. +lick Cognos Connection, and do not save changes. *eave +ognos +onnection and Framework Manager open 0or the ,orkshop. Results: We $reated stand&alone filters based on produ$t lines and made them available to Report )uthors. ,hey $an no "ui$'ly add these filters hen $reatin! reports. 16 2006, Cognos Incorpor!"# T$%s g&%#" con!%ns propr%"!r' %n(or)!%on *$%c$ %s pro!"c!"# +' cop'r%g$!, No pr! o( !$%s #oc&)"n! )' +" p$o!ocop%"#, r"pro#&c"#, or !rns-!"# %n!o no!$"r -ng&g",