• Can parts of a process flow (process snippets) be dynamically called as work flows through the process, enabling the reuse of these process snippets?
…BIMIXS Cases contains user-defined business objects like orders, requests, applications and so on. Business objects are stateful, thus they can re-act on events. Parts of this reactionís processing are done by attached business rules. Business objects can be re-used in many different case-types, thus enabling the re-use of their behavior. It is a much more natural way of re-using the behavior of objects, than having just reusable parts of process flows, so called snippets.
• Does your solution incorporate documents as an integral part of the process? If so please describe how these documents and their underlying content/information is available in your solution.
…Yes, documents can be attached to Cases and Talks. Depending on the state, documents can be modified and/or deleted. Versioning as well as classifying and naming is done by the system automatically, thus the user does not have to worry about document classification and naming. When a Case or Talks will be closed, attached documents will be sent back to the owner as part of the Case and Talk report for archiving purposes.
• Does your system manage content from a single common interface that can access any content type regardless of format?
…Yes, but not all types of documents are supported by the system. Only Microsoft Office type of documents (Word, Excel, Power-Point and so on) and internet type of files like .jpg, gif, tif e.g. are allowed to be uploaded. It is not allowed to upload any type of executable files for security purposes.
• Does your solution offer digital signature capability to ensure the integrity of a specific document?
…Yes, this is done by the system automatically.
• Does your solution provide for versioning and version control at the folder, document, and field level? If so please describe this functionality in detail.
…Yes, document versioning is done by the system automatically. Folder structures are not necessary anymore, because documents are business objects which will be stored in the context of the Case or Task respectively. Structured data (fields) are stored in the context of the Business Object or Case or Task, depending on their Meta data definition. All structured data are versioned and stored in a database. Because people can work at the same time, everybody has its own copy of the data required. Without versioning it would not be possible to merge data on the Case level when tasks will be closed. The merging of data is defined by default rules, which can be extended by users on request.
• Describe the search and retrieval capabilities of your system.
…You can search for all of the data available in a Case or Talk. Because all information is stored in a relational database, search results show up in less than a second.
• Does your software include the ability to annotate without changing the underlying file, including redaction of information?
…There is no underlying file; redaction of information is visible by default, including date and timestamp.
• Does your software include the ability to link selected documents into a group and treat such documents as a single entity that retains its grouping/structure?
…Yes, but this feature is available only in the Enterprise Edition.