When deploying a BPM / SaaS workflow process using an SaaS environment, this is a short list of considerations. These three items comprise the core BPM components that require tenant separation within an SaaS environment.
- Accessing tenant specific workflow definitions
- Accessing tenant specific workflow instances
- Accessing tenant specific workflow tasks
In addition to these core BPM concerns, we must also consider how the following requirements will be addressed.
- Tenant data storage - How application data is separated from the BPM data
- Information routing - Security access control for items routed
When building a BPM / SaaS workflow solution within an SaaS environment, it is very important to monitor BPM activity and analyze the data gathered. It is possible for data to be lost or damaged if the SaaS environment is slowed down by BPM / SaaS workflow processes.
This is nothing new. We are all familiar with server processing speeds being negatively impacted as application loads and server requests increase. If your BPM application is struggling to function within the current server constraints moving the BPM processing to dedicated load balanced servers is one possible solution.
A small sampling of the Workflow Technology for BPM Solutions contained within our cDevWorkflow product offering can be found here: Workflow Technology That Works.
Learn more about our Process Automation & IT, QA Services or Software Development products and solutions on the Web! Visit us at: Innovative Process Solutions