Overview

ISM's flexible and customizable architecture allows for the implementation of complex business processes in a simple and intuitive way. The flow designer provides a visual interface for building flows, where components can be easily added, configured, and connected to create a customized workflow.

ISM also provides a wide range of components that can handle various business operations such as validation, retries, and error handling. These components can be easily integrated into a flow to perform the required operations before transferring data from source to target.

In addition, ISM's monitoring and reporting capabilities provide good visibility into the execution of flows and business operations, allowing users to easily track the progress and status of their workflows.

Overall, ISM's design philosophy emphasizes ease of use and maintenance, making it accessible to less technical users while still providing the necessary flexibility and customization for complex business requirements.

ISM provides following components to implement business processes.

• Flow : Entire business process regarding interface.

• Task : Business logic inside a business process, which is executed step by step or by condition.

In addition to Flows and Tasks, ISM also provides the following components to implement business processes:

• Conditions: Used to define conditions that determine the path the flow should take based on the data being processed.

• Loops: Used to iterate over a set of data or execute a set of tasks repeatedly until a certain condition is met.

• Subflows: Used to modularize and reuse parts of a flow in multiple places.

• Event triggers: Used to trigger a flow based on a specific event, such as a file being dropped into a directory or a message arriving on a queue.

• Error handlers: Used to handle errors and exceptions that may occur during the execution of a flow or task.

While ISM allows for unlimited depth of subflow invocation, it is generally recommended to limit subflow invocations to three levels or less to maintain clarity and simplicity in the design of the flow. Deeply nested subflows can become difficult to manage and debug, and may lead to performance issues. It is best to use subflows sparingly and only when necessary to achieve the desired functionality.

Tasks can be divided into two types:

• Control Task

• Function Task

Once a flow has been designed in ISM, it can be published to the runtime environment where it can be executed. The flow's progress and performance can then be monitored through the ISM Admin UI, which provides users with a centralized location to manage and maintain all of their flows. This includes monitoring flow status, debugging any issues that may arise, and making any necessary updates or changes to the flow's configuration over time.