InRule vs. OpenText AppWorks

With InRule, we are expecting to be able to move business logic out of the developer domain and back into the business domain. Business logic is currently captured in UI (data validation) and middleware layers. These are areas in any application where leveraging InRule's capabilities allow for changes in business logic to be made with little or no IT involvement.

Especially for telecom sector, AppWorks handling huge data and transform it easily and very quickly to send it to target systems with in seconds. At a time communicate more than one systems.

Incentivized

• It is easy to tweak business rule parameters.
• Create new logic with low barriers.

Incentivized

• Entity model
• BPM
• User interface GUI
• Integrations

Incentivized

• Needs more debugging capabilities.

• Few Controls which needs improve from user interface
• Custom controls
• Data transformation

Incentivized

InRule's Support Portal provides a "one stop shop" for submitting support questions, accessing training information, managing licenses, and getting updates on InRule's roadmap.

InRule offers a more organized software design, a well-structured framework in design, and is easier for new users to start contributing given documentation. Drools is spreadsheet-based and lacking the capability to do really advanced pseudo-programming.

Incentivized

AppWorks platform is very user friendly which will help us to develop the components quickly and deploy it easily. Flows can be developed quickly compared to others platform where business users can view the flow easily.

Incentivized

• It is always reliable and efficient.
• Has won customers over.

• Integration management
• Rapid development
• SOA

Incentivized