IBM Support

IV96441: GOOGLE MAPS NOT SHOWING ALL WORKORDERS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • REPRODUCTION STEPS
    1. Go to Administration ---->Service Address --> Create a new
    record
    "SKINUDT-KLV-1"
       With Latitude = 55.6399880000 / Longitude = 12.5497770000
    
    2. Save changes --> Go to Wotrack--> Create a new record
    "818963" -->
    Click on Service Address tab --> Associate the service addreess
    created above.
    
    3. Save changes and create another workorder record "818964"
    --> Click on Service Address tab --> Associate the service
    addreess created above
    --> Save changes.
    
    4. Setup Workorder application in Application designer with
    ability to view Multiple Markers on a Map in Maximo.
    
    5. Go to Application Deisgner --> Wotrack --> Click on Map
    tab-->
    Highlight Map    section--> Click on Control Properties-
       Data source = results_showlist.
       Width = 100%
       Height = 100%
       Under Tool Items --> Check AssetLocationTool - Check
    FullScreen and check LayersTool.
    
    6. Save changes
    
    7. Setup MAP administration GOOGLE --> Go To Administration -->
    Map Manager --> Create a new map called "GOOGLE"
       SITE = BEDFORD
       Latitude = 55.6399880000
       Longitude = 12.5497770000
       Save changes.
    
    8. Go to Map Manager --> "GOOGLE" -->Enable it and save --> Go
    to Wotrack --> Filter for both workorders i.e "81896" both
    records will show up.
    
    9. Click on Workorder = 818963 --> Click on Map tab
    
    10. Click Marker on the Map ,
    
    INCORRECT BEHAVIOUR
    You will only see one workorder record = 818963 on the Google
    map, workorder record = 818964 is missing on the Google map.
    
    EXPECTED RESULTS
    Both Work Orders should be visible on Google map
    
    ENVIRONMENT
    BM WebSphere Application Server 8.5.5.3
    Tlvoli's  process automation engine 7.6.0.3 BuiId 20160114-1313
    DB BuiId V7603-151
    Version IBM TPAE Integration Framework 7.6.0.3 Build 20160108-1
    912 DB Build V7603-21
    IBM Maximo Asset Management 7.6.0.3 Build 20160113-2204 DB Build
    V7603-01
    Server OS  Windows 6.3
    Server DB Microsoft SQL Server 11.0 (11.00.6567)
    (c) Copyright IBM Corp. 2015
    
    Also observed at
    IBM WebSphere Application Server 8.5.5.11
    Tivoli's process automation engine 7.6.0.6-IFIX20170502-1943
    Build 20161019-0100 DB Build V7606-50 HFDB Build HF7606-05
    IBM TPAE Integration Framework 7.6.0.6 Build 20161014-1504 DB
    Build V7606-24
    IBM Maximo Asset Management Work Centers 7.6.0.1 Build
    20161014-1326 DB Build V7601-41
    IBM Maximo Asset Management 7.6.0.6 Build 20161019-0100 DB
    Build V7604-01
    
    Server OS  Windows Server 2012 R2 6.3
    Server DB  DB2/NT64 10.5 (SQL10054)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * GOOGLE MAPS NOT SHOWING ALL WORKORDERS                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Interim Fix for Release 7.6.0.9 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV96441

  • Reported component name

    ADMINISTRATION

  • Reported component ID

    5724R46A1

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-22

  • Closed date

    2017-08-02

  • Last modified date

    2017-08-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    ADMINISTRATION

  • Fixed component ID

    5724R46A1

Applicable component levels

  • R760 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPP5","label":"System Related"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 August 2017