Professional Documents
Culture Documents
PRS TLCSM08 004 E RAID 8.0 MASHUPS Training Unit
PRS TLCSM08 004 E RAID 8.0 MASHUPS Training Unit
Mashup Introduction
1) What will we do?
2) Datamodel
Pay Attention
Listen to the narrator
Follow me
Replicate the described steps in your environment
Do it by yourself
Hands on
The main objective of this unit is to provide to the end-user the capabilities of
building a smart content with different components with interaction between
and has the capability to invoke other smart contents.
Some of the activities planned on this unit are:
Create a mashups, with distinct components:
Data lists
Sections with distinct type of graphics
Progress Indicators
Read only forms
Filters the information
Define distinct behaviours associated to an event.
By clicking either in a row or a columns
Change section
Invoke other Mashups
Manage the smart content layout
Set a mashup to open as default in a page
Define variables Mashup variables
Chart
Selector
To accomplish the activities planned on this course we will mainly use 2 entities:
RD SGSN Out Agg – contains aggregated data information about the SGSN
events.
RV T SGSN xDR Stream – contains the detail of the SGSN event calls.
The Entry View should have the default value that corresponds to the selected unit.
To use a Data List the user must add the “Data List” component to
the Mashup and configure it.
Two Data Lists should be added using different levels of
aggregation regarding the below fields
On Data List must be named as Aggregation Data
The Other Detailed Data
Aggregation Data “Data Lista” Detailed Data “Data Lista”
Start Date (SGSN Out Agg) Start Date (SGSN Out Agg)
Traffic Type (Traffic Type) Start Hour (SGSN Out Agg)
Call Type (Call Type) Traffic Type (Traffic Type)
Event Count (SGSN Out Agg) (Sum) Call Type (Call Type)
Event Duration (SGSN Out Agg) (Sum) Description (Subscriber Type)
Data Volume Gb (SGSN Out Agg) (Sum) Event Type (Event Type)
In the end the two data list should look like the below ones
For the “Data Volume Total” progress indicator, the Logical Field SGSN “Data Volume Gb”
should be sum aggregated.
Clicking twice on the indicator either in or select or preview area the format are available. It
is also available on double cogwheel in the right grey area.
Apply the follow formats
Type: Knob.
Label: Data Volume Total
Untougle Percentage
Format Mask : #,### 'GB'
Ranges: Defines the Maximum threshold interb
Minimum: 0
Maximum 24 522
Add New Range
Light Blue: 0-9200
Medium Blue: 9200-18000
Dark Blue: 18000-24522
For the “Subscriber Types Prepaid” process indicator, the user must select two
columns:
“Percentage of Prepaid Subscriber Type”
“Data Volume Gb” and set sum aggregation measure.
For the first column, the user must select the Icon format type with the user male icon
and enable the percentage option. The maximum range must be 100.
For the second, the user must apply the Text format type with a “GB” suffix. The user
must add a filter to the Subscriber Type Description which will select only names
terminated with "Prepaid”.
For the “Subscriber Types Prepaid” process indicator, the user must select two
columns:
“Percentage of Postpaid Subscriber Type”
“Data Volume Gb” and set sum aggregation measure.
For the first column, the user must select the Icon format type with the user male icon
and enable the percentage option. The maximum range must be 100
For the second, the user must apply the Text format type with a “GB” suffix.
The user must add a filter to the Subscriber Type Description which will select only
names terminated with "Postpaid”.
The Read Only Form is used to present data in a simple way and
complement the Data List 2 table ad apply the follow format
Name the form “Record Information”
Enable the multi column option.
After uplink Logical filed click on to change the columns position
On the Data List scope, Customized Events allows to define some specific events.
The More popular events are:
Line Click
Line Button
Column Click
For each defined event a behaviour must be associated
Behaviours will define which are the action associated to the event
One event can have zero or more than one behaviour (Named as Actions) and the usage is
defined by the order in the behaviour area
The way to interpret an event on behaviours is something like this
Whenever ShowDL2 (Event) is triggered, do in (Action Area) the following actions (Actions to be
executed)
On Data List 1 -> Customised Events, add a new event named “ShowDL2” this event
should have the “Line Click” activation mode.
On the Behaviour Tab add a new behaviour that will be triggered by the previously created
event.
Add new Actions to this behaviour:
ShowDL2 Data List (2) Filter Start Date Event = Start Date
(SGSN Out Agg) (SGSN Out Agg)
ShowDL2 Data List (2) Filter Call Type (Call Event = Call Type (Call
Type) Type)
ShowDL2 Data List (2) Filter Traffic Type Event = Traffic Type
(Traffic Type) (Traffic Type)
For each Progress Indicator for “Prepaid” and “Postpaid”, the user must add some behaviours to
filter and/or clear filters by Subscriber Type.
By clicking once on “Percentage of Prepaid Subscriber Type, Subscriber Type filter will be applied.
By double clicking on “Percentage of Prepaid Subscriber Type”, Subscriber Type filter will be cleared.
By clicking on Data List 2 row’s content, the dimensions must filter the Read Only Form.
Define Filters
For each of added field, edit it and set Input Control Type = Value List (Multiple)
This control type allows to use the list of values
In the end is expected to have and filterable area like the below picture
Before adding the Drill Down button, in Data List 2, the user needs to create a new “Smart
Content”.
Add a new “Data List” with the following data from “Sgsn Xdr Stream” entity:
After the “Customized Events” is configured, the user must add a new behaviour to the
Xdr Stream button.
Before adding a Section Container, the user needs to go to Options and add a Section.
This option allows you to create different displays within the same Smart Content.
The user must add 3 sections set to not visible in Navigation Bar: Traffic Type, Call Type and
Subscriber Type.
This behaviour allows to the sections be used in the component Section and not create sections on
the Mashup.
For each Section (except All), the user must create a different type of Chart by adding the
“Chart” component.
The user must configure a behaviour to Filter when clicking a specific “Traffic Type”. This
requires adding a new event to the tab “Customised Events” with the “Activation Mode”
selected on “X Axis Click” for the filter to be applied when any of X Axis point is clicked.
In the "Behaviours" tab, not only must the user have a behaviour to add filters in Global
but also another to switch section in the Section Container, allowing navigation to the "Call
Type" section.
Add a new event “CallTypeFilter” to the tab “Customised Events” with the
“Activation Mode” selected on “X Axis Click”;
Add new Action to this behaviour:
Whenever is triggered, do in the following action Filter field Using Operator Value
CallTypeFilter Global Add Filter Call Type (Call Type) Event = Call Type (Call Type)
On Advanced Configuration, set true for multiple charts and then configure one more chart for “Description”
instead of “Category”
For each Section the user must also add the “Action Bar” component
to the Smart Content.
The user can change the look of the buttons at “Look and Feel” and
must define a behaviour for the buttons that will allow to navigate to
the other sections by clicking on the respective names.
On Section “All”:
To design a Smart Content, the user can change the Layout and
select a template to apply. In this case, the selected Layout
Template is “Header-Left-Right-Side”.
The final design of the Composing Mashups Content should look like this:
HEADER
SIDE
LEFT RIGHT
To manage the layout, the user should click the “Manage Layout” button.
It’s possible to Hide and Show specific areas by adding Behaviours to do what the
user needs. The objective of the user is to be able to hide and show the components
at the right zone of the layout.
For this, the user needs to apply 25 in Right - width (%) area:
The Right zone should be shown when the user clicks on a Data List 2 row. For that, the
behaviours must be configured in the Data List 2.
Taking advantage of the previously created Record Information filter event, the user needs to
add an action to:
Manage the layout for:
“Header + (Left + Right)” zone with 80 Width (%), the Side with 20%, the Left zone with 75% and the Right
zone 25%.
Add an “Action Bar” at the top of the right zone to create a button that allows to hide the
Record Information
Add a behaviour with actions that allow to define that the zone has to be hidden and that
allow to manage the layout.