HD89951: RM9: LONG LINES TRUNCATED IN PRIMARY REQUIREMENT WHEN OPENED IN INFOPATH THROUGH A REQ CHAPTER OR A REQ MODULE.

APAR status

• Closed as program error.

Error description

• Long lines truncated in Primary Requirement when opened in
  InfoPath through a Req Chapter or a Req Module
  
  Additional Fixes
  Installed:
  Add on: CSE D6 SP3
  
  Scenario:
  Long lines are truncated in Primary Requirement when opening in
  InfoPath through a Req Chapter or a Req Module
  see description in the attached document.
  
  When Primary Requirement content have some long lines, these
  lines are truncated when editing in InfoPath the Req Chapter or
  the Req module containing the Prim Req.
  These long lines are correctly displayed when opening the Prim
  Req directly in InfoPath.
  
  Requirement content is not truncated in New, checked Out or
  Checked In
  Primary Requirement when opening Prim Req directly in InfoPath:
  
  Requirement content is truncated in New, Checked Out or
  Checked In
  Primary Requirement when opening Req Module in InfoPath :
  
  Requirement content is truncated in New, Checked Out or
  Checked In Prim Req when opening Req Chapter in InfoPath :
  
  The correct behavior when opening Req Chapter or Req Module must
  be the same as opening Primary Requirement directly in InfoPath.
  

Local fix

Problem summary

• Scenario:
  1.When Primary Requirement content have some long lines, these l
  aretruncated when editing in InfoPath the Req Chapter or the Req
  module containing the Prim Req.These long lines are correctly
  displayed when opening the Prim Req
  directly in InfoPath.
  2. Requirement content is not truncated in New, checked Out or
  Checked InPrimary Requirement when opening Prim Req directly in
  InfoPath:
  3. Requirement content is truncated in New, Checked Out or Check
  InPrimary Requirement when opening Req Module in InfoPath :
  4.Requirement content is truncated in New, Checked Out or Checke
  Prim Req when opening Req Chapter in InfoPath :
  .
  Expected Result: When opening Req Chapter or Req Module must be
  same as opening Primary Requirement directly in InfoPath.
  

Problem conclusion

• THIS PROBLEM WILL BE FIXED ON  BPA DELIVERY8 ON SmarTeam V5R20 G
  level.
  NOTE THAT THIS PROBLEM WILL ALSO BE FIXED ON BPA V5.7SP7 on Smar
  V5R19SP7.
  

Temporary fix

Comments

APAR Information

• 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

  SMARTEAM NT>XP

• Fixed component ID

  569199970

Applicable component levels

• R519 PSN

     UP