BPM, Workflow, and Case

BPM, Workflow, and Case

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

  • 1.  Unable to Upload Excel Files in BPM/BAW? SOLVED!

    Posted Tue February 25, 2025 11:20 AM
    Edited by Peter Victor 2 days ago

    Hi IBM community,

    Today, I'll be discussing an issue I encountered while attempting to upload Excel files in BAW/Workflow Authoring, which is part of Cloud Pak for Business Automation (CP4BA) v24.0.1.

    Problem Definition

    Document Attachment document mime-type application/vnd.openxmlformats-officedocument.spreadsheetml.sheet and extension xlsx is not accepted for upload to the server. The following error can be seen in the "icp4adeploy-bastudio-deployment-0" pod.

    "SRVE0293E: [Servlet Error]-[CREATE_FILE_FAILED]: java.lang.SecurityException: Document Attachment document mime-type application\/vnd.openxmlformats-officedocument.spreadsheetml.sheet and extension xlsx is not accepted for upload to the server\n\tat com.lombardisoftware.portal.servlet.ECMDocumentServlet.createDocument(ECMDocumentServlet.java:1138)\n\tat com.lombardisoftware.portal.servlet.ECMDocumentServlet.createDocument(ECMDocumentServlet.java:1108)\n\tat com.lombardisoftware.portal.servlet.ECMDocumentServlet.access$1200(ECMDocumentServlet.java:90)\n\tat

    For Workflow Authoring: Add the XML content (mentioned below) directly as a value to the bastudio_custom_xml key under:

    spec:
  bastudio_configuration:
    ...
    bastudio_custom_xml: |
      <properties>
        ...
      </properties>

    For Workflow Runtime: Create a Kubernetes secret that contains the custom XML and reference it using the lombardi_custom_xml_secret_name field under:

    spec:
  baw_configuration:
    ...
    lombardi_custom_xml_secret_name: secret-name

    I added the following parameters: <document-attachment-accepted-mime-types> along with the first three mime types, as shown below. After making these changes, the upload worked successfully.

    <properties>
	<server merge="mergeChildren">
		<!--  mime type allowed list which specifies mime types accepted for  -->
		<!--  specifies whether to allow a null mime type for upload  -->
		<allow-null-mime-type>false</allow-null-mime-type>
		<document-attachment-accepted-mime-types>
			<mime-type>application/vnd.ms-excel</mime-type>
			<mime-type>application/vnd.ms-excel.sheet.macroEnabled.12</mime-type>
			<mime-type>application/vnd.openxmlformats-officedocument.spreadsheetml.sheet</mime-type>
			<mime-type>application/vnd.openxmlformats-officedocument.wordprocessingml.document</mime-type>
			<mime-type>application/vnd.openxmlformats-officedocument.presentationml.presentation</mime-type>
			<mime-type>application/msword</mime-type>
			<mime-type>application/vnd.ms-powerpoint</mime-type>
			<mime-type>application/pdf</mime-type>
			<mime-type>application/rtf</mime-type>
			<mime-type>application/xml</mime-type>
			<mime-type>application/zip</mime-type>
			<mime-type>text/plain</mime-type>
			<mime-type>text/csv</mime-type>
			<mime-type>text/html</mime-type>
			<mime-type>image/bmp</mime-type>
			<mime-type>image/gif</mime-type>
			<mime-type>image/jpeg</mime-type>
			<mime-type>image/tiff</mime-type>
			<mime-type>image/png</mime-type>
		</document-attachment-accepted-mime-types>
	</properties>

    This solution resolved the issue, and I hope it helps others facing similar challenges. Feel free to reach out if you have any questions!

    Note: In CP4BA v24.0.0 and later, Workflow Authoring is now merged into the BAStudio pod, unlike earlier versions (e.g., v21.0.3) where it was deployed as a separate pod.

    [1] https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/24.0.1?topic=studio-optional-customizing-business-automation-properties

    [2] https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/21.0.3?topic=bawarws-optional-customizing-business-automation-workflow-properties

    [3] https://www.ibm.com/support/pages/make-changes-100customxml-file-modify-business-automation-workflow-configuration-cloud-pak-business-automation
    [4] https://www.ibm.com/mysupport/s/defect/aCI3p000000bm2TGAQ/dt195853?language=en_US

    [5] https://community.ibm.com/community/user/automation/discussion/mime-type-extension-conflict-when-uploading-to-bpm-document-store-v21



    ------------------------------
    Peter Victor
    ------------------------------



  • 2.  RE: Unable to Upload Excel Files in BPM/BAW? SOLVED!

    Posted Thu May 29, 2025 09:03 AM

    Peter Victor Thanks for your effort and for sharing the workaround, but if you restart the pod, all those configuration changes will be removed because I didn't see the config file mounted to a PVC or external volume.



    ------------------------------
    Mohamed Mousa
    ------------------------------

    Original Message


  • 3.  RE: Unable to Upload Excel Files in BPM/BAW? SOLVED!

    Posted 2 days ago

    Yes, you are correct. I will update the article with the following.

    The only permanent method is to add the previous sections as a value to the key bastudio_custom_xml for Workflow Authoring under spec: bastudio_configuration: section

    or create a secret and pass the secret name to lombardi_custom_xml_secret_name for Workflow Runtime under spec: baw_configuration: section



    ------------------------------
    Peter Victor
    ------------------------------

    Original Message


  • 4.  RE: Unable to Upload Excel Files in BPM/BAW? SOLVED!

    Posted 2 days ago

    Adding to the above, 

    Applying the above to allow different/additional mime types to be uploaded/allowed from server backend / product configuration. 

    But now all IBM BPM Workflows can upload the configured mime types so to control this per workflow / screen we need to configure the below in "ECM Document List Control"  to define allowed types as per business needs.



    ------------------------------
    Mohammed Shaker
    IBM BPM Consaultant
    Valleysoft
    Nasr City
    01007073310
    ------------------------------

    Original Message


Related Content