IBM Support

IV77521: DOCUMENT UPLOAD WINDOW STOPS WORKING IF TRIED UPLOADING USING A TOO LARGE A DOCUMENT NUMBER VALUE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • If a user tries uploading a document to TRIRIGA and the document
    number has too many characters, the upload is allowed to begin
    but fails, with a vague error ("Error occurs while uploading
    file") being written to the screen and a message like the
    following being written to the server.log:
    
    2015-09-25 08:58:21,625 ERROR
    [com.tririga.platform.document.controller.DocUploadCont
    roller](Default Executor-thread-565) An error occurred while
    processing the upload of a document.[MID-1599977701]
    com.tririga.platform.error.PlatformRuntimeException:
    com.tririga.architecture.docmgmt.ExceededFieldSizeException:
    null
    rootCause=[ com.tririga.platform.error.PlatformRuntimeException:
    Cannot set a value for DM_DOCUMENT_NUMBER because its field size
    is smaller than the length of the new value ]
    [...]
    Caused by:
    com.tririga.architecture.docmgmt.ExceededFieldSizeException:
    null
    rootCause=[ com.tririga.platform.error.PlatformRuntimeException:
    Cannot set a value for DM_DOCUMENT_NUMBER because its field size
    is smaller than the length of the new value ]
            ... 90 more
    Caused by: com.tririga.platform.error.PlatformRuntimeException:
    Cannot set a value for DM_DOCUMENT_NUMBER because its field size
    is smaller than the length of the new value
            [...]
    
    The 'New Document' windows remains open. Any attempts to work
    from this window after this point initially fail with the same
    vague error message appearing on the screen and nothing being
    written to the server.log.
    
    The window only begins to work again once the user by chance
    realizes they need to reattach the file AND put valid number of
    characters in the document number field.
    
    An upload should not be allowed to begin if an invalid document
    number value is present.  An error or warning should appear
    before the upload starts.
    
    This issue has been seen in 3.4.2 as well as 3.4.2.1. It may
    have been present in earlier releases, as well.
    

Local fix

  • If you encounter this problem, specify a document number
    value that does not exceed the maximum length allowed in the
    business object for this field
       (e.g. if you are using the Out-of-Box Document Business
       Object, do not specify more than 150 characters)
    and reattach the file you want to upload.
    

Problem summary

  • The problem is due to an issue where the document upload window
    would fail to upload a document if its document number was
    longer than the Document Number field size.
    

Problem conclusion

  • This resolves an issue where the document upload window would
    fail to upload a document if its document number was longer
    than the Document Number field size.
    Input is now validated prior to form submission and a string
    longer than field size will no longer be typed into the input.
    This change set adds validation to the 'new document' upload
    window and the 'multi-document' upload window. Documents with
    name and number fields that are longer than specified in the
    document bo can no longer be submitted.
    This also resolves another issue where the document upload
    window would become unresponsive after a failed upload.
    This also adds descriptive error messages to the document
    upload window.
    This will be targeted for the 2h2015 release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV77521

  • Reported component name

    TRI APPLCATION

  • Reported component ID

    5725F26AB

  • Reported release

    342

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-09-28

  • Closed date

    2015-10-12

  • Last modified date

    2015-12-10

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

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

Modules/Macros

  • 999
    

Fix information

Applicable component levels

  • R342 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"342","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
30 March 2022