Difference between revisions of "Users Page Manual 3.0"

From Gvp-public
Jump to navigation Jump to search
 
(28 intermediate revisions by 3 users not shown)
Line 14: Line 14:
 
=== Users ===
 
=== Users ===
 
----
 
----
−
[[File:UsersForm.jpg|center|800px|Basic Information Users]]  
+
[[File:UsersForm.jpg|center|800px|User Basic Information]]  
  
 
<br />
 
<br />
Line 22: Line 22:
 
! style="width:40%;" | Restrictions
 
! style="width:40%;" | Restrictions
 
|-
 
|-
−
! style="text-align:left;;" | Name
+
! style="text-align:left;;border-left:5px solid yellow;" | Name
 
| Internal name. Not displayed in end user apps
 
| Internal name. Not displayed in end user apps
 
| Read Only
 
| Read Only
 
|-
 
|-
−
! style="text-align:left;" | Unique ID
+
! style="text-align:left;border-left:5px solid yellow;" | Unique ID
 
| Unique identifier, that uniquely identifies each user in the OSS/BSS.
 
| Unique identifier, that uniquely identifies each user in the OSS/BSS.
 
| Read Only
 
| Read Only
 
|-
 
|-
−
! style="text-align:left;" | E-mail
+
! style="text-align:left;border-left:5px solid yellow;" | E-mail
 
| User email, that will be used for login and email notification purposes
 
| User email, that will be used for login and email notification purposes
 
| Read Only
 
| Read Only
 
|-
 
|-
−
! style="text-align:left;" | Status
+
! style="text-align:left;border-left:5px solid yellow;" | Status
 
| Can be:
 
| Can be:
 
* '''Awaiting Email Confirmation''': Waiting confirmation E-mail from the user.
 
* '''Awaiting Email Confirmation''': Waiting confirmation E-mail from the user.
Line 43: Line 43:
 
| Read Only for Telefonica users.
 
| Read Only for Telefonica users.
 
|-
 
|-
−
! style="text-align:left;" | Source
+
! style="text-align:left;border-left:5px solid yellow;" | Source
 
| Controls the access and visibility of this subscription for other operators. Only operators with rights over this source or its children will be able to see it.
 
| Controls the access and visibility of this subscription for other operators. Only operators with rights over this source or its children will be able to see it.
 
| Read Only
 
| Read Only
 
|-
 
|-
−
! style="text-align:left;" | Instance
+
! style="text-align:left;border-left:5px solid yellow;" | Instance
 
| Instance where the user belongs to.
 
| Instance where the user belongs to.
−
| -
+
| Read Only
 +
|-
 +
! style="text-align:left;border-left:5px solid yellow;" | Since With GAL Connector
 +
| Flag that indicates if the new user has synchronized with GAL correctly.
 +
| Read Only
 
|-
 
|-
−
! style="text-align:left;" | Platform ID
+
! style="text-align:left;border-left:5px solid yellow;" | Platform ID
 
| Identifier of the OSS/BSS platform that manages this user
 
| Identifier of the OSS/BSS platform that manages this user
−
| -
+
| Read Only
 
|-
 
|-
−
! style="text-align:left;" | Type
+
! style="text-align:left;border-left:5px solid yellow;" | Type
 
| Values can be:  
 
| Values can be:  
 
* '''Telefonica''': means that the user is managed by an OB OSS/BSS. You cannot modify some fields for this user type.
 
* '''Telefonica''': means that the user is managed by an OB OSS/BSS. You cannot modify some fields for this user type.
 
* '''Non-Telefonica''': means that the user has been created directly in the platform and is not managed by any external OSS/BSS.
 
* '''Non-Telefonica''': means that the user has been created directly in the platform and is not managed by any external OSS/BSS.
−
| Some modifications are blocked for Telefonica users:
+
| Read Only <br> Some modifications are blocked for Telefonica users:
 
* Status
 
* Status
 
* Type
 
* Type
 
* …
 
* …
 +
|-
 +
! style="text-align:left;border-left:5px solid yellow;" | ServiceId Type
 +
| A registration user made by OB can be IPTV or OTT but registration users made on the portal will be always OTT.
 +
| ReadOnly
 
|-
 
|-
 
! style="text-align:left;" | E-wallet
 
! style="text-align:left;" | E-wallet
Line 74: Line 82:
 
| -
 
| -
 
|-
 
|-
−
! style="text-align:left;" | Default Credit Limit
+
! style="text-align:left;border-left:5px solid yellow;" | Default Credit Limit
 
| It is calculated with the minimum limit of user subscriptions and is used when the credit limit needs to be reset. It is -1 when user has not any limited subscription
 
| It is calculated with the minimum limit of user subscriptions and is used when the credit limit needs to be reset. It is -1 when user has not any limited subscription
 
| Read Only
 
| Read Only
 
|-
 
|-
−
! style="text-align:left;" | Credit Card Availability
+
! style="text-align:left;border-left:5px solid yellow;" | Credit Card Availability
 
| This field has meaning only for Non-Telefonica users in instances with SIA payment method.<br />
 
| This field has meaning only for Non-Telefonica users in instances with SIA payment method.<br />
 
It indicates if user has ever registered a valid credit card and then user's registration process can be seen as finished. It is stored at GVP_USERS.CREDIT_CARD_STATUS. Possible values are:
 
It indicates if user has ever registered a valid credit card and then user's registration process can be seen as finished. It is stored at GVP_USERS.CREDIT_CARD_STATUS. Possible values are:
Line 84: Line 92:
 
* '''1''': Pending. It will be ""1: pending"", after a NO TEF user self-registers to an instance with SIA_ENABLED = true.It means that this user needs to register a valid credit card in SIA system and he has not done it yet. In that case, after a loginUser or an attempt to createPurchase, PC client will always redirect user to registration credit card page.
 
* '''1''': Pending. It will be ""1: pending"", after a NO TEF user self-registers to an instance with SIA_ENABLED = true.It means that this user needs to register a valid credit card in SIA system and he has not done it yet. In that case, after a loginUser or an attempt to createPurchase, PC client will always redirect user to registration credit card page.
 
* '''2''': Active. Meaning that this user has registered a valid credit card in SIA.
 
* '''2''': Active. Meaning that this user has registered a valid credit card in SIA.
−
|  
+
| Read Only
 
|-
 
|-
−
! style="text-align:left;" | First Name
+
! style="text-align:left;border-left:5px solid yellow;" | First Name
 
| First name of the user. Managed by the user itself, in the registration fields in web portal
 
| First name of the user. Managed by the user itself, in the registration fields in web portal
−
| -
+
| Read Only
 
|-
 
|-
−
! style="text-align:left;" | Last Name
+
! style="text-align:left;border-left:5px solid yellow;" | Last Name
 
| Last name of the user. Managed by the user itself, in the registration fields in web portal
 
| Last name of the user. Managed by the user itself, in the registration fields in web portal
−
| -
+
| Read Only
 
|-
 
|-
 
! style="text-align:left;" | Birth Date
 
! style="text-align:left;" | Birth Date
Line 102: Line 110:
 
| -
 
| -
 
|-
 
|-
−
! style="text-align:left;" | Confirmation Code
+
! style="text-align:left;border-left:5px solid yellow;" | Confirmation Code
 
| Confirmation code sent by the platform during the registration process.
 
| Confirmation code sent by the platform during the registration process.
−
| -
+
| Read Only
 
|-
 
|-
−
! style="text-align:left;" | Geoblock White List
+
! style="text-align:left;border-left:5px solid yellow;" | Geoblock White List
 
| It allows to whilelist the user, so Geo Blocking is not applied when accessing from outside the country the instances is configured to be available in
 
| It allows to whilelist the user, so Geo Blocking is not applied when accessing from outside the country the instances is configured to be available in
 
| Read Only
 
| Read Only
 
|-
 
|-
−
! style="text-align:left;" | Owner
+
! style="text-align:left;border-left:5px solid yellow;" | Owner
 
| Operator that created this channel
 
| Operator that created this channel
 
| Read Only
 
| Read Only
Line 116: Line 124:
 
! style="text-align:left;" | Is Test User
 
! style="text-align:left;" | Is Test User
 
| Flag that indicates if the user is a test user.
 
| Flag that indicates if the user is a test user.
 +
| -
 +
|-
 +
! style="text-align:left;" | BI Test User
 +
| Flag that indicates if the user is a BI test user.
 
| -
 
| -
 
|-
 
|-
Line 126: Line 138:
 
| -
 
| -
 
|-
 
|-
−
 
+
! style="text-align:left;border-left:5px solid yellow;" | Suspension Date
 +
| Date on which the user has been suspended for the last time.
 +
| ReadOnly
 +
|-
 
|}
 
|}
  
 +
<br />
 +
=== Nagra User Data ===
 +
----
 +
[[File:NagraUserDataBlock.png|1200px|left]]
 +
<br>
 +
<br>
 +
<br>
 +
<br>
  
−
<br />
+
'''In this block there are two buttons:'''
 +
* '''GET INFO'''  This button will launch a request to CAS-API and trigger a pop-up with the response, with a readable formatting, for the operator to check.
 +
** Success Example: [[File:NagraDatauserGet.png|middle|70px]]
 +
* '''CONSOLIDATE'''  This button will launch a POST request to CAS-API to consolidate the data, and show a confirmation message, or any error message if that's the case, in a pop-up:
 +
** Success Example: [[File:NagraUserDataConsolidate.png|middle|70px]]
 +
<br>
 +
* In case of failure an error message will be displayed: [[File:NagraError.png|middle|70px]]
  
 
=== User PINS ===
 
=== User PINS ===
Line 157: Line 186:
 
# To save changes, press the [[File:Save3.png|middle|30px]] in the user page.<br />
 
# To save changes, press the [[File:Save3.png|middle|30px]] in the user page.<br />
 
<br />
 
<br />
−
'''Delete PIN'''
 
−
# Use the [[File:Delete2_3.png|middle|40px]] button to remove a PIN entry
 
−
# To save changes, press the [[File:Save3.png|middle|30px]] in the user page.<br />
 
−
<br /><br />
 
  
 
=== User Rights  ===
 
=== User Rights  ===
Line 175: Line 200:
 
* '''Date End:''' Date until the user has rights. In case of Subscriptions where recurrence is controlled by GVP (SIA, eWallet), this is the date for the next billing period.
 
* '''Date End:''' Date until the user has rights. In case of Subscriptions where recurrence is controlled by GVP (SIA, eWallet), this is the date for the next billing period.
 
* '''Purchase Status:''' Status of the purchase, value can be:
 
* '''Purchase Status:''' Status of the purchase, value can be:
−
** Active: the purchase is active and the user has active user rights.
+
** '''Active:''' the purchase is active and the user has active user rights.
−
** Error: An error occurred during the purchase process.  
+
** '''Error:''' An error occurred during the purchase process.  
−
** Finished: The purchased period is end, of a nonrecurring purchase.
+
** '''Finished:''' The purchased period is end, of a nonrecurring purchase.
−
** Trial: The user has made a purchase of product with a trial period configured. After the period, the purchase is changed to active and is billed.
+
** '''Trial:''' The user has made a purchase of product with a trial period configured. After the period, the purchase is changed to active and is billed.
−
** Canceled: the purchase has been cancelled.  
+
** '''Canceled:''' the purchase has been cancelled.  
−
** Cancelling: the purchase has been canceled, but the user still have rights in the purchased period.
+
** '''Cancelling:''' the purchase has been canceled, but the user still have rights in the purchased period.
−
** PendingOBActivation: The purchase is pending to be confirmed towards the BSS.  
+
** '''PendingOBActivation:''' The purchase is pending to be confirmed towards the BSS.  
−
** PendingOBCancellation: The purchase cancellation is pending to be confirmed towards the BSS.
+
** '''PendingOBCancellation:''' The purchase cancellation is pending to be confirmed towards the BSS.
−
** Pending: For non-billing purchases, the purchase is pending to be notified to the payment gateway.  
+
** '''Pending:''' For non-billing purchases, the purchase is pending to be notified to the payment gateway.  
 
* '''Payment Type:''' Type of payment:
 
* '''Payment Type:''' Type of payment:
−
** Billing
+
** '''Billing'''
−
** eWallet
+
** '''eWallet'''
−
** WebPay
+
** '''WebPay'''
−
** SIA
+
** '''SIA'''
 
* '''AutoRenew:''' Indicates if this is a recurrent user right (Subscription based)
 
* '''AutoRenew:''' Indicates if this is a recurrent user right (Subscription based)
 
* '''Price:''' The price of the purchase related to this user right.
 
* '''Price:''' The price of the purchase related to this user right.
Line 215: Line 240:
 
# To save changes, press the [[File:Save3.png|middle|30px]] in the user page.<br />
 
# To save changes, press the [[File:Save3.png|middle|30px]] in the user page.<br />
 
<br /><br />
 
<br /><br />
 +
 +
=== Nagra User Rights Data ===
 +
----
 +
[[File: NagraUserRightsDataBlock.png|1200px|left]]
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
 +
In this block there are two buttons:
 +
* '''GET INFO'''  This button will launch a request to CAS-API and trigger a pop-up with the response, with a readable formatting, for the operator to check.
 +
** Success Example:[[File:NagraUserRightsDataGet.png|middle|70px]]
 +
* '''CONSOLIDATE'''  This button will launch a POST request to CAS-API to consolidate the data, and show a confirmation message, or any error message if that's the case, in a pop-up:
 +
** Success Example:[[File:NagraUserDataConsolidate.png|middle|70px]]
 +
<br>
 +
* In case of failure an error message will be displayed
 +
** [[File:NagraError.png|middle|70px]]
  
 
=== User History ===
 
=== User History ===
Line 221: Line 263:
 
The fields are described below:
 
The fields are described below:
 
* '''Product Id''' - The product ID.
 
* '''Product Id''' - The product ID.
−
* '''Product Type''' - The type of product
+
* '''Product Type''' - The type of product.
 +
* '''Purchase ID''' - Id of the relative purchase.
 
* '''Name''' - The product name.
 
* '''Name''' - The product name.
 
* '''Date Start''' - Date when the rights were given.
 
* '''Date Start''' - Date when the rights were given.
 
* '''Date End''' - Date when the rights will be removed.
 
* '''Date End''' - Date when the rights will be removed.
−
* Status field - Same status as in User Rights
+
* '''Status field''' - Same status as in User Rights.
−
* Payment Type - Same as in User Rights
+
* '''Payment Type''' - Same as in User Rights.
−
* Transaction - ID of the transaction, each transaction in GVP has a unique ID transaction.
+
* '''Transaction''' - ID of the transaction, each transaction in GVP has a unique ID transaction.
−
* Price - Price of the product bought.
+
* '''Price''' - Price of the product bought.
−
* Quality - The max quality that the product was purchased with.
+
* '''Quality''' - The max quality that the product was purchased with.
−
* PricingModel - ID of the pricing model used on this purchase.
+
* '''PricingModel''' - ID of the pricing model used on this purchase.
 
<br />
 
<br />
 
[[File:UserHistory3.png|thumb|Subscription Event Collections block|center|800px]]
 
[[File:UserHistory3.png|thumb|Subscription Event Collections block|center|800px]]
Line 236: Line 279:
 
<br />
 
<br />
  
−
=== User History ===
+
=== Playback History ===
 
----
 
----
 
This block shows exactly the time (based on the heartbeats) a user has been playing a media, for both, VOD Contents and Live Contents. So when a user is watching a movie or a program, for example, it will record the time of the movie on this block based on each heartbeat.  
 
This block shows exactly the time (based on the heartbeats) a user has been playing a media, for both, VOD Contents and Live Contents. So when a user is watching a movie or a program, for example, it will record the time of the movie on this block based on each heartbeat.  
  
 +
<br />
 +
<br />
 +
 +
=== Current Playback Sessions ===
 +
----
 +
This block display all info of the session, and there is a Action Button, KICK, to request kick session.
 
<br />
 
<br />
 
<br />
 
<br />
Line 255: Line 304:
 
* '''Status:''' Indicates if the device is enabled or disabled. A disabled device will request the user to login to continue using that device
 
* '''Status:''' Indicates if the device is enabled or disabled. A disabled device will request the user to login to continue using that device
 
* '''Notification Token:''' The token used to register for receiving notifications
 
* '''Notification Token:''' The token used to register for receiving notifications
−
* '''Token status:''' The status of the notification token,
+
* '''Token status:''' The status of the notification token
 +
<br />
 
[[File:UserDevices3.png|thumb|User devices block|center|800px]]<br />
 
[[File:UserDevices3.png|thumb|User devices block|center|800px]]<br />
 
You can perform several actions in this block:<br /><br />
 
You can perform several actions in this block:<br /><br />
Line 272: Line 322:
 
<br />
 
<br />
  
−
=== User Video Service Info ===
+
=== Nagra Devices Data ===
 +
----
 +
[[File: NagraDevicesDataBlock.png|1200px|left]]
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
 
 +
In this block there are two buttons:
 +
* '''GET INFO'''  This button will launch a request to CAS-API and trigger a pop-up with the response, with a readable formatting, for the operator to check.
 +
** Success Example:[[File:NagraDevicesDataGet.png|middle|70px]]
 +
* '''CONSOLIDATE'''  This button will launch a POST request to CAS-API to consolidate the data, and show a confirmation message, or any error message if that's the case, in a pop-up:
 +
** Success Example:[[File:NagraUserDataConsolidate.png|middle|70px]]
 +
<br>
 +
* In case of failure an error message will be displayed
 +
** [[File:NagraError.png|middle|70px]]
 +
 
 +
=== Commands ===
 +
----
 +
This block allows the operator to see the list of individual commands previously sent to Open Platform STBs currently linked to user.
 +
And Send a command to 1 or more devices using the Block Commands Palette.
 +
 
 +
* '''Command Selector:''' type of command selected
 +
* '''Force Datahub Report:''' Indicates whether the stb sends the response immediately or in batches.
 +
* '''Start Date:''' Start Date
 +
* '''End Date:''' End Date
 +
<br />
 +
 
 +
[[File:CommandsUserBlock.jpg|thumb|Commands block|center|800px]]
 +
 
 +
<br />
 +
<br />
 +
 
 +
=== Commands Massive History ===
 
----
 
----
−
This block allows you to review extended information about the video service and settings. Some of this information is related only for IPTV users (Mediaroom) but the rest is used for any user type.
+
This block shows the list of massive commands previously sent for that user's devices
−
* '''Unique ID:''' User OSS/BSS Unique ID (Alias)
 
−
* '''Geographic Area:''' Geographic Area code, used for [[Channel Maps Page Manual 3.0|Channel Maps]] definition.
 
−
* '''Blackout Area:''' Blackout area, used for [[Blackouts Page Manual 3.0|Blackout]] region definition.
 
−
* '''Time Zone:''' User Timezone defined by the OSS/BSS
 
−
* '''SD Media Streams :''' Number of SD streams available
 
−
* '''HD Media Streams:''' Number of HD streams available
 
−
* '''Service Group:''' (Mediaroom) Indicates the service group assigned.
 
−
* '''Server Code List:''' (Mediaroom) Indicates the server code list.
 
−
* '''TimeShift Status Id''' (Mediaroom) Indicates the status of Mediaroom
 
−
* '''TimeShift Status Date:''' Flag that indicate (Mediaroom) Indicates the last date when the status was updated.
 
−
[[File:UserVideoServiceInfo3.png|thumb|User Video Service Info block|center|800px]]
 
 
<br />
 
<br />
−
This block doesn't allow any modifications.
+
 
 +
[[File:CommandMassiveHistoryBlock.jpg|thumb|Commands Massive History block|center|800px]]
 +
 
 
<br />
 
<br />
 
<br />
 
<br />
Line 311: Line 385:
 
<br />
 
<br />
 
<br />
 
<br />
 +
 +
 +
=== User Video Service Info ===
 +
----
 +
This block allows you to review extended information about the video service and settings. Some of this information is related only for IPTV users (Mediaroom) but the rest is used for any user type.
 +
* '''Unique ID:''' User OSS/BSS Unique ID (Alias)
 +
* '''Geographic Area:''' Geographic Area code, used for [[Channel Maps Page Manual 3.0|Channel Maps]] definition.
 +
* '''Blackout Area:''' Blackout area, used for [[Blackouts Page Manual 3.0|Blackout]] region definition.
 +
* '''Time Zone:''' User Timezone defined by the OSS/BSS
 +
* '''SD Media Streams :''' Number of SD streams available
 +
* '''HD Media Streams:''' Number of HD streams available
 +
* '''Service Group:''' (Mediaroom) Indicates the service group assigned.
 +
* '''Server Code List:''' (Mediaroom) Indicates the server code list.
 +
* '''TimeShift Status Id''' (Mediaroom) Indicates the status of Mediaroom
 +
* '''TimeShift Status Date:''' Flag that indicate (Mediaroom) Indicates the last date when the status was updated.
 +
[[File:UserVideoServiceInfo3.png|thumb|User Video Service Info block|center|800px]]
 +
<br />
 +
This block doesn't allow any modifications.
 +
<br />
 +
<br />
 +
  
 
=== User Interests ===
 
=== User Interests ===
Line 335: Line 430:
 
<br />
 
<br />
  
−
=== User SIA Cards ===
+
=== User SIA Cards (DEPRECATED)===
 
----
 
----
 
This block shows all credit cards linked to this user.
 
This block shows all credit cards linked to this user.
Line 359: Line 454:
 
<br />
 
<br />
 
<br />
 
<br />
 +
  
 
=== User Services ===
 
=== User Services ===
 
----
 
----
 
This block shows information about the [[Services_Page_Manual_3.0|Services]] associated to the user. The different services are associated to the users through the subscriptions the user has access to.
 
This block shows information about the [[Services_Page_Manual_3.0|Services]] associated to the user. The different services are associated to the users through the subscriptions the user has access to.
−
* '''ID''': Service ID
+
* '''Service ID''': Service ID
 
* '''Service Name''': Name of the Service.
 
* '''Service Name''': Name of the Service.
−
* '''Requires Agreement''': Shows if that specific services is set to require user agreement.
+
* '''Required''': Pending.
−
* '''Service Accepted''': Shows if the user has accepted the agreement text.
+
* '''Requires User Agreement''': Shows if that specific services is set to require user agreement.
−
* '''User Has Access''': Shows if the user has access to this service through his current subscriptions.  
+
* '''Has Access''': Shows if the user has access to this service through his current subscriptions.  
 +
* '''Has Accepted Agreement''': Shows if the user has accepted the agreement text.
 
[[File:UserServices.png|thumb|Subscription Relationships block|center|800px]]<br />
 
[[File:UserServices.png|thumb|Subscription Relationships block|center|800px]]<br />
 
<br />
 
<br />
Line 398: Line 495:
 
----
 
----
 
This block shows the user tags. For example: what content has the user reproduced, what content has completely visualized, what content has rated, what you have marked as favorite...
 
This block shows the user tags. For example: what content has the user reproduced, what content has completely visualized, what content has rated, what you have marked as favorite...
−
[[File:UserTagsBlock.png|thumb|User Tags block|center|800px]]<br />
+
[[File:UserTagsBlock.jpg|thumb|User Tags block|center|800px]]<br />
 
<br />
 
<br />
 
<br />
 
<br />
Line 406: Line 503:
 
This block shows the custom fields. These are fields created by the OB for user registration. They are fields that use obs, in addition to the basic fields
 
This block shows the custom fields. These are fields created by the OB for user registration. They are fields that use obs, in addition to the basic fields
 
[[File:UserCustomFieldsBlock.png|thumb|Custom Fields block|center|800px]]<br />
 
[[File:UserCustomFieldsBlock.png|thumb|Custom Fields block|center|800px]]<br />
 +
<br />
 +
<br />
 +
 +
=== User Activities ===
 +
----
 +
This block displays the user pin and password change logs.
 +
[[File:UserActivitiesBlock.jpg|thumb|User Activities block|center|800px]]<br />
 
<br />
 
<br />
 
<br />
 
<br />

Latest revision as of 19:34, 14 May 2024


Infobox info icon white.svg.png

Access to this menu in Betools through: UsersIcon.png Users



This section lists all the users that exist in the service and allows you to perform CRM actions.
You can use this menu to review users information and modify some user related information. The list of actions available might vary between the type of user (Telefonica, Non-Telefonica).


Blocks

Users

User Basic Information


Field Description Restrictions
Name Internal name. Not displayed in end user apps Read Only
Unique ID Unique identifier, that uniquely identifies each user in the OSS/BSS. Read Only
E-mail User email, that will be used for login and email notification purposes Read Only
Status Can be:
  • Awaiting Email Confirmation: Waiting confirmation E-mail from the user.
  • Active: User is active.
  • Suspended: User suspended.
  • Excluded: User excluded.
  • Unknown: User with some invalid data.
 Read Only for Telefonica users.
Source Controls the access and visibility of this subscription for other operators. Only operators with rights over this source or its children will be able to see it. Read Only
Instance Instance where the user belongs to. Read Only
Since With GAL Connector Flag that indicates if the new user has synchronized with GAL correctly. Read Only
Platform ID Identifier of the OSS/BSS platform that manages this user Read Only
Type Values can be:
  • Telefonica: means that the user is managed by an OB OSS/BSS. You cannot modify some fields for this user type.
  • Non-Telefonica: means that the user has been created directly in the platform and is not managed by any external OSS/BSS.
 Read Only
Some modifications are blocked for Telefonica users:
  • Status
  • Type
  • …
ServiceId Type A registration user made by OB can be IPTV or OTT but registration users made on the portal will be always OTT. ReadOnly
E-wallet Amount of e-wallet balance. The currency used will be the one defined at Instance level -
Current Credit Limit Remaining amount of money that can be spent in rentals during the ongoing month:
  • 0 means user cannot purchase contents.
  • -1 means user has no limit to purchase contents.
 -
Default Credit Limit It is calculated with the minimum limit of user subscriptions and is used when the credit limit needs to be reset. It is -1 when user has not any limited subscription Read Only
Credit Card Availability This field has meaning only for Non-Telefonica users in instances with SIA payment method.

It indicates if user has ever registered a valid credit card and then user's registration process can be seen as finished. It is stored at GVP_USERS.CREDIT_CARD_STATUS. Possible values are:

  • 0: n/a. Meaning that this field does not apply to this user. Possible reasons: instance parameter SIA_ENABLED = false (this instance is not connected to SIA payment gateway), TEF user, ... By default, it will be ""0: n/a"" for every GVP user.
  • 1: Pending. It will be ""1: pending"", after a NO TEF user self-registers to an instance with SIA_ENABLED = true.It means that this user needs to register a valid credit card in SIA system and he has not done it yet. In that case, after a loginUser or an attempt to createPurchase, PC client will always redirect user to registration credit card page.
  • 2: Active. Meaning that this user has registered a valid credit card in SIA.
 Read Only
First Name First name of the user. Managed by the user itself, in the registration fields in web portal Read Only
Last Name Last name of the user. Managed by the user itself, in the registration fields in web portal Read Only
Birth Date User birthday. Managed by the user itself, in the registration fields in web portal -
First Access Indicates if the user performed the first login or not. -
Confirmation Code Confirmation code sent by the platform during the registration process. Read Only
Geoblock White List It allows to whilelist the user, so Geo Blocking is not applied when accessing from outside the country the instances is configured to be available in Read Only
Owner Operator that created this channel Read Only
Is Test User Flag that indicates if the user is a test user. -
BI Test User Flag that indicates if the user is a BI test user. -
Telefonica User ID Identifier of the associated telefonica user. -
CPVR Hours Amount of hours for recordings the end user can schedule. -
Suspension Date Date on which the user has been suspended for the last time. ReadOnly


Nagra User Data

NagraUserDataBlock.png





In this block there are two buttons:

  • GET INFO This button will launch a request to CAS-API and trigger a pop-up with the response, with a readable formatting, for the operator to check.
    • Success Example: NagraDatauserGet.png
  • CONSOLIDATE This button will launch a POST request to CAS-API to consolidate the data, and show a confirmation message, or any error message if that's the case, in a pop-up:
    • Success Example: NagraUserDataConsolidate.png


  • In case of failure an error message will be displayed: NagraError.png

User PINS

In this block you can manage User PIN codes. Those codes are created when user self registers though UNIAPI or user is enabled if provisioned though GAL BSS.
There are three PIN types:

  • Adult Control: used for Adult contents
  • Parental Control: used for Parental level verification.
  • Purchase Control: used for Purchase verification.

Each PIN has a PIN value which allows to see the value that the user has configured and Enabled flag, that allows to enable/disable the PIN

User PINs management block


Add New PIN

  1. Use the AddNew.png button and new PIN row will be created.
  2. Fill in the PIN number and the enabled flag and the PIN Type
  3. To save changes, press the Save3.png in the user page.


Modify a PIN
You can modify any PIN number and enable/disable each of the PINs. To save changes, press the Save3.png in the user page.

Reset PIN

  1. Use the Reset 3.png button to set the PIN to 0000 and the enabled flag to false (disabled).
  2. To save changes, press the Save3.png in the user page.


User Rights

User Rights block shows the list of products the user has rights for and that are active. This block shows different information related to the user rights:

  • Purchase ID: Internal ID of the purchase
  • Product ID: ID of the product
  • Product Type: The types of product, that can be:
    • TVOD rentals (Movie, Serie, Season, Episode)
    • PPV purchases (PPV)
    • Subscriptions (Subscription)
  • Date Start: Date from the user has rights
  • Date End: Date until the user has rights. In case of Subscriptions where recurrence is controlled by GVP (SIA, eWallet), this is the date for the next billing period.
  • Purchase Status: Status of the purchase, value can be:
    • Active: the purchase is active and the user has active user rights.
    • Error: An error occurred during the purchase process.
    • Finished: The purchased period is end, of a nonrecurring purchase.
    • Trial: The user has made a purchase of product with a trial period configured. After the period, the purchase is changed to active and is billed.
    • Canceled: the purchase has been cancelled.
    • Cancelling: the purchase has been canceled, but the user still have rights in the purchased period.
    • PendingOBActivation: The purchase is pending to be confirmed towards the BSS.
    • PendingOBCancellation: The purchase cancellation is pending to be confirmed towards the BSS.
    • Pending: For non-billing purchases, the purchase is pending to be notified to the payment gateway.
  • Payment Type: Type of payment:
    • Billing
    • eWallet
    • WebPay
    • SIA
  • AutoRenew: Indicates if this is a recurrent user right (Subscription based)
  • Price: The price of the purchase related to this user right.


User rights block


Extend Rental Period On this block it’s possible to extend or to expire the rights of a user for a specific product.

  1. First change the End Date to the desired new date.
  2.  To save changes, press the Save3.png in the user page.


Cancel right You can also cancel a user right, which will make the user right to move to Cancelling status. It applies only to Subscription products (recurrent) because the user will still have access to the content until the end date is reached. After the end date, the user right will be Cancelled.

  1. Use the Cancel 3.png button to cancel the user right.
  2. A confirmation popup will be shown asking for confirmation.
  3. To save changes, press the Save3.png in the user page.


Disable right You can also Disable the user right, which means that the content purchased will be cancelled immediately and the user will not have access to the content anymore. The purchase status will be changed to Expired and it will be moved to User History block.

  1. Use the Disable 3.png button to remove a PIN entry.
  2. A confirmation popup will be shown asking for confirmation.
  3. To save changes, press the Save3.png in the user page.



Nagra User Rights Data

NagraUserRightsDataBlock.png





In this block there are two buttons:

  • GET INFO This button will launch a request to CAS-API and trigger a pop-up with the response, with a readable formatting, for the operator to check.
    • Success Example:NagraUserRightsDataGet.png
  • CONSOLIDATE This button will launch a POST request to CAS-API to consolidate the data, and show a confirmation message, or any error message if that's the case, in a pop-up:
    • Success Example:NagraUserDataConsolidate.png


  • In case of failure an error message will be displayed
    • NagraError.png

User History

This block shows the different purchases made by the user over time, displaying the product type, name status and its price. The fields are described below:

  • Product Id - The product ID.
  • Product Type - The type of product.
  • Purchase ID - Id of the relative purchase.
  • Name - The product name.
  • Date Start - Date when the rights were given.
  • Date End - Date when the rights will be removed.
  • Status field - Same status as in User Rights.
  • Payment Type - Same as in User Rights.
  • Transaction - ID of the transaction, each transaction in GVP has a unique ID transaction.
  • Price - Price of the product bought.
  • Quality - The max quality that the product was purchased with.
  • PricingModel - ID of the pricing model used on this purchase.


Subscription Event Collections block



Playback History

This block shows exactly the time (based on the heartbeats) a user has been playing a media, for both, VOD Contents and Live Contents. So when a user is watching a movie or a program, for example, it will record the time of the movie on this block based on each heartbeat.



Current Playback Sessions

This block display all info of the session, and there is a Action Button, KICK, to request kick session.

User Devices

This block allows you to review all the devices the user has linked with his account. The information available about the device is:

  • Creation Date: Date when the device was first registered in the platform.
  • Last Update: Date when the device has been updated
  • Name: Device name
  • Friendly Name: Device friendly name assigned by the user
  • Device ID: Unique Device ID used to register the device in the platform
  • MAC: Mac address of the device
  • Master: Flag that indicates if the device is a Master device (Mediaroom only)
  • Status: Indicates if the device is enabled or disabled. A disabled device will request the user to login to continue using that device
  • Notification Token: The token used to register for receiving notifications
  • Token status: The status of the notification token


User devices block


You can perform several actions in this block:

Review all the info for a device
Use the Info 3.png button and you will be taken to the User devices page so you can review extended information about an specific device.

Disable or enable a device

  1. Use the Enable 3.png button to enable a device, allowing the user to use it without having to login.
  2. You can also disable the device using the Disable 3.png button. A disabled device will request the user to login to be able to continue using it.
  3. The device status flag will be modified depending on the status.
  4. To save changes, press the Save3.png in the user page. The device will be enabled or disabled.


Delete a device

  1. Use the Delete2 3.png button to remove a device
  2. To save changes, press the Save3.png in the user page. The device will be deleted


Nagra Devices Data

NagraDevicesDataBlock.png





In this block there are two buttons:

  • GET INFO This button will launch a request to CAS-API and trigger a pop-up with the response, with a readable formatting, for the operator to check.
    • Success Example:NagraDevicesDataGet.png
  • CONSOLIDATE This button will launch a POST request to CAS-API to consolidate the data, and show a confirmation message, or any error message if that's the case, in a pop-up:
    • Success Example:NagraUserDataConsolidate.png


  • In case of failure an error message will be displayed
    • NagraError.png

Commands

This block allows the operator to see the list of individual commands previously sent to Open Platform STBs currently linked to user. And Send a command to 1 or more devices using the Block Commands Palette.

  • Command Selector: type of command selected
  • Force Datahub Report: Indicates whether the stb sends the response immediately or in batches.
  • Start Date: Start Date
  • End Date: End Date


Commands block



Commands Massive History

This block shows the list of massive commands previously sent for that user's devices

Commands Massive History block



Email Communication

This block allows to review all the emails that have been sent to a specific user as well as resending some of those emails. You can also us the Sent Mail page to review extended information.
Click on the LOAD MESSAGES button so the different emails are loaded.

Email communications block

Preview email sent
By clicking in the Preview.png button in each email, you can access to its contents and review the information that has been sent to the user.

Send a new email (Remember password / Welcome)
By clicking in the SEND REMEMBER PASSWORD EMAIL button, you can send a new remember password email to the user. This option is only available for users in Active status
By clicking in the SEND WELCOME EMAIL button, you can send a new welcome email to the user. This option is only available for users in Awaiting Email Confirmation status

Re-sending an email sent
You can re-send any email that has been sent to the user.

  1. Click on the 30px to re-send an email
  2. A confirmation popup will ask you for confirmation. If you accept it, the email will be sent again to the user.




User Video Service Info

This block allows you to review extended information about the video service and settings. Some of this information is related only for IPTV users (Mediaroom) but the rest is used for any user type.

  • Unique ID: User OSS/BSS Unique ID (Alias)
  • Geographic Area: Geographic Area code, used for Channel Maps definition.
  • Blackout Area: Blackout area, used for Blackout region definition.
  • Time Zone: User Timezone defined by the OSS/BSS
  • SD Media Streams : Number of SD streams available
  • HD Media Streams: Number of HD streams available
  • Service Group: (Mediaroom) Indicates the service group assigned.
  • Server Code List: (Mediaroom) Indicates the server code list.
  • TimeShift Status Id (Mediaroom) Indicates the status of Mediaroom
  • TimeShift Status Date: Flag that indicate (Mediaroom) Indicates the last date when the status was updated.
User Video Service Info block


This block doesn't allow any modifications.


User Interests

This block allows you to review and manage the User interests. The interests can be used to send notifications to users segmented by interests.

User Interests block


Add existing Interests

  • Click the AddExisting.png button and a dialog will open to select an existing Interest.
  • Once finished, save changes by using the Save3.png in the User page and the interest will be removed from that user.


Remove Interests

  • Use the DeleteRed3.png button to remove the association of an Interest .
  • Once finished, save changes by using the Save3.png in the User page. This will not delete the interest from the platform. In order to delete the Interest, you will have to go to the Notification Interests Page.


CRM History

In this block it is possible to see all the events related to an user CRM history and status changes are displayed, so it is possible review what CRM actions have been performed to the user. The block displays the different events generated by a the specific user. The events are ordered by creation date (last event first) the last 20 events and will allow to navigate to older events.

CRM history block


No other action is allowed in this block.

User SIA Cards (DEPRECATED)

This block shows all credit cards linked to this user.

SIA Cards block

Each credit card will be described by the following fields:

  • ID: Index in database (GVP_USERS_SIA_CARDS table)
  • Creation date: Creation date for this register
  • Name: Alias configured by user to identify registered credit card (e.g. Visa personal)
  • Owner: MiB user that generated this register
  • Token: Token generated by SIA. It connects a user with his registered credit card.
  • Pan: Masked credit card number (e.g. 2098 **** **** **** 6789)
  • Status: The status of the token (credit card) may be:
    • 0: Unknown
    • 1: Active. When a token is active means this token is used for every purchase and recurring payment. In GVP4.0, every user can have one and only one active token.
    • 2: To be canceled. When a user is excluded in GVP, GVP must remove from SIA his credit card info.
    • 3: Canceling. Whereas agent is processing the cleaning process in SIA after a user is excluded.
    • 4: Canceled. When SIA has removed the token because it has expired or replaced by a new token.
  • Micropayment: ID in GVP_SIA_MICROPAYMENTS of the micropayment used to validate this credit card.
  • User: User Id




User Services

This block shows information about the Services associated to the user. The different services are associated to the users through the subscriptions the user has access to.

  • Service ID: Service ID
  • Service Name: Name of the Service.
  • Required: Pending.
  • Requires User Agreement: Shows if that specific services is set to require user agreement.
  • Has Access: Shows if the user has access to this service through his current subscriptions.
  • Has Accepted Agreement: Shows if the user has accepted the agreement text.
Subscription Relationships block




Groups

This block shows Groups the user belongs to. This block allows adding a user to an existing group

  • ID: Group ID
  • Name: Name of the Group.
  • Priority: Shows the priority of the group.
  • Settings Partition: Shows the partition parameters that affect this group.
Groups block




User Preferences

This block shows the different preferences that have been configured by the users. The different preferences depend on the different applications, but some examples are:

  • LastLanguage
  • CatchupServiceActive
  • StartOverServiceActive
  • AdultFirstAccess
User Preferences block




User Tags

This block shows the user tags. For example: what content has the user reproduced, what content has completely visualized, what content has rated, what you have marked as favorite...

User Tags block




User Custom Fields

This block shows the custom fields. These are fields created by the OB for user registration. They are fields that use obs, in addition to the basic fields

Custom Fields block




User Activities

This block displays the user pin and password change logs.

User Activities block




Actions

Create Edit Edit in List Bulk Edit Copy Copy with Relateds Delete
Cross.png
Tick.png
Cross.png
Cross.png
Cross.png
Cross.png
Cross.png

New3.png Create

User creation from users page is not allowed. Users can only be created in the platform through two ways:

  • OSS/BSS provisioning: Telefonica (billing payment) users are created through OSS/BSS provisioning. Those users will be completely managed from the OB OSS/BSS and the set of actions that can be performed in MIB 3.0 Users page is limited.
  • User self registration: Non-Telefonica (no billing payment) users can perform self-registration in the different portals. Only available in Instances where self-registration is configured.

In this case the user will be Non-Telefonica and will be completely managed inside the platform.

BulkEdit3.png Edit

User modifications are enabled for some operator profiles (CRM, OB Admin). It can be used to perform modifications in some of the user related data. As it has been already explained before, the user data that can be modified depends on the user type:

  • Telefonica users:
  • Non-Telefonica users:


Edit3.png Edit in List

Edit in list is disabled for Users for security reasons. You have to go to Edit Page to perform any modification.


BulkEdit3.png Bulk Edit

Bulk Edit is disabled in the Users page for security reasons. Only single modification is allowed in the Edit Page.

Copy3.png Copy

Copy is disabled for users as user creation from MIB is not allowed.

CopyWithRelateds3.png Copy with Relateds

Copy with Relateds is disabled for users


Delete3.png Delete

User deletion is not allowed. To disable users, set them to Status = Excluded. They should remain excluded at least for 6 months. If you want to remove some users that have been excluded since more than 6 months, use the Users Cleaner tool.



Retrieved from "https://wikis.tid.es/gvp-public/index.php?title=Users_Page_Manual_3.0&oldid=4339"