DecisionRules

Product details

Q: Reading through the questions and answers here was a bit of a wild ride.

I have a few questions, but I was so exasperated at the lack of answers to real life use cases that I want to provide a few in case others find them useful.
Each of these is not only possible with this deal, but is also a real life scenario from clients I develop for.
- I have a wholesale client that uses price discrimination. Each of their ~10000 products has a series of price rules that determine the final selling price for their customers, depending on customer account type, season and the availability of stock levels that need to be compared to SLAs and projected sales to maintain customer contracts. The price rule itself is a formula that uses several variables, like cogs, markup tolerance, etc. While they're able to manage these with the solution I built for them, DecisionRules supports more functions out of the box, (and therefore more customized rules) than I built for them.
- I have another client that sells product kits. Each kit has anywhere from 3 to 20 components across a few different base configurations. Not all component combinations are compatible with all configurations and each time new components are manufactured, I have to change the legacy code base, which is a pain. DecisionRules allows these kit configurations to be constructed accurately with the client able to add new components at will.
- When building software, I don't always know what the business logic is up front. Sometimes clients are experimenting with new workflows and procedures that aren't codified yet. With DecisionRules, I can support this crazy development process by simply putting what I know of the logic in it instead of my code base and during demos, easily switch out the logic as necessary without having to update the code base right then and there. This also allows the client to collaborate with me more efficiently, which is likely to help them get to an actual decision about the logic quicker, as the demo is pretty much when the client does their best thinking.

Questions:
1. Is access to your BI API included in this deal? I bought Tier 4, in case it matters. If not, what do I have to do for access? Specifically, I'm looking for access to the audit endpoint.
2. There are conflicting answers below in earlier discussions, so what is the decision table row limit per table? What is the total row limit across the entire account?
3. What are the account upgrade options, when I need them? Will I forfeit my Tier 4 license to move to a customized monthly plan, or will the monthly plan stack on top of my Tier 4 license?

Thank you and good luck. This is a difficult market to compete in as I'm sure you know.

cc58PLUSJul 15, 2022
Founder Team
Erik_DecisionRules

Erik_DecisionRules

May 14, 2024

A: Hello,

Thank you for your comments and for sharing information about your use/business case on how you use the DecisionRules. We hope it will help your company in the day-to-day business.

Questions:
1) The BI, via a connector to the database is currently available only on the on-premise or private managed cloud. Our team will release an Audit API on the SaaS which will be available also for the AppSumo clients.

2) It was my mistake, there can be 1k rows in each Decision Table in all tiers. If you need more please contact us at sales@decisionrules.io and we can figure out something for you.

3) The AppSumo deal is a limited offer. Some limits can be increased, but the additional charge would be made on a monthly basis. We recommend opting in for a monthly plan if you need a custom-tailored package.

I hope it helps.

Regards,
Erik

Share
Helpful?
Log in to join the conversation