Changes

CrossLinked Reports

6,102 bytes added, 13:58, 31 January 2018

no edit summary

The linking is done usually by putting a "CrossLink" type field in the second form. i.e. a "Basic - Campaign Listing" type or "Basic - Campaign Search"

== Background ==

CrossLinked reports would be considered an advanced setup report due to the complexity of the options available. Cross Linked campaigns allow you to associate children records to parent records. There are many instances where a Parent and Child form are linked. Examples include:

For HR training records

* Parent = Staff Member

* Child = Examination result

For Case management

* Parent = Customer

* Child = Case

For Order management

* Parent = Order

* Child = Order Item

For Billing management

* Parent = Client

* Child = Work Tickets

In each of these scenarios there is a parent form. In the second form a “Cross Campaign” type is added. Setting up linked databases in BE is easy using the “Basic – Campaign Search” and “Basic – Campaign Listing” types when building databases. This question type is linked back to the parent form. Records added to the child form are associated with a parent record.

It becomes important then to be able to look up a parent record and display all the relevant children records.

This report is called a Cross Linked report.

[[File:CrossLinked_Demo001.png|800px]]

[[File:CrossLinked_Demo002.png|800px]]

[[File:CrossLinked_Demo003.png|800px]]

[[File:CrossLinked_Demo004.png|800px]]

[[File:CrossLinked_Demo005.png|800px]]

Cross Linked Options

[[File:CrossLinked_Demo006.png|800px]]

[[File:CrossLinked_Demo007.png|800px]]

[[File:CrossLinked_Demo009.png|800px]]

[[File:CrossLinked_Demo008.png|800px]]

[[File:CrossLinked_Demo010.png|800px]]

[[File:CrossLinked_Demo011.png|800px]] In the Interaction Options we can also enable the "Show Child Headers" which adds the column headings for the children. [[File:CrossLinked_Demo012.png|800px]] == Worked Example - Multiple listings == Cross Linked reports easily handle multiple companies on the same report. For this example we add two more companies. Nikkon Express and All n One Limited. [[File:CrossLinked_Demo013.png|800px]] They're not alphabetically sorted, they're sorted by ID. So we tweak the listing by modifying the fields and sequence of the report to order by Business Name. [[File:CrossLinked_Demo014.png|800px]] [[File:CrossLinked_Demo015.png|800px]] No we go in and add two different contacts each. [[File:CrossLinked_Demo016.png|800px]] == Worked Example - Child Rules == It is possible to apply rules to the children records to perform mathematical calculations within the report. The following example adds a rule to count the number of contacts each parent has. [[CrossLinked_Calculation_Fields]] gives examples of how this field is used. In our example we add "count#strCDA_616_field_1_2#child;" to the "Child Calculation Fields". You can see in the output report to the right, the count, with the summation total of 6 at the bottom. [[File:CrossLinked_Demo017.png|800px]] [[File:CrossLinked_Demo018.png|800px]] == Worked Example - Limiting the report by parameter == To allow these reports to be very selective and only show one parent record at a time, it is possible to pass via QueryString parameter the Id or other limiting factor into the grouping. Lets say for example we wanted the report to only show the All n One company example... i.e. Parent ID = 3 Firstly we modify the Customised Group parameters to look for an Id. "Campaign Group - Grouping Parameters" modify this to look for the static Id of 3 [[File:CrossLinked_Demo019.png|800px]] Then we modify the parameters to let it know to go looking for a changing value [[File:CrossLinked_Demo020.png|800px]] If we pull the report we don't get an answer we want [[File:CrossLinked_Demo021.png|800px]] We need to modify the URL of the query slightly. we change it from "rptCrossLinked.asp?ID=146" to "rptCrossLinked.asp?intGroup_Id=146&intCampaign_Id=615" through the Control Bar module. After modifying the query, we get: [[File:CrossLinked_Demo022.png|800px]] We then want to extend the query even further by making the Id to display dynamic. We change the URL to "rptCrossLinked.asp?intGroup_Id=146&intCampaign_Id=615&intCDA_615_Id=3" We change the "Campaign Group - Grouping Parameters" to look for --intCDA_615_Id-- [[File:CrossLinked_Demo023.png|800px]] Now pulling the report we get: [[File:CrossLinked_Demo024.png|800px]] Using this final parameter we can change the ID to anything. This then opens up the possibility of using this report from anywhere just by passing in the Id of the record to display. The primary areas to use this from are:* Worklists: redirection to an alternate URL and append in the ID of the record clicked* Outcomes: redirection to an alternate URL and append in the ID of the parent, or parent of the child record. == Worked Example - Including eCourse Assets == The final customisation of the report enables your own custom HTML to be included on the page as well to add an infinite amount of flexibility to the report. By specifying the Asset Id of the item you wish to display in the report, it will be rendered below the report. If you put HTML including JavaScript, you can use the items above to perform extensive customisations. Main Menu > Data Profiling > Customised - Group Management > Group - Edit Cross Linked Campaign Engine Settings > Demo - CrossLinked - Business > Choose your Customised Group > Interaction Options > eCourse Asset Ids. You can add multiple assets separated by commas. In this example the asset draws the photo of Polar Bear and cub. [[File:CrossLinked_Demo025.png|800px]] == Worked Example - Work Flow == If as mentioned above in "Limiting the report by parameter", you wish to use the report to drive activity, the buttons on page can be change to "open in a new window" or to "continue processing in the current window" Main Menu > Data Profiling > Customised - Group Management > Group - Edit Cross Linked Campaign Engine Settings > Demo - CrossLinked - Business > Choose your Customised Group > Interaction Options > Flow Control * SameWindow : Means that the new processing will occur in the current tab in focus* NewWindow : Means the new processing will open in a new tab If the report is used as part of an enhanced process flow then SameWindow is the best choice. If however you're using the CrossLinked report for data cleaning or as a research tool, then NewWindow keeps the parent record open for easier management. [[Category:Module Specific:Data Profiling]][[Category:Topic:Reporting‏‎]]