CrossLinked Reports - Revision history

Philip Lacey at 12:58, 31 January 2018

2018-01-31T12:58:56Z

Philip Lacey at 14:55, 6 September 2015

2015-09-06T14:55:28Z

Philip Lacey at 20:23, 9 November 2014

2014-11-09T20:23:17Z

Philip Lacey at 00:56, 26 October 2014

2014-10-26T00:56:27Z

Philip Lacey at 00:55, 26 October 2014

2014-10-26T00:55:30Z

Philip Lacey at 00:47, 26 October 2014

2014-10-26T00:47:12Z

Philip Lacey at 00:06, 26 October 2014

2014-10-26T00:06:11Z

Philip Lacey at 23:42, 25 October 2014

2014-10-25T23:42:50Z

Philip Lacey at 23:16, 25 October 2014

2014-10-25T23:16:13Z

Philip Lacey at 23:14, 25 October 2014

2014-10-25T23:14:25Z

@@ Line 71: / Line 71: @@
-[[File:CrossLinked_Demo001.png]]
+[[File:CrossLinked_Demo001.png|800px]]
@@ Line 80: / Line 80: @@
-[[File:CrossLinked_Demo002.png]]
+[[File:CrossLinked_Demo002.png|800px]]
@@ Line 105: / Line 105: @@
-[[File:CrossLinked_Demo003.png]]
+[[File:CrossLinked_Demo003.png|800px]]
@@ Line 141: / Line 141: @@
-[[File:CrossLinked_Demo004.png]]
+[[File:CrossLinked_Demo004.png|800px]]
@@ Line 153: / Line 153: @@
-[[File:CrossLinked_Demo005.png]]
+[[File:CrossLinked_Demo005.png|800px]]
 Cross Linked Options
@@ Line 202: / Line 202: @@
-[[File:CrossLinked_Demo006.png]]
+[[File:CrossLinked_Demo006.png|800px]]
@@ Line 222: / Line 222: @@
-[[File:CrossLinked_Demo007.png]]
+[[File:CrossLinked_Demo007.png|800px]]
@@ Line 236: / Line 236: @@
-[[File:CrossLinked_Demo009.png]]
+[[File:CrossLinked_Demo009.png|800px]]
@@ Line 250: / Line 250: @@
-[[File:CrossLinked_Demo008.png]]
+[[File:CrossLinked_Demo008.png|800px]]
@@ Line 266: / Line 266: @@
-[[File:CrossLinked_Demo010.png]]
+[[File:CrossLinked_Demo010.png|800px]]
@@ Line 272: / Line 272: @@
-[[File:CrossLinked_Demo011.png]]
+[[File:CrossLinked_Demo011.png|800px]]
@@ Line 278: / Line 278: @@
-[[File:CrossLinked_Demo012.png]]
+[[File:CrossLinked_Demo012.png|800px]]
@@ Line 288: / Line 288: @@
-[[File:CrossLinked_Demo013.png]]
+[[File:CrossLinked_Demo013.png|800px]]
@@ Line 294: / Line 294: @@
-[[File:CrossLinked_Demo014.png]]
+[[File:CrossLinked_Demo014.png|800px]]
-[[File:CrossLinked_Demo015.png]]
+[[File:CrossLinked_Demo015.png|800px]]
@@ Line 302: / Line 302: @@
-[[File:CrossLinked_Demo016.png]]
+[[File:CrossLinked_Demo016.png|800px]]
@@ Line 317: / Line 317: @@
-[[File:CrossLinked_Demo017.png]]
+[[File:CrossLinked_Demo017.png|800px]]
-[[File:CrossLinked_Demo018.png]]
+[[File:CrossLinked_Demo018.png|800px]]
@@ Line 333: / Line 333: @@
-[[File:CrossLinked_Demo019.png]]
+[[File:CrossLinked_Demo019.png|800px]]
@@ Line 339: / Line 339: @@
-[[File:CrossLinked_Demo020.png]]
+[[File:CrossLinked_Demo020.png|800px]]
@@ Line 345: / Line 345: @@
-[[File:CrossLinked_Demo021.png]]
+[[File:CrossLinked_Demo021.png|800px]]
@@ Line 351: / Line 351: @@
-[[File:CrossLinked_Demo022.png]]
+[[File:CrossLinked_Demo022.png|800px]]
@@ Line 360: / Line 360: @@
-[[File:CrossLinked_Demo023.png]]
+[[File:CrossLinked_Demo023.png|800px]]
@@ Line 366: / Line 366: @@
-[[File:CrossLinked_Demo024.png]]
+[[File:CrossLinked_Demo024.png|800px]]
@@ Line 389: / Line 389: @@
-[[File:CrossLinked_Demo025.png]]
+[[File:CrossLinked_Demo025.png|800px]]

← Older revision		Revision as of 14:55, 6 September 2015
Line 22:		Line 22:

	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"		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.
		+

← Older revision		Revision as of 20:23, 9 November 2014
Line 375:		Line 375:

	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.		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‏‎]]

@@ Line 367: / Line 367: @@
-SameWindow : Means that the new processing will occur in the current tab in focus
+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
 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.

← Older revision		Revision as of 00:55, 26 October 2014
Line 343:		Line 343:

	== Worked Example - Including eCourse Assets ==		== 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]]
		+
		+
		+
		+	== 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"
		+
		+
		+	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.

← Older revision		Revision as of 00:47, 26 October 2014
Line 282:		Line 282:


−	In our example we add "count#strCDA_616_field_1_2#child;" to the "Child Calculation Fields"	+	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.


Line 289:		Line 289:

	[[File:CrossLinked_Demo018.png]]		[[File:CrossLinked_Demo018.png]]
		+
		+
		+
		+	== 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]]
		+
		+
		+	Then we modify the parameters to let it know to go looking for a changing value
		+
		+
		+	[[File:CrossLinked_Demo020.png]]
		+
		+
		+	If we pull the report we don't get an answer we want
		+
		+
		+	[[File:CrossLinked_Demo021.png]]
		+
		+
		+	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]]
		+
		+
		+	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]]
		+
		+
		+	Now pulling the report we get:
		+
		+
		+	[[File:CrossLinked_Demo024.png]]
		+
		+
		+	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 ==

← Older revision		Revision as of 00:06, 26 October 2014
Line 271:		Line 271:

	[[File:CrossLinked_Demo016.png]]		[[File:CrossLinked_Demo016.png]]
		+
		+
		+	== 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"
		+
		+
		+	[[File:CrossLinked_Demo017.png]]
		+
		+
		+	[[File:CrossLinked_Demo018.png]]

← Older revision		Revision as of 23:42, 25 October 2014
Line 241:		Line 241:

	[[File:CrossLinked_Demo011.png]]		[[File:CrossLinked_Demo011.png]]
		+
		+
		+	In the Interaction Options we can also enable the "Show Child Headers" which adds the column headings for the children.
		+
		+
		+	[[File:CrossLinked_Demo012.png]]
		+
		+
		+
		+	== 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]]
		+
		+
		+	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]]
		+
		+	[[File:CrossLinked_Demo015.png]]
		+
		+
		+	No we go in and add two different contacts each.
		+
		+
		+	[[File:CrossLinked_Demo016.png]]

← Older revision		Revision as of 23:16, 25 October 2014
Line 235:		Line 235:

	[[File:CrossLinked_Demo010.png]]		[[File:CrossLinked_Demo010.png]]
		+
		+
		+	For completeness we turn on the AED buttons for the Children.
		+
		+
		+	[[File:CrossLinked_Demo011.png]]

@@ Line 94: / Line 94: @@
-== Worked Example - Creating the report ==
+== Worked Example - Creating the initial report ==
-A cross linked report is built as part of a customised group report.  In the same way that a rolling totals report is completely independent of the settings of a customised group report, the cross linked report requires a customised group report to be part of but the settings are completely independent.
+A cross linked report is built as part of a customised group report. The cross linked report requires a customised group report to be part of but the settings are completely independent of how the customised group reporting works.
@@ Line 106: / Line 106: @@
-The cross linked report MUST be set up on the parent form.  So Form 615 in our example.  We only need to fill out the first screen of the Customised Group setup.
+The cross linked report MUST be set up on the parent form.  So Form 615 in our example.  We only need to fill out the first screen of the Customised Group set up, for the moment.
@@ Line 123: / Line 123: @@
 [[File:CrossLinked_Demo005.png]]
 * Layout : Interactive.   See [[CrossLinked_Layouts]] for the different options available.
@@ Line 131: / Line 132: @@
 Child Parameters
 * Child Campaign : Choose the child form Blended - Demo - CrossLinked - Contacts
 * Link Field : This is the Basic - Campaign Listing field.  You use field mapping to find this information out.  in our example case it is strCDA_616_field_0_1
@@ Line 138: / Line 140: @@
 Interaction Options
 * Flow Control : SameWindow
 * eCourse Asset Ids : Allows eCourse assets to be drawn into the report.  Leave blank.
@@ Line 146: / Line 149: @@
 * Child Buttons : No
 * AED Buttons - Child : False