Anonymous, bureaucrat, administrator
7,528
edits
Changes
From All n One's bxp software Wixi
no edit summary
N.B If you need to change the element name of “record”, this is done through: ''Main Menu > Form Management > Form - Primary Management > Form - Advanced Settings > Choose the form > Campaign CMI API XML and Excel AutoLoad Processing Options > XML Element''
=== Worklist Options ===
[[File:Dataprofiling_customised_007.png]]
Worklists and their usage are described in 2.3.6.6 of this document.
Alternate URL: When clicking a worklist button you will be taken into the record via the Inbound contact module. It is possible to redirect the click to another page altogether, with the Form Id and CDA Id parameters also being passed. This is useful when using eCourse pages for custom builds.
Open In: When the worklist button is clicked does the new URL open in the current window or is a new window / tab opened.
Include records with no CCL’s: By default Custom Groups build their reports on times. This requires there to be a CCL. When using a Custom Group as a worklist there are occasions where there are freshly loaded CDAs or CDAs brought in through the BEAPI from a public website which will not have a CCL. This option allows all CDAs regardless of time to be included in the worklist.
== Step 2 - Limit by Users ==
This screen allows the data output of the reports to be limited to CCLs involving specific individuals. This is how a team report would be configured. Simply select the people you wish to only report on.
It is not necessary to select any user from this list. Selecting no users will include all records in the reporting.
== Step 3 - Limit by Outcomes ==
This screen allows you to limit the report by the outcomes of relevance. You must select outcomes to have data in your report. Selecting no outcomes will result in no data in your report.
Custom Entry is provided to allow the report to include CDAs that do not yet have CCLs, or for outcomes not used at the time of the report creation.
An outcome must be used at least once for it to appear in the list of outcomes available.
Click “Select All” to save time selecting options.
== Step 4 - Fields and Sequence ==
This screen allows you to select which fields will appear in the report. Simply check the fields you want to include.
If the field names have “New” in a lot of them, then this means that the Field Mapping was not set up correctly early on in the process. You can change the field names by simply clicking the “Open Field Mapping” button. This opens a new window with the Field Mapping process and you can adjust the column names as required. Remember to go to the bottom and click “Update Mappings.” When done close the Field Mapping new window. Refresh the Fields and Sequence page and the new field names should appear.
When the data is output it is possible to sort by any of the CDA fields. This can save a lot of time sorting data when it is exported to Excel. The format is to use the field names separated by commas, e.g.
strCDA_X_field_0_1,strCDA_X_field_0_0
Tip: It is also possible to put ,DESC at the end of this list of fields and this will make the sort order Descending instead of the default Ascending (ASC)
When you save and go the next screen you can numerically order the fields in any order you like. This saves times having to reorder output in Excel later on. Simply number the fields in the order you need.
== Step 5 - Grouping Parameters ==
This is by far one of the most powerful features of bxp reporting available. This screen allows for very specific custom groups to be created.
[[File:Dataprofiling_customised_008.png]]
If not used, the report will include all the outcomes and if used the user limitations. These parameters are for limiting the data by information stored in the CDAs.
In order to clarify the use of this report we need some sample data.
{| class="wikitable"
! Id,
! Name,
! Colour,
! Location,
! Date of Contact
|-
| 1, || Philip Lacey, || Blue, || Dublin || April
|-
| 2, || Nick Wheeler, || Blue, || Dublin || April
|-
| 3, || Chris Thomson, || Red, || Dublin || April
|-
| 4, || Santa Clause, || Red, || North Pole || April
|-
| 5, || Tony Stark, || Red, || NewYork || April
|-
|}
{| class="wikitable"
! Field Field
! Mapped Name
|-
| intCDA_X_Id || Id
|-
| strCDA_X_field_0_0 || Name
|-
| strCDA_X_field_0_1 || Colour
|-
| strCDA_X_field_0_2 || Location
|-
| strCDA_X_field_0_3 || Date of Contact
|-
|}
=== Example 1: Just Dublin ===
* Field From the list of fields we choose Location.
* Match Exact Match
* Value Dublin
Result Returns 1,2,3
''The query reads''
Where strCDA_X_field_0_2 = ‘Dublin’
This will return any record where the Location field has Dublin in it.
=== Example 2: Dublin and New York ===
* Field From the list of fields we choose Location.
* Match Exact Match
* Value Dublin
* Limiting Or
* Field From the list of fields we choose Location.
* Match Exact Match
* Value New York
Result Returns 1,2,3,5
''The query reads''
Where strCDA_X_field_0_2 = ‘Dublin’ or strCDA_X_field_0_2 = ‘New York’
This will return any record where the Location field has Dublin in it.
