IBM Support

JR44978: WEB PROCESS INSPECTOR DOES NOT SUPPORT EDITING OF SIMPLE BUSINESS OBJECTS AS PART OF TASK DATA

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a Business Object is created and is a simple type, the Web
    Process Inspector throws an IOException when the task data is
    viewed using the "Edit Data" feature
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Any administrator of processes that use     *
    *                  simple business objects as part of task     *
    *                  data.                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Web Inspector REST Facade does      *
    *                      not correctly handle variables where    *
    *                      the type has simply been aliased        *
    *                      (i.e. a custom BO created with a        *
    *                      simple type, e.g. Date). It only        *
    *                      handles primitive types and complex     *
    *                      type variables properly.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A variable has two different "types" - there is a type name,
    as well as an actual type. For example, the customer's type in
    this scenario was "Wirksamkeit", whereas the actual type was
    "date". The code was incorrectly using the type name to
    determine type information, which works properly for primitive
    types like Strings, Integers, etc., but will not handle this
    case. The code made the assumption that anything that's
    not a primitive type should just be parsed as JSON and
    returned to the browser, but this assumption only holds if the
    actual type is "object" (e.g. the variable is a complex type).
    

Problem conclusion

  • Code was added to make the actual type name available to the
    affected method (as String, which is used for stringifying
    variables based on their input type) in the code. We also
    added fallback code to catch parser errors and instead fall
    back to stringifying the variable.
    
    For install/uninstall instructions, please download the README
    file along with the JR44978 ifix file from Fix Central.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR44978

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-30

  • Closed date

    2013-02-07

  • Last modified date

    2013-02-07

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 October 2021