Q: Hello Erik_DecisionRules , I looked at your site, it seems you are not including SSO (Single sign on) in ...
this deal, what scenarios will require that? Can you discuss it from web businesses standpoint and your business logic of not doing so.
Thanks

Erik_DecisionRules
May 14, 2024A: Hello Sumo-ling,
SSO is usually used by our bigger customers using Azure AD or similar identity providers. It is not included in the deal, because it requires a custom setup.
If you are interested in getting more details do not hesitate to contact us about the possibilities at sales@decisionrules.io
The SSO you can use is GMAIL, which is available for everyone using SaaS.
Thank you.
Regard,
Erik

Verified purchaser
Hello,
I understand it is used by your bigger customers but how it helps, is it like your customer can give one username and password to their employee to login in input system (causing trigger event), decisionrules and output system. Is this correct?
If yes, that means I can use my Gmail to achieve same ease of use provided my input system and output system, also accept the Gmail credentials. Correct?
Thanks

Verified purchaser
Hello,
Yes, this is correct there are various protocols used (SAML, OAuth,...) and also identity providers. Everyone using any of them has assigned their certificates and URLs which are different from client to client. Please see the documentation https://docs.decisionrules.io/doc/on-premise-docker/setting-up-sso
Yes, that's right, you can use your Gmail account, it is pretty much the same the only difference is that Gmail is widely used and the setting is the same for all its users, so we have it as a solution out of the box.
Regards,
Erik

Verified purchaser
Hello,
1. It seems Kafka, decision trees are not part of this deal. Can you suggest scenarios under which each of them will be needed. There shouldn't be so many restrictions the way you are putting.
2. Also advanced role management and API management are only part of certain tiers, which scenarios will warrant their use. What's difference between API calls as offered in each tier to API management as offered only in tier 4.
Thanks

Verified purchaser
Hello,
1. Yes, that is right. Kafka is used by our customers, who are making decisions based on the inputs from more systems. Kafka helps them to make asynchronous calls. In other words, wait for the information from multiple systems, then execute the decision.
Decision Trees will be a different way of rule creation, based on the if-then-else structure, there rules can be handled by tables or scripting rules currently.
2. Advanced permissions - every used in the space can have a different role with permission, e.g. only create tables, but no access to the rule flows. You can use the predefined roles or create custom ones.
Management API - basically you can manage your rules without using the UI, update/delete/create rules, move the rules from one environment to the other...
We have a couple of management APIs and we are exerting the list https://docs.decisionrules.io/doc/api/management-api
Regards,
Erik

Verified purchaser
Erik_DecisionRules,
1. Since you are not giving Kafka and decision trees in this deal, so what is the best way for user who buys this deal to progress, is there a common sense hack?
2. So that means, API as available in every tier works only with User interface and API management (license tier 4) can be used without user interface, is there a video to explain this. Lets say how will Zapier or Kconnectzit work in this scenario, will they work with API of license tier 4 or API as available in all tiers.
Thanks

Verified purchaser
Hello,
1. I am not sure if we understand each other. Our customers (80%) are using Decision Tables to create the rules because that's the way how business users can easily manage them. Kafka is used by clients whose architecture and systems rely on Kafka-based events. The recommendation is to create the rules in scripting rules/decision tables. :)
2. Solver API = decision making, is available in all the TIERS. The management API is only in the higher tier. In fact, management API is used for automatization of the tasks, e.g. you are using a pipeline Jenkins, so you want to move the rule from one environment to the other one. You will use a management API, which will take a rule with a defined TAG and move it to the other environment.
Zapier - you have a form where from which you extract data and you trigger events. If you want to make a decision based on the data from the form and then trigger the events you embed the DecisionRules in between these steps.
You can integrate DecisionRules anywhere where the REST API can be used and you make business decisions.
Should you have more questions please contact us at sales@decisionrules.io.
Regards,
Erik

Verified purchaser
Hello,
Thanks for your response.
1. Can you tell me how will a web based business use it? I use some conditional logics in forms but is there a way that I can use your solution to display choices. For example while consulting for oil and gas company, lets say I am tackling an assignment to decide price point based on certain criteria, I would like to give them (oil & gas company executives) a separate online page behind a paywall, where they can click and input parameters in plain English and get choices based on decisions.
Now to achieve such function, what a small web based business is suppose to do especially who will I display output parameters (or choices) on a web page. I understand "Decisionrules" is a rule engine in middle, but what is input here (web based interface on my website, lets call it 'A', is that a trigger event) and what will be output (again web based interface, lets call it 'C')?
But how A and C will be integrated. If this can be done, I can use it for many new simple functional pages (behind paywall) for my clients
I understand in bigger company, lets say input may be like data feed coming from stock market and output may be something like data warehouse, but I am talking about using it from a small company perspective whose systems are online. No internal data servers, no multiple systems.
2. Now in terms of writing rules, I can easily create them in table, means if this, then do this else do this. Or you mean to say one has to write 500 pages of code script for one rule, if that is the case then which language is compatible, JavaScript, PHP or Python (languages which I know). If it can be created only in tabular structure (like Excel) then things will be easy.
API calls- Seems this feature is required to integrate with input system (lets call it A) and output systems (lets call it C), these will be more clear based on your response to my point 1. So it seems neither I need Zapier or Kconnectzit (whose LTD I have from Appsumo), but if that is the case how will I connect APIs to system A and C. Also it seems I need to buy tier 4 (which is lot of money) to get API functionality in this deal. Is this understanding correct? Please clarify these doubts.
3. Role management- So one user can create rules, what else can be roles here, what is the need for role management in this context?
4. What do you mean by workflow engine? Can you share example in context of point 1 as listed above.
5. I want to start API business, using Rapid API type solution, so can my API use "decisionrules"
6. So it doesn't matter whether I buy tier 1 or tier 4, I will get new features and updates related to small business plan only. The only difference is each license tier has different restrictions and features (like advance role management permissions is part of tier 2 and 3 and Management API is only available for tier 4).
Is this what you mean?
7. Can you show me a demo? If yes how to contact you to see a demo?
Thanks

Verified purchaser
1. Can you tell me how a web based business uses it? I use some conditional logic in forms but is there a way that I can use your solution to display choices. For example while consulting for oil and gas company, let's say I am tackling an assignment to decide price point based on certain criteria, I would like to give them (oil & gas company executives) a separate online page behind a paywall, where they can click and input parameters in plain English and get choices based on decisions.
It is not clear what you mean by web business. If you want to use it for such use case, it is feasible. You have to understand that DecisionRules as such is working with the inputs provided by you/calling system, it runs through the conditions defined in the application and you get the result which you can use to display the results on the FE. Lets say the condition is to have a deal between 1-5 billion USD to give an access to the separate webpage.
The input will be 1.5 billion USD, the result is TRUE, so you display the page. To trigger the requested action, you need to handle it on your side based on the output which was TRUE.
Now to achieve such function, what a small web based business is suppose to do especially who will I display output parameters (or choices) on a web page. I understand "Decisionrules" is a rule engine in middle, but what is input here (web based interface on my website, let's call it 'A', is that a trigger event) and what will be output (again web based interface, lets call it 'C')?
You will show the outputs on FE or trigger events based on the results made during the decisions. Please see the answer above for the rest.
But how A and C will be integrated. If this can be done, I can use it for many new simple functional pages (behind paywall) for my clients
The pages are up to you how you handle them and what you want to achieve with the provided results.
I understand in a bigger company, let's say input may be like data feed coming from stock market and output may be something like data warehouse, but I am talking about using it from a small company perspective whose systems are online. No internal data servers, no multiple systems.
There are no servers required, only the data on the input fed via REST API. It is the same for SME/enterspice or startup, it depends on how your system is built, but in general, API is simple to use.

Verified purchaser
2. Now in terms of writing rules, I can easily create them in a table, meaning if this, then do this else do this. Or you mean to say one has to write 500 pages of code script for one rule, if that is the case then which language is compatible, JavaScript, PHP or Python (languages which I know). If it can be created only in tabular structure (like Excel) then things will be easy.
There are decision tables = no code, simple and easy to use 80% of our clients are using this kind of rule creation. You can export to XLSX/CSV edit the rules and import them back in
scripting rules = JavaScript, which allows you to create more complex rules and combine them with decision tables
rule flow = graphical editor to connect decision tables and scripting rules together
API calls- Seems this feature is required to integrate with input systems (let's call it A) and output systems (lets call it C), these will be more clear based on your response to my point 1. So it seems neither I need Zapier or Kconnectzit (whose LTD I have from Appsumo), but if that is the case how will I connect APIs to system A and C. Also it seems I need to buy tier 4 (which is lot of money) to get API functionality in this deal. Is this understanding correct? Please clarify these doubts.
I would not say "a lot of money" for a lifetime offer. If you will use it as the core functionality of your application that makes you money, there is no point to talk about the price (kindly please check the price of other rule engines on the market). Zapier is currently not supported but might be in the future. I don't understand the second half of the question, you can use the TIER 1 in the same way as TIER4, only the limits are different.

Verified purchaser
3. Role management- So one user can create rules, what else can be roles here, what is the need for role management in this context?
Please refer to the documentation https://docs.decisionrules.io/doc/teamwork/advanced-permissions or try it in the application.
4. What do you mean by workflow engine? Can you share an example in context of point 1 as listed above.
https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation - please see the link to what I mean by workflow management. This tool is not a BPMN tool, but a rule engine.
5. I want to start API business, using Rapid API type solution, so can my API use "decisionrules"
We don't have an experience with Rapid API, but based on quick research it could be possible.
6. So it doesn't matter whether I buy tier 1 or tier 4, I will get new features and updates related to small business plan only. The only difference is each license tier has different restrictions and features (like advance role management permissions is part of tier 2 and 3 and Management API is only available for tier 4).
Yes, small plan is the one of which the features will be included.
Is this what you mean?
Yes.
7. Can you show me a demo? If yes, how to contact you to see a demo?
Via the email as you have already done it. We are in Prague, GMT+2 timezone. We can offer you a demo on April 19th, at 3PM CET.