APIs Enhancement<\/p>\n
APIs Enhancement Order Number Complaint number<\/p>\n
Introduction
\nPurpose
\nThis document defines the changes to be implemented for Oneview along with the data that is required for performing these tests.<\/p>\n
Business Objective
\nBusiness requested enhancements on OLO ONT line status parameters to provide better service assurance to OLO customers.<\/p>\n
Description
\nThe OLO ONT status (current and historical data of ONT) will be fetched from the OLO provider and will be shown in Oneview for the agents to better troubleshoot the customer issues.<\/p>\n
Solution Overview
\nAgent has to initiate the API request by triggering the function from Oneview. Oneview will fetch the OLO ONT status and other parameters from BSST EAI, APIM and the parameters will be shown in Oneview.<\/p>\n
Below is the high-level solution summary for the reference from the SDD.<\/p>\n
Assumptions and Constraints
\nAssumptions
\n\u00b7 The reader of this document should be familiar with:<\/p>\n
Oneview (NOKIA\/Motive SMP 18.1.9)<\/p>\n
\u00b7 ODS, BSST EAI, APIM are highly available systems for Oneview application.<\/p>\n
\u00b7 The change will impact EBU services. CBU business will align with EBU business, so that the delivery of CBU and EBU (CR-50899) for this interface enhancement will be synchronized, else the changes for CBU will not be moved to production.<\/p>\n
Scope
\n1. Scope of this feature is for CBU LL services.<\/p>\n
2. Applicable to FTTH line types.<\/p>\n
3. Scope is limited to Open Access seeker lines, all OLO providers. (Mobily, Salam, Dawiyat)<\/p>\n
4. Scope includes both Oneview and MiniOV.<\/p>\n
Functional Requirements
\n#<\/p>\n
User Story<\/p>\n
Requirement<\/p>\n
IT Impact<\/p>\n
Compliance<\/p>\n
HLD Mapping<\/p>\n
Functional Requirements<\/p>\n
FR-1<\/p>\n
UST-9837<\/p>\n
Mobily is not passing all parameters of line status to STC.<\/p>\n
Mobily Line Status Question Assignment API should be enhanced to include below values:<\/p>\n
1. ONT signal RX&TX<\/p>\n
2. ONT status – Up\/down\/Switched off (dying gasp)<\/p>\n
3. ONT Latency<\/p>\n
4. ONT Speed<\/p>\n
5. Current Link Quality<\/p>\n
6. MAC status and details for both HAG\/ONT.<\/p>\n
7. Historical data ONT, CPE, and OLO for 7 days<\/p>\n
STC Phone Number<\/p>\n
OneView<\/p>\n
PC<\/p>\n
1. Following are not provided by Mobily in the response.<\/p>\n
a. Latency<\/p>\n
b. Speed<\/p>\n
c. MAC<\/p>\n
Historical data of ONT will be presented.<\/p>\n
6.1.1<\/p>\n
6.1.2<\/p>\n
6.1.3<\/p>\n
FR-2<\/p>\n
UST-10141<\/p>\n
SALAM Line Status Question Assignment API should be enhanced to include below values:<\/p>\n
\u00b7 RX\/TX ONT\/OLT level.<\/p>\n
Device status \u2026 up\/down\/ switched off<\/p>\n
OneView<\/p>\n
PC<\/p>\n
Rx\/Tx as provided by Salam (ONT\/OLT) will be presented to the user.<\/p>\n
6.1.1<\/p>\n
6.1.2<\/p>\n
6.1.3<\/p>\n
Open Items
\nID<\/p>\n
Open Item<\/p>\n
Comments<\/p>\n
Status<\/p>\n
O-1<\/p>\n
Dawiyat OLO Provider<\/p>\n
As Dawiyat provider is not providing with the additional new parameters, the additional new fields will still be shown in Oneview UI with the values as blank.<\/p>\n
Open<\/p>\n
O-2<\/p>\n
Parameters not fetched<\/p>\n
In case BSST EAI response status is SUCCESS but some of the parameters or values are missing in the response, then the relevant fields in Oneview UI will be shown as blank.<\/p>\n
Open<\/p>\n
O-3<\/p>\n
Arabic Locale Texts<\/p>\n
Business will provide the Arabic locales\/texts for the screen items, so that it can be displayed for the Arabic language selection.<\/p>\n
Open<\/p>\n
O-4<\/p>\n
WSDL and Request\/Response XMLs<\/p>\n
BSST EAI team will provide the WSDL for the interface INT0402 and Request\/Response XML during their development.<\/p>\n
Open<\/p>\n
Technical Solution Details
\nSolution Details
\n\u00b7 The current implementation of fetching OLO line parameters in Oneview, which happens on the initialization of the session will be stopped. Comment by Author: Is it applicable only for OLO? Or STC as well? Comment by Author: It is applicable only for OLO, STC as seeker.<\/p>\n
\u00b7 Agent has to initiate a request to fetch the OLO line status parameters by clicking a link. Comment by Author: Is it a link or button\/label? Comment by Author: It is a link, decorated as a tree->leaf. please refer to the mock screens in section 6.1.2.6<\/p>\n
\u00b7 The Network Analyzer summary widget, which is currently populated during the initialization will show a message \u201cNetwork Analyzer is not applicable for Open Acess seeker lines\u201d.<\/p>\n
\u00b7 New link will be provided under advanced diagnostics section for invoking the OLO line status parameters manually by the Agent.<\/p>\n
\u00b7 Mini Oneview screen needs to be modified to stop fetching the OLO line parameters on startup.<\/p>\n
\u00b7 New link to be provided under the Tools->Internet Tools section for fetching the OLO line status parameters manually by the Agent.<\/p>\n
\u00b7 The below list of parameters to be fetched from BSST EAI->APIM->OLO and shown in Oneview.<\/p>\n
\u00b7 ONT Status<\/p>\n
\u00b7 ONT current link Quality<\/p>\n
\u00b7 ONT Signal Rx<\/p>\n
\u00b7 ONT Signal Tx<\/p>\n
\u00b7 OLT Signal Rx<\/p>\n
\u00b7 OLT Signal Tx<\/p>\n
\u00b7 ONT latency<\/p>\n
\u00b7 ONT Speed<\/p>\n
Oneview Changes
\nWorkflow
\n\u00b7 A new interactive workflow (STC_OLO_ONT_FETCH_LINE_STATUS) will be created.<\/p>\n
\u00b7 The workflow will perform the following operations<\/p>\n
\u00b7 Fetch the below details from the dictionary.<\/p>\n
\u00b7 Service identifier<\/p>\n
\u00b7 Operator Name<\/p>\n
These parameters are being fetched from ODS view (ONVIEW_CUSTOMER_PROFILE) using customer service number as part of Oneview session initialization.<\/p>\n
\u00b7 Invoke the BSST EAI interface INT0402 using Java Service Operation to fetch the OLO line status parameters.<\/p>\n
\u00b7 Display the parameters in a tabular format.<\/p>\n
Service Operation Module
\n\u00b7 A new Service Operation module will be created which will do the invocation of fetchLineStatus operation to the BSST EAI interface INT0402.<\/p>\n
Service Operation Name<\/p>\n
JSO Module Display Name<\/p>\n
JSO Operation Name<\/p>\n
STCOloOntFetchLineStatus<\/p>\n
STCOloOntFetchDetails<\/p>\n
fetchLineStatus<\/p>\n
Java Service Operation
\n\u00b7 A new Java Service Operation will be created, which will perform the below operations<\/p>\n
\u00b7 It will fetch the input parameters from workflow and invoke the BSST EAI interface INT0402.<\/p>\n
\u00b7 Process the response from the BSST EAI interface and pass it back to the workflow.<\/p>\n
Service Operation Inputs
\nName<\/p>\n
Type<\/p>\n
Description<\/p>\n
Backend Mapping<\/p>\n
serviceIdentifier<\/p>\n
String<\/p>\n
Service Identifier of the OLO customer<\/p>\n
OLO_OPERATOR_ID from ONVIEW_CUSTOMER_PROFILE view in ODS<\/p>\n
operatorName<\/p>\n
String<\/p>\n
Name of the OLO operator<\/p>\n
OLO_OPERATOR_NAME from ONVIEW_CUSTOMER_PROFILE view in ODS<\/p>\n
Service Operation Outputs
\nName<\/p>\n
Type<\/p>\n
Description<\/p>\n
result<\/p>\n
String<\/p>\n
Result of the service operation<\/p>\n
resolution<\/p>\n
List<\/p>\n
Resolution of the service operation<\/p>\n
error<\/p>\n
List of Map<\/p>\n
List of errors each member of the list is a Map with: (String errorCode, String errorMessage)<\/p>\n
properties<\/p>\n
Map<\/p>\n
Map of properties to contain the detailed OLO ONT Status Question Assignment results.<\/p>\n
OLO ONT Line Status Results
\nName<\/p>\n
Type<\/p>\n
Description<\/p>\n
BSST EAI (INT 0402) Mapping<\/p>\n
ontStatus<\/p>\n
String<\/p>\n
ONT Status from OLO Provider<\/p>\n
equipmentPort\/equipmentPortStatusCode<\/p>\n
ontCurrentLinkQuality<\/p>\n
String<\/p>\n
ONT Link Quality from the OLO Provider<\/p>\n
equipmentPort\/ equipmentPortLinkQuality<\/p>\n
ontSignalRx<\/p>\n
String<\/p>\n
ONT Signal Rx value from the OLO Provider<\/p>\n
Name-equipmentPort\/equipmentPortCharacteristics\/ equipmentPortCharacteristicsName\/ONTSignalRx<\/p>\n
Value- equipmentPort\/equipmentPortCharacteristics\/ equipmentPortCharacteristicsValue<\/p>\n
ontSignalTx<\/p>\n
String<\/p>\n
ONT Signal Tx value from the OLO Provider<\/p>\n
Name-equipmentPort\/equipmentPortCharacteristics\/ equipmentPortCharacteristicsName\/ONTSignalTx<\/p>\n
Value- equipmentPort\/equipmentPortCharacteristics\/ equipmentPortCharacteristicsValue<\/p>\n
oltSignalRx<\/p>\n
String<\/p>\n
OLT Signal Rx value from the OLO Provider<\/p>\n
Name-equipmentPort\/equipmentPortCharacteristics\/ equipmentPortCharacteristicsName\/OLTSignalRx<\/p>\n
Value- equipmentPort\/equipmentPortCharacteristics\/ equipmentPortCharacteristicsValue<\/p>\n
oltSignalTx<\/p>\n
String<\/p>\n
OLT Signal Tx value from the OLO Provider<\/p>\n
Name-equipmentPort\/equipmentPortCharacteristics\/ equipmentPortCharacteristicsName\/OLTSignalTx<\/p>\n
Value- equipmentPort\/equipmentPortCharacteristics\/ equipmentPortCharacteristicsValue<\/p>\n
ontLatency<\/p>\n
String<\/p>\n
ONT Latency value from the OLO Provider<\/p>\n
equipmentPort \/equipmentPortLatency<\/p>\n
ontSpeed<\/p>\n
String<\/p>\n
ONT Speed value from the OLO Provider<\/p>\n
equipmentPort\/ equipmentPortExpectedBandwidth<\/p>\n
equipmentPort\/ equipmentPortExpectedBandwidthCode<\/p>\n
ontSignalRxHistory<\/p>\n
List of Map<\/p>\n
Each Map should have time, ONTSignalRxValue<\/p>\n
Historical ONT Signal Rx Data<\/p>\n
Type-equipmentPort\/technicalParameters\/ technicalParameterType\/ONTSignalRx<\/p>\n
Name- equipmentPort\/technicalParameters\/ technicalParameterName\/<\/p>\n
Value-<\/p>\n
equipmentPort\/technicalParameters\/ technicalParameterValue\/<\/p>\n
Timestamp-<\/p>\n
equipmentPort\/technicalParameters\/timestamp\/<\/p>\n
ontSignalTxHistory<\/p>\n
List of Map<\/p>\n
Each Map should have time, ONTSignalTxValue<\/p>\n
Historical ONT Signal Tx Data<\/p>\n
Type-equipmentPort\/technicalParameters\/ technicalParameterType\/ONTSignalTx<\/p>\n
Name- equipmentPort\/technicalParameters\/ technicalParameterName\/<\/p>\n
Value-<\/p>\n
equipmentPort\/technicalParameters\/ technicalParameterValue\/<\/p>\n
Timestamp-<\/p>\n
equipmentPort\/technicalParameters\/timestamp\/<\/p>\n
status<\/p>\n
String<\/p>\n
SUCCESS\/ERROR<\/p>\n
result\/status<\/p>\n
errorSourceSystem<\/p>\n
String<\/p>\n
Source system where the error occurred.<\/p>\n
result\/error\/ errorSourceSystem<\/p>\n
sourceErrorCode<\/p>\n
String<\/p>\n
Error code from the source system.<\/p>\n
result\/error\/ sourceErrorCode<\/p>\n
errorCode<\/p>\n
String<\/p>\n
Error code mapped in ESB<\/p>\n
result\/error\/errorCode<\/p>\n
errorType<\/p>\n
String<\/p>\n
Type of the error<\/p>\n
result\/error\/errorType<\/p>\n
errorDescription<\/p>\n
String<\/p>\n
Detailed description of the error message.<\/p>\n
result\/error\/errorDescription<\/p>\n
errorDescriptionArabic<\/p>\n
String<\/p>\n
Description of the error message in Arabic.<\/p>\n
result\/error\/errorDescriptionArabic<\/p>\n
Initialization Modules
\n\u00b7 Remove the OLOQuestion AssignmentlineStatus invocation from the startup\/initialization modules.<\/p>\n
\u00b7 Shared Function \u2013 callEAIforOLOQuestion AssignmentlineStatus.<\/p>\n
Oneview Customer Profile
\n\u00b7 The Network Analyzer summary widget will show a message \u201cNetwork Analyzer not applicable for Open Acess seeker lines\u201d.<\/p>\n
Advanced Diagnostics
\n\u00b7 A new section will be created in Advanced Diagnostics tab \u201cOLO Tools\u201d.<\/p>\n
\u00b7 The new workflow created will be nested under the section \u201cOLO Tools\u201d as \u201cOLO ONT Line Status Enquiry\u201d.<\/p>\n
\u00b7 If the result is \u2018SUCCESS\u2019 and parameters fetched from the OLO Line Status Enquiry, those will be shown in a tabular format, along with a green status icon.<\/p>\n
\u00b7 In case result is \u2018ERROR\u2019, the error message will be shown with a red icon along with the details of the error which will be shown in tabular format.<\/p>\n
\u00b7 The ONT Signal Rx History and ONT Signal Tx History will be will be shown in separate tables.<\/p>\n
\u00b7 Wherever the data is not available from the backend call, the value will be shown as blank. Comment by Author: Is it possible to hide the field instead? Comment by Author: It is not possible to hide the field, hence it is suggested to show blank, this is the current behaviour as well.<\/p>\n
\u00b7 The arabic localization will be done, as applicable.<\/p>\n
\u00b7 Indicative mockup screen for Oneview customer profile section and advanced diagnostics section for the result table with ONT line status parameters are as below.<\/p>\n
\u00b7 SUCCESS Screen:<\/p>\n
\u00b7 ERROR Screen:<\/p>\n
MiniOv Changes
\n360 Degree View:
\n\u00b7 The OLO information section which is being loaded during the startup\/initialization will be removed. Comment by Author: Please confirm if this is applicable for OLO customers only. For stc, existing process would continue as is. Comment by Author: Applicable for OLO customer, STC as seeker. For stc customers at present there is no \u201cOLO information\u201d section and hence there will be no changes<\/p>\n
\u00b7 The workflow will be modified to remove the startup invocation of Question Assignment OLO line status in the startup\/initialization.<\/p>\n
\u00b7 Please see the below existing screen, which will be updated, to remove the \u201cOLO Information\u201d section.<\/p>\n
Tools
\n\u00b7 The workflow for fetching line status (STC_OLO_FETCH_LINE_STATUS) will be linked under Internet Tools in the Tools section.<\/p>\n
\u00b7 The workflow with fetch the OLO ONT line status parameters and display in the Mini Oneview screen in a tabular format.<\/p>\n
\u00b7 The FTTH NAF related workflows will be hidden for the OLO customer numbers.<\/p>\n
\u00b7 Please refer to the below mockup screen for the link Tools -> Internet Tools.<\/p>\n
BSST EAI Interface (INT0402)
\nThe BSST EAI Interface (INT0402) will be enhanced by the BSST EAI team to pass on additional parameters from APIM\/OLO.<\/p>\n
Below are the sample request and response parameters for the API. For more details, please refer the BSST EAI HLD and Interface Mapping document in Appendix-1.<\/p>\n
Request – getEquipmentPortExpectedBandwidth
\nheader<\/p>\n
Sample values<\/p>\n
messageVersion<\/p>\n
1.0<\/p>\n
systemID<\/p>\n
One View<\/p>\n
messageID<\/p>\n
1-A7KNC<\/p>\n
correlationID<\/p>\n
1-123456789<\/p>\n
timestamp<\/p>\n
Current time (“yyyy-MM-dd’T’HH:mm:ss”)<\/p>\n
operationType<\/p>\n
Inquiry<\/p>\n
processName<\/p>\n
GetModemBandwidth<\/p>\n
userID<\/p>\n
OV<\/p>\n
interfaceID<\/p>\n
INT0402<\/p>\n
systemIP<\/p>\n
System IP from Environment Property<\/p>\n
customerType<\/p>\n
crmSourceSystem from ODS \u2013 B2C\/B2B<\/p>\n
body<\/p>\n
operator\/operatorName<\/p>\n
OLO_OPERATOR_NAME from ODS view (Dawiyat, Salam, Mobily)<\/p>\n
service\/serviceIdentifier<\/p>\n
OLO_OPERATOR_ID from ODS view<\/p>\n
Response – getEquipmentPortExpectedBandwidth
\nbody<\/p>\n
Sample values<\/p>\n
equipmentPort<\/p>\n
equipmentPortExpectedBandwidth<\/p>\n
4094.0<\/p>\n
equipmentPortExpectedBandwidthUnitCode<\/p>\n
kb\/s<\/p>\n
equipmentPortStatusCode<\/p>\n
CONNECTED Up\/Down Comment by Author: It will be Up\/Down Comment by Author: Updated.<\/p>\n
equipmentPortLatency<\/p>\n
1<\/p>\n
equipmentPortLinkQuality<\/p>\n
Good\/ Bad<\/p>\n
equipmentPortCharacteristics<\/p>\n
equipmentPortCharacteristicName<\/p>\n
ONTSignalRx<\/p>\n
equipmentPortCharacteristicValue<\/p>\n
-21<\/p>\n
equipmentPortCharacteristics<\/p>\n
equipmentPortCharacteristicName<\/p>\n
ONTSignalTx<\/p>\n
equipmentPortCharacteristicValue<\/p>\n
2<\/p>\n
equipmentPortCharacteristics<\/p>\n
equipmentPortCharacteristicName<\/p>\n
OLTSignalRx<\/p>\n
equipmentPortCharacteristicValue<\/p>\n
-5<\/p>\n
equipmentPortCharacteristics<\/p>\n
equipmentPortCharacteristicName<\/p>\n
OLTSignalTx<\/p>\n
equipmentPortCharacteristicValue<\/p>\n
3<\/p>\n
technicalParameters<\/p>\n
technicalParameterType<\/p>\n
ONTSignalRx<\/p>\n
technicalParameterName<\/p>\n
ontRx1\/ontRx2\/\u2026<\/p>\n
technicalParameterValue<\/p>\n
-13\/-12\/\u2026<\/p>\n
timestamp<\/p>\n
1587027629\/1587029999\/\u2026<\/p>\n
technicalParameters<\/p>\n
technicalParameterType<\/p>\n
ONTSignalTx<\/p>\n
technicalParameterName<\/p>\n
ontTx1\/ontTx2\/\u2026<\/p>\n
technicalParameterValue<\/p>\n
2\/3\/\u2026<\/p>\n
timestamp<\/p>\n
1587027629\/1587029999\/\u2026<\/p>\n
result<\/p>\n
status<\/p>\n
SUCCESS\/ERROR<\/p>\n
error<\/p>\n
errorSourceSystem<\/p>\n
Source System of the Error<\/p>\n
sourceErrorCode<\/p>\n
Error Code of the source system<\/p>\n
errorCode<\/p>\n
APP.FN.ERROR<\/p>\n
errorType<\/p>\n
TECHNICAL<\/p>\n
errorDescription<\/p>\n
No data found<\/p>\n
errorDescriptionArabic<\/p>\n
NA<\/p>\n
Endpoint Details
\nEnvironment<\/p>\n
URL<\/p>\n
Production<\/p>\n
http:\/\/oneview-bsstprod.stc.com.sa:20900\/ws\/STC_RMOSupportAndReadiness.wsProviders.v_1_1:ResourceDiscoveryManagement\/STC_RMOSupportAndReadiness_wsProviders_v_1_1_ResourceDiscoveryManagement_Port<\/p>\n
SIT<\/p>\n
http:\/\/172.20.204.98:20900\/ws\/STC_RMOSupportAndReadiness.wsProviders.v_1_1:ResourceDiscoveryManagement\/STC_RMOSupportAndReadiness_wsProviders_v_1_1_ResourceDiscoveryManagement_Port<\/p>\n
I18N Locales
\nBelow are the text\/labels for the Oneview UI. The Arabic equivalent texts will be provided by the business.<\/p>\n
Display Text – English<\/p>\n
Display Text – Arabic<\/p>\n
OLO Tools<\/p>\n
OLO ONT Line Status Enquiry<\/p>\n
Display of OLO ONT Line Status<\/p>\n
ONT Line Status Enquiry Results<\/p>\n
ONT Status<\/p>\n
Current Link Quality<\/p>\n
ONT Signal RX<\/p>\n
ONT Signal TX<\/p>\n
OLT Signal RX<\/p>\n
OLT Signal TX<\/p>\n
ONT Latency<\/p>\n
ONT Speed<\/p>\n
ONT Signal RX History<\/p>\n
ONT Signal TX History<\/p>\n
Parameter<\/p>\n
Value<\/p>\n
Time<\/p>\n
Date<\/p>\n
Successfully retrieved the data<\/p>\n
There was an error retrieving the data<\/p>\n
Error Source System<\/p>\n
Source Error Code<\/p>\n
Error Code<\/p>\n
Error Type<\/p>\n
Error Description English<\/p>\n
Error Description Arabic<\/p>\n
Network Analyzer not applicable for Open Access seeker lines<\/p>\n
Test Scenarios
\n#Sr<\/p>\n
Use Case<\/p>\n
Scenario<\/p>\n
Target<\/p>\n
Expected Result<\/p>\n
Status<\/p>\n
Remark<\/p>\n
1<\/p>\n
Network Analyzer Summary Widget<\/p>\n
Network Analyzer Summary Widget for OLO Customers.<\/p>\n
OV<\/p>\n
For OLO customers when the number is searched in Oneview, the Network Analyzer summary widget should display message \u201cNetwork Analyzer is not applicable for Open Acess seeker lines\u201d<\/p>\n
2<\/p>\n
Network Analyzer Summary Widget<\/p>\n
Network Analyzer Summary widget for STC Customers.<\/p>\n
OV<\/p>\n
For STC customers when the number is searched in Oneview, the Network Analyzer summary widget should display the details fetched from Network Analyzer backend.<\/p>\n
3<\/p>\n
Advanced Diagnostics<\/p>\n
New link in Advanced Diagnostics for OLO Customers.<\/p>\n
OV<\/p>\n
For the OLO customers there should be a new link in the Advanced Diagnostics section in Oneview \u201cOLO Tools\u201d-> \u201cOLO Line Status Enquiry\u201d.<\/p>\n
4<\/p>\n
Advanced Diagnostics<\/p>\n
No OLO Tools link for the STC Customers.<\/p>\n
OV<\/p>\n
For the STC customers there should not be any link \u201cOLO Tools\u201d-> \u201cOLO Line Status Enquiry\u201d in the Advanced Diagnostics section.<\/p>\n
5<\/p>\n
Advanced Diagnostics<\/p>\n
Fetch and display OLO line information for OLO customers.<\/p>\n
OV<\/p>\n
For OLO customers, when the agent clicks on link \u201cOLO Tools\u201d-> \u201cOLO Line Status Enquiry\u201d in the Advanced Diagnostics section, Oneview should fetch the information from BSST EAI\/APIM\/OLO and display the information as applicable and available from the OLO systems.<\/p>\n
6<\/p>\n
MiniOneview 360 view<\/p>\n
OLO section should not appear in 360 view for OLO customers.<\/p>\n
OV<\/p>\n
For OLO customers there will be no OLO section shown in the 360 view when Mini Oneview screen is loaded.<\/p>\n
7<\/p>\n
MiniOneview Tools<\/p>\n
\u201cOLO Line Status Enquiry\u201d to be shown under \u201cInternet Tools\u201d for OLO customers.<\/p>\n
OV<\/p>\n
For OLO customers the link OLO Line Status Enquiry should appear under \u201cInternet Tools\u201d in the \u201cTools\u201d section when Mini Oneview screen is loaded for OLO customers.<\/p>\n
8<\/p>\n
NAF Utility Links<\/p>\n
NAF Utility links should be hidden for OLO customers.<\/p>\n
OV<\/p>\n
For OLO customers the utility tools links should not appear under \u201cInternet Tools\u201d in the \u201cTools\u201d section when Mini Oneview screen is loaded for OLO customers.<\/p>\n
STC IT SystemsOLO ProvidersCC\/BO AgentCC\/BO<\/p>\n","protected":false},"excerpt":{"rendered":"
APIs Enhancement APIs Enhancement Order Number Complaint number Introduction Purpose This document defines the changes to be implemented for Oneview along with the data that\u2026<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7643,7642,7645,7644],"tags":[7678,8989,8988,7387,633,8991,630,8987,8994,8467,15,8990,7656,7571,8993,66,8992],"class_list":["post-104193","post","type-post","status-publish","format-standard","hentry","category-custom-same-day-essays","category-custom-writings-writers","category-do-my-essay-mla-format","category-write-my-paper-hub-writers","tag-best-custom-paper-writing-service","tag-best-online-paper-writing-service","tag-best-paper-writing-service","tag-best-research-paper-writing-services","tag-cheap-research-paper-writing-service","tag-cheapest-paper-writing-service","tag-college-paper-writing-service","tag-free-paper-writing-service","tag-free-term-paper-writing-service","tag-paper-writing-service","tag-paper-writing-service-reddit","tag-professional-paper-writing-service","tag-someone-to-write-my-paper","tag-websites-that-write-papers-for-you","tag-what-is-the-best-paper-writing-service","tag-write-my-paper","tag-write-my-paper-for-me-free"],"_links":{"self":[{"href":"https:\/\/www.studyproessays.com\/help\/wp-json\/wp\/v2\/posts\/104193","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studyproessays.com\/help\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.studyproessays.com\/help\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.studyproessays.com\/help\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.studyproessays.com\/help\/wp-json\/wp\/v2\/comments?post=104193"}],"version-history":[{"count":0,"href":"https:\/\/www.studyproessays.com\/help\/wp-json\/wp\/v2\/posts\/104193\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.studyproessays.com\/help\/wp-json\/wp\/v2\/media?parent=104193"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.studyproessays.com\/help\/wp-json\/wp\/v2\/categories?post=104193"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.studyproessays.com\/help\/wp-json\/wp\/v2\/tags?post=104193"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}