The OYKR Process Communicator (OPC) can allow the Metastorm BPM developer to build more efficient and reliable processes and deploy them faster.

The OPC allows this by enhancing and extending the existing concept and adds functionality that allows processes to respond to incoming files without requiring the engine to poll repeatedly & unnecessarily.

Currently developers cope with the fact that flags do not respond to say if the intended action was successful or not, this mode of working can be referred to as fire and forget. If the requested action is not available or fails then the user and client are none the wiser and the processes may hang causing problems to build up behind the scenes. The OPC replaces the flag concept with messages

The OPC allows the developer to queue messages within the database and they are then processed and marked as successful or failed. If the message fails, the reason is recorded alongside the original message to allow the developer to take the appropriate action. If the message failed due to an error within the process any failed messages can be re-queued for processing once the original issuer has been fixed. This ensures no messages are ever lost.

The OPC also introduces the ability for a process to respond to incoming files without the need for repeated & time consuming polling of a directory. Incoming files may be used to start a process or drive an existing process onwards. The OPC allows you to set up multiple directories where files entering these areas drive the related process forward.

Key features of the OYKR Process Communicator:

Orchestrate process events via the database from any process or system

Orchestrate process events via the file system.

Pro-active fault monitoring and notification.