To answer this question, let's go through each option to understand why it is correct or incorrect:
Option A) We can force the iProcess Engine to re-calculate its deadlines on all outstanding work items for a case by triggering an event on a particular step of the case.
This option is correct. In iProcess, you can trigger an event on a particular step of a case, which will cause the iProcess Engine to recalculate the deadlines for all outstanding work items related to that case.
Option B) Feedback from EAI Steps in failure/retry situations via SW_QRETRYCOUNT.
This option is correct. In iPE, SW_QRETRYCOUNT is used to handle failure/retry situations in EAI (Enterprise Application Integration) steps. It allows feedback on the number of retries attempted for a particular step.
Option C) Not all data is held in the database & hence we need to stop the engine for backup.
This option is incorrect. In iPE, all data is held in the database, and you do not need to stop the engine for backup purposes. The iProcess Engine is designed to handle backups without the need for stopping the engine.
Option D) Supports Oracle Real Application Cluster (RAC) for Oracle 10G.
This option is correct. iPE supports Oracle Real Application Cluster (RAC) for Oracle 10G. RAC allows multiple instances of the database to run on different nodes in a cluster, providing high availability and scalability.
The correct answer is C. This option is incorrect because all data in iPE is held in the database, and the engine does not need to be stopped for backup purposes.