The following sections describe known limitations that you might encounter while working
with workstreams in Workplace.
- Restrictions on large file uploads and SVG browser display for ECM and
BPM documents
- To prevent any potential security issues, the following restrictions on large file uploads and
SVG browser display have been instated for ECM and BPM documents.
These restrictions expand the set of default restrictions and strengthen the default configuration,
which prevented viewing text or HTML content directly in the browser.
- The default maximum file size for document uploads through views in the Content Management toolkit is 100 MB.
- SVG documents cannot be directly viewed in the browser, but can be downloaded instead.
- To configure file restrictions in Workstream Services, you must add a
Lombardi custom secret file that contains a 100Custom.xml configuration with
relevant restrictions. You can customize this configuration by adding
file restrictions by type and size to 100Custom.xml. See the following example
for such a configuration:
<properties>
<server merge="mergeChildren">
<!-- max file size of 50kb -->
<document-attachment-max-file-size-upload>50000</document-attachment-max-file-size-upload>
<!-- mime type white list which specifies mime types accepted for -->
<!-- upload to document list or document attachment -->
<document-attachment-accepted-mime-types>
<!-- specifies whether to allow a null mime type for upload -->
<allow-null-mime-type>false</allow-null-mime-type>
<!-- lists the mime types allowed for upload -->
<mime-type>text/plain</mime-type>
<mime-type>img/png</mime-type>
</document-attachment-accepted-mime-types>
<!-- mime type black list which specifies mappings from unacceptable -->
<!-- mime types to acceptable mime types for download from -->
<!-- document list or document attachment -->
<document-attachment-download-mime-types>
<!-- will map text/html mime type to text/plain mime type -->
<mime-type-map>
<from>text/html</from>
<to>text/plain</to>
</mime-type-map>
<!-- missing <to> element implies mapping to content/octet-stream -->
<mime-type-map>
<from>application/pdf</from>
</mime-type-map>
</document-attachment-download-mime-types>
</server>
</properties>
- For more information about the supported file restrictions that are
configured in 100Custom.xml, see the following information:
- Unable to initialize data items for an approval activity in a custom workstream
- When Workstream Services and
Business Automation Workflow coexist in
the same container, in a custom workstream to which you added an approval activity, you cannot
initialize the approval data items that you configured to initialize at the start of the workstream.
To initialize the data items, add a form activity and provide initial values to the data items
required in the approval in the form.
- Workstreams cannot be deployed from a starter environment to a custom environment
- In previous releases, the starter pattern used for demonstration and trial purposes was based on
the Business Automation Workflow runtime
environment only and included Workstream Services. In the latest
version, the starter pattern, which still has Workstream Services in it, includes both
the Business Automation Workflow runtime
environment and the Business Automation Workflow authoring
environment.
- You can create and configure your own workstreams in the starter environment, but you cannot
export and import these workstreams into a custom environment. If you try building an app that
starts a workstream built in the starter environment, you cannot deploy and use the app in the
custom environment because the workstream cannot be deployed from one environment to another.
For more information, see the IBM Cloud Pak for Business Automation known limitations.