Welcome to the HCL Connections Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by the HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events, please visit our HCL Connections page.
SWAT Team also tested it ends with below questions.
Case notifications IBM Support TS002035804 Severity 4 Updated 20 June 2019, 11:34 AM CEST Limitation of uploadable files extensions IBM Support - 20 June 2019, 11:34 AM CEST ICS SWAT Update @Marcos Vinicius Gomes
Looking at the results from the tests carried out, including the additional test 5 , the way I am intepreteing the results is that code appears to give the line
overall precedence and overrides all other file limit (no-zero) settings for file specific extensions. This is only the case though when a setting of zero is used ".*">0
As seen with results of test 5, when non-zero value is used then it does NOT take precedence and honors other file extensions limit settings including ones that have a limit setting of 0. A clue here with the error here for test file WAV with setting <limit mimeFilenameRegex=".*\.wav">0</limit> stating that it is "is a type that is not allowed" rather than in other tests where global limit setting was 0 <limit mimeFilenameRegex=".*">0</limit> and error given was "The file cannot be attached because it is larger than the maximum file size of 0." which would indicate a different code path.
This needs to go to development to give reason : 1) Why "".*">0/limit is overridding other specific file extension limit settings that defined, why does it not honour file limit extension if there is a non-zero limit setting for it, can it be fixed so that it does? 2) Why does "".*">0/limit NOT give message ""is a type that is not allowed" rather than "file cannot be attached because it is larger than the maximum file size of 0."