IBM Support

JR47092: DOC - DESIGN LIMITATION FOR COACH VALIDATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • Design Limitation & issue:
    Based on the as design debug web capability that is not
    designed for web 2.0 fashion, if you step, and if validation is
    required (i.e. fireValidation is set to true on boundary
    event),  since the validate boundary event path is a loop back,
    it will always go back to open a new coach.  As well, as the
    validate boundary event response will not be able to go back to
    in the originating coach in debug(as it will open up a new
    coach), and hence visual error decoration will not be
    presented.
    

Local fix

  • You can still step and see validation error in debug page, but
    it will always return back to a new coach. The workaround is
    that once you have debugged the validation path, and have
    checked the debug info page,i.e. tw.system.coachValidation
    error information, you will need to either 'run' to continue or
    'run' to next break point defined in the next step in regular
    boundary event flow in order to move to next step in the
    regular boundary event flow.
    

Problem summary

  • Proposed changes to Information Center is to add the following
    tip to step 9. c. in Building Coaches topic,
    
    <change>
    Tip: If you step through a process and validation is required at
    a step, the validate boundary event path loops back and goes
    back to open a new Coach. Because the validate boundary event
    response cannot go back to the originating Coach during the
    debugging, you don't see a visual error during debugging. You
    can step through a
    process and see the validation error on the debug page, but it
    always
    returns to a new Coach.
    After you have debugged the validation path, and you have
    reviewed the debug info page, including
    tw.system.coachValidation error information, select one of the
    following options:
    -Run to continue.
    -Run to the next break point that is defined in the next step in
    a regular boundary event flow. This option moves to the next
    step in the regular boundary event flow.
    </change>
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR47092

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    801

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-26

  • Closed date

    2013-07-30

  • Last modified date

    2013-07-30

  • 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":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
30 July 2013