IBM Connections

Latest News from IBM

• REST API response is not in the specified format if the response code is not 200.

  Even though the response format (_format=xml) is specified in the URL parameter, I got the response in the json format when the response code is not 200.

• IJ49367: IN THE PURCHASE ORDERS(NUC) APPLICATION, TECHNICAL TERM IS WRONGLY POPULATED IN THE TERM AND CONDITIONS SECTION.

  Problem Description:

• IJ49458: IN THE INSPECTIONS, "INVALID TIME" ERROR WHILE TRYING TO ENTER TIME IN HH:MM:SS FORMAT.

  STEPS TO REPRODUCE:

• Question regarding Prorate Cost Functionality for FIFO and LIFO items

  Could you provide more details about Prorate Cost Functionality for FIFO and LIFO items?

• IJ49153: THE ISSUE IS THAT IN MAXIMO, PR.NOTES (A NON-CORE COLUMN) NEEDS TO BE DEFINED AS MAXTYPE=CLOB, LENGHT=999999 FOR COLUMNS THAT AR

  THE ISSUE IS THAT IN MAXIMO, PR.NOTES (A NON-CORE COLUMN) NEEDS TO BE DEFINED AS MAXTYPE=CLOB, LENGHT=999999 FOR COLUMNS THAT AR

• MAXADMIN Database User Blocked

  If the MAXADMIN database user is blocked due to incorrect password entry, Maximo Asset Management will not start up and cannot be used.

• IJ49377: NASHORN SCRIPT CAUSING OUT OF MEMORY

  Nashorn script engine is storing global object and not releasing - which causes OOM errors. We need to wrap nashorn scripts with

• IJ49381: TYPE-AHEAD LIST LIMITED BY FIRST SELECTION MADE IN BROWSER SESSION

  Steps to reproduce: 1. Configure TypeAhead for Location field in Work Order Tracking

• IJ49375: TAX VALUES NOT POPULATING PR/PO BASED ON ORGANIZATION TAX CODE HIERARCHY

  ABSTRACT: Tax Values Not Populating PR/PO Based On Organization Tax Code

• IJ49365: INPUT NODE OPTIONS ARE DISPLAYED INCORRECTLY WHEN CALLED VIA REST API

  ABSTRACT : Input Node options are displayed incorrectly when called via REST API