IBM Support

JR61147: DOC - PASSING A TW.OBJECT.MAP VARIABLE FROM A CLIENT-SIDE HUMAN SERVICE TO A SERVICE FLOW IS NOT WELL DOCUMENTED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • When a variable is created in a client-side human service, a
    JavaScript variable is created in the background. When the
    client-side human service was developed, the ES6 map was not
    available; an array with key and values pairs was created
    instead for when a variable of type tw.object.Map is created.
    
    To access the data of that map variable at run time in the
    client-side human service, you must access it the way it's
    described in the answer to "Why can't I see the values when
    using a Map data type as a return value of a nested service from
    within my Client Side Human Service?"
    (https://developer.ibm.com/answers/questions/468584/why-cant-i-s
    ee-the-values-when-using-a-map-data-ty.html).
    
    The auto-mapping will map from a tw.object.Map to a
    tw.object.Map so data can be sent from a client-side human
    service to a service flow.
    
    You can't use an ES6 map to map a client-side human service to a
    service flow by creating it by using tw.local.myMap = new Map();
    because the default JSON serialization for an ES6 map is the
    empty object ({}).
    
    The documentation must be revised to reflect what is done with a
    tw.object.Map. It should also explain that having an object of
    type any in the service flow and passing an object from the
    client-side human service to that service flow will not work
    because there is no type information when you send the object
    from the client-side human service to the service flow.
    
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM)
    IBM BPM Express
    IBM Business Automation Workflow
    

Local fix

Problem summary

  • No additional information is available.
    

Problem conclusion

  • The content will be updated the next time the documentation is
    refreshed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR61147

  • Reported component name

    BUS AUTO WORKFL

  • Reported component ID

    5737H4100

  • Reported release

    J00

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-05-29

  • Closed date

    2019-06-03

  • Last modified date

    2019-06-03

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"19.0.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 June 2019