Maximo Anywhere

  • 1.  Work list records could not be downloaded error on Work Items List View in Anywhere

    Posted Fri September 24, 2021 01:07 PM
    Hi ,

    The following error message is triggered when an automation script is invoked in OSLCWODETAIL object structure. The script invokes overrideValues(ctx) to set value on non-persistent field for displaying in the UI of Work order details view. I'm not sure how to overcome this issue. Please let me know whether anyone has faced this issue before. 


    ------------------------------
    MAX092012
    ------------------------------


  • 2.  RE: Work list records could not be downloaded error on Work Items List View in Anywhere

    Posted Mon September 27, 2021 08:02 AM
    Are you sure your Automation Script isn't generating an error? It seems like Maximo is getting an error code in the response instead of a 200 success. I'd check your application server (WebSphere/WebLogic) to see if Maximo is throwing an error when it calls your automation script. Understanding what that error is we'd be better able to assist with the underlying problem.

    ------------------------------
    Steven Shull
    ------------------------------



  • 3.  RE: Work list records could not be downloaded error on Work Items List View in Anywhere

    Posted Mon September 27, 2021 11:43 AM
    Is the automation scripts supposed to do something with the Maximo Anywhere UI?  Or is it for core Maximo UI the automation script action is intended.  My experience indicates that is you want the automation script to do something in the UI for the user on core Maximo do NOT use the OSLCWODETAIL object structure.  That is intended for Maximo Anywhere.  It was built for Maximo Anywhere.  If you want to provide some type of UI interaction on Maximo anywhere then the automation script from core Maximo CANNOT be used.  There is no mechanism on Anywhere to work with the Automation scripting.  You have to do all that in JavaScript in the Maximo Anywhere framework.  So please help us understand what you intend to do. What is your use case scenario?

    ------------------------------
    Bradley K. Downing , MBA
    Solutions Engineer
    IBM
    Bakersfield CA
    ------------------------------



  • 4.  RE: Work list records could not be downloaded error on Work Items List View in Anywhere

    Posted Tue September 28, 2021 01:51 AM
    How do you know that this error is happening only when that particular script is triggered? If you found from Maximo logs then Maximo logs must also give you some information on why the script is failing.
    1. Which version of Anywhere are you using? Anywhere 764 has a problem with download work list when using web server url. The request url size is too long for web server to process data.
    2. Are you facing script failure while updating work order data as well? Like update description of the work order from anywhere and the script failure logs can be seen.
    3. Iterating the point from Bradley - what is it that you are trying to achieve by calling object structure script?

    ------------------------------
    Biplab Choudhury
    Maximo Consultant
    Tata Consultancy Services
    Melbourne
    ------------------------------



  • 5.  RE: Work list records could not be downloaded error on Work Items List View in Anywhere

    Posted Tue September 28, 2021 05:24 AM
    Hi,
    Thank you everyone for your reply! I was trying to achieve something on Anywhere side , typically populating description for a related record field in anywhere only hence I thought of creating an automation script on the OSLCWODETAIL object structure to populate the same by creating a non-persistent field on WORKORDER object. 
    I was confident that the error was occurring due to the script because if I de-activated the script then the error was no longer occurring and there was an error in the log which stated null pointer exception. I figured out that the issue was due to AUTOSCRIPT.INTERFACE = 0 instead of 1 for the automation script which was resulting in the error. For some unknown reason the flag did not get checked when the script was initially created. 

    I have finally achieved the requirement using handler instead out going for automation script. Thanks once again for all the response.

    ------------------------------
    MAX092012
    ------------------------------