Jara NetBusiness Vedlikeholdsrelease , 11. februar 2008

Introduksjon Denne presentasjonen går igjennom endringer og nyheter i Jara NetBusiness, ny vedlikeholdsrelease 11. februar 2008.

3 Contents •Change: ―Order Line Item Cancellation ―Connection# included when SR is started from order ―More interface values for Capacity Products ―Handle status “Avvik (A)” from Marius ―New action must be displayed in Order Search ―Assets module ―New return channel solutions for telephony, broadband and error status ―Handle new Kapaks 4xx error codes ―Change from full to shared and shared to full access ―Change name of end user ―Product change from OA to Jara ADSL

4 Contents continued •Bugfix: ―Digital Aksess - Should not be possible to submit without Telelosjinummer ATP ―Duplicate s On Cancelled Orders ―Technical fixes in B2B ―Change order OA change of “telelosji” and “blokkposisjon” ―VAB change of “sperreprogram” goes to OMS but changes are not performed ―Change of user when customer id is outdated is rejected by OMS

5 Change: Order Line Item Cancellation - New functionality •“Cancel Line Item” button is moved back to the applet (originally it was planned to introduce it in Release K) •Orders can be cancelled even when they are submitted ―Applicable for OMS orders only ―Available for submitted orders on Line Item level ―Unavailable for orders in status Cancelled, Finished, Closed and Delivery (D) ―Existing Cancel functionality on Order header remains untouched •Response on order cancellation ―Cancellation status is displayed to user. ―New attribute “Cancellation Status” and “Cancellation Reason” ―“Cancellation Status” gives the status “Request sent” and “Request OK” ―Successful cancellation gives the Line Item status “Cancelled (A)” ―Unsuccessful cancellation gives the status “The Requested Operation Failed” in the attribute “Cancellation Status” ―Cancellation Reason field should get value “Cancelled by customer” •With unsuccessful cancellation contakt Jara Kundeservice

6 Change: Order Line Item Cancellation - New functionality continued

7 Change: Connection# included when SR is started from order •When Service Request is created from the Orders screen, the value in field Connection# on Order Line Item can be transferred to the field Connection # on the Service Request. •To transferred Connection# to the Service Request, you must search up the Order Line Item from the pick list in attribute “Order Line Item”

8 Change: More interface values for Capacity Products •New interface values are implemented for Capacity Products: ―Digital punkt til punkt (> 2 Mbps) ―Optisk Kanal Part #ProductEnhet HastighetHastighetGrensenitt Bruker 1Grensenitt Bruker 2 DIGITALDigital punkt til punkt (> 2 Mbps) Mbps34 G S1-75 S1-S-SC S1-S-FC S1-S-LC S4-S-SC S4-S-FC S4-S-LC 622 S4-S-FC S4-S-LC

9 Change: More interface values for Capacity Products continued Part #ProductEnhet HastighetHastighetGrensenitt Bruker 1Grensenitt Bruker 2 WDMOptisk KanalMbps2500 S16-S-SC S16-S-FC S16-S-LC 10GLS-FC 10GLS-LC 10GLS-SC 10GWS-FC 10GWS-LC 10GWS-SC S64-S-SC S64-S-FC S64-S-LC 10GLS-FC 10GLS-LC 10GLS-SC 10GWS-FC 10GWS-LC 10GWS-SC

10 Change: Handle status Avvik (A) from Marius •Marius is introducing a new process-id/status in addition to existing, with the value Avvik (A) that is to be sent on return channel to Jara NetBusiness. •The status Avvik (A) will occur when of type Avvik (A) is sent from Marius directly to customer. •Marius return channel will send a new process-id/status Avvik (A) to JNB for all “Marius products”.

11 Change: New action displayed in Order Search •In Release K a lot of order actions (Flytt, Flytting bruker 1, Flytting bruker 2, Produktbytte..) have been replaced with line item flags •Fields like Move User 1, Move User 2, Move User Change, Product Change are displayed and searchable in Orders Search under Orders.

12 Change: Assets module •Assets module has been updated •You can use this module to see connection and telephone number registered on your company •Updating of this module will be carried out once a week

13 Change: New return channel solutions for telephony, broadband and error status •New return channel solutions for telephony, broadband and error status are introduced

14 Change: Handle new Kapaks 4xx error codes •JNB did not recognize all Kapaks error codes •New Error codes added returned to Jara NetBusiness and B2B •The new Kapaks codes and the corresponding error message for the order services New Order and Move User 422 S Ø KET M Å TTE AVBRYTES, DA DET IKKE FINNES LEDIGE LINJERESSURSER Å VALIDERE P Å. Gir r ø dt lys 423 S Ø KET M Å TTE AVBRYTES. Å rsak: N ø dvendig henvisning til fordeler mangler for kundeadressen. Forholdet m å unders ø kes av Telenor kundeleveranse Gir gult lys 424 S Ø KET M Å TTE AVBRYTES. Å rsak: Henvisning finnes til flere enn `en fordeler for kundeadressen. Forholdet m å unders ø kes av Telenor kundeleveranse Gir gult lys 425 S Ø KET M Å TTE AVBRYTES. Å rsak: Kundeadressens n æ rmeste fordeler har ikke angivelse av teknologiomr å de for produktet. Vanligivs fordi fordeleren befinner seg for langt unna DSLAM tilknytningspunkt, eller fordi fordeleren mangler angivelse av annen å rsak. Forholdet m å unders ø kes av Telenor kundeleveranse Gir gult lys 442 S Ø K ETTER NYE LINJER M Å TTE AVBRYTES, DA DET IKKE FINNES LEDIGE LINJERESSURSER Å VALIDERE P Å Gir r ø dt lys 443 S Ø K ETTER NYE LINJER M Å TTE AVBRYTES Å rsak: N ø dvendig henvisning til fordeler mangler for kundeadressen. Forholdet m å unders ø kes av Telenor kundeleveranse Gir gult lys 444 S Ø K ETTER NYE LINJER M Å TTE AVBRYTES Å rsak: Henvisning finnes til flere enn `en fordeler for kundeadressen. Forholdet m å unders ø kes av Telenor kundeleveranse Gir gult lys 445 S Ø K ETTER NYE LINJER M Å TTE AVBRYTES Å rsak: Kundeadressens n æ rmeste fordeler har ikke angivelse av teknologiomr å de for produktet. Vanligivs fordi fordeleren befinner seg for langt unna DSLAM tilknytningspunkt, eller fordi fordeleren mangler angivelse av annen å rsak. Forholdet m å unders ø kes av Telenor kundeleveranse Gir gult lys

15 Change: Change from full to shared and shared to full access •Take orders of change form full to shared or shared to full access must be ordered by sending a Service Request

16 Change: Change name of end user •The order is built as an ordinary change order with modify search •New end user is searched up with attribute ”User 1 – Name”

17 Change: Product change from OA to Jara ADSL •Orders on product change from OA to Jara ADSL that involve change of exchange, you also must send a Service Request.

18 Bugfix: Digital Aksess - Should not be possible to submit without Telelosjinummer ATP •It was possible to submit Digital Aksess products without Telelosjinummer ATP. •Now you must filed out the Attribute Telelosjinummer ATP in Product Configuration •An error message is displayed if Telelosjinummer ATP is missing.

19 Bugfix: Duplicate s On Cancelled Orders •When cancelling an order, an (autorespons) should be auto generated and sent to the ISP. •Multiple s were sent for each cancelled order; one per line item. •This issue are now solved

20 Bugfix: Technical fixes in B2B There has been some small technical fixes for the B2B solution in this release. •Order Status Updates are sometimes not sent to partner ―This issue are now solved •Orders with outdated customer ID failed ―This issue are now solved

21 Bugfix: Change order OA change of “telelosji” and “blokkposisjon” •This funconality was released in release K •You must use Product Configuration to change this information •Not use Comment field

22 Bugfix: VAB change of “sperreprogram” goes to OMS but changes are not performed •This issue are now solved.

23 Bugfix: Change of user when customer id is outdated is rejected by OMS •When doing a modify search for a subscription with an outdated customer, no user information was previously returned from the search, instead, it was indicated that the user information is outdated •Changing the customer on such subscriptions should now be working, with one exception: •The field “Customer Ref” must NOT be set when previous user is outdated •This is because the field is mapped to an Order Reference in the applicatin, and causes a resource change (which is not allowed when user is outdated)