ccbd792f8694477b985b1fa9447ff6f7Q: Hi Harris, I have spent some time look at your YT clips and so forth.
Say I wanted to set up a smart CRM, how many records could the system deal with. Could the system efficiently deal with (say) 500k records, task automation, security at field level, etc. The clips are fine, and I can appreciate the top layer benefits, but if you were (say) promoting a car, they really only deal with the paint job. I'm wanting to know about the underlying structure and the engine, etc.
Thanks in advance for your early reply.
Noel
Hey Noel. The system could handle a large number of records using the filtering system. We could easily add paging to the UI to make the UI a bit more scalable when a filter did not exist.
What kind of tasks would you want to automate? We are working on some notification automations for sending emails or Slack alerts. What else would be helpful for your use cases?
Currently we have security and permissions at the table level but we could add additional security down to the field level. I assume you'd want to hide some fields from some users. What else would be helpful here?
Having a robust no-code platform is fairly difficult but we are working toward solving any problem that is generally applicable to a large number of users.
I hope that helps. Hit me if you have any further questions.
The system could handle a large number of records using the filtering system. <<What about indexes. What CMS does it sit on?
We could easily add paging to the UI to make the UI a bit more scalable when a filter did not exist. <<OK
What kind of tasks would you want to automate? <<Pretty much using the No-Code as the Interface for Widgets - i.e. a user friendly interface to a bunch of "black boxes standard functions" at the CMS level. Some related examples. 1. Save a master record and populate it with data from related fields in other tables, with error checking. (i.e. If then else stuff) 2. Web hooks 3. Import mapping 4. RSS feeds (with actions driven by filters 5. If it is Friday, do this.)
We are working on some notification automations for sending emails or Slack alerts. <<OK - this is useful
What else would be helpful for your use cases? <<See the Commece.com product - there is a desktop version that is like using plasticine (https://www.commence.com/commence-rm-7-1-release-notes/). But the cost is ridiculous for small businesses. The Cloud solution, while streets ahead of Salesforce and other products I have seen/used, is too corporate-centric - small business workl very different to floors filled with university graduates :-)
Currently we have security and permissions at the table level but we could add additional security down to the field level. <<One of the faults of some databases to this day...
I assume you'd want to hide some fields from some users. <<Yes - and give users the opportunity to design their own screens using fields ni tables they have permissions for etc.
What else would be helpful here? <<The above is a general list - I suspect I have already outworn my welcome :-)
Having a robust no-code platform is fairly difficult but we are working toward solving any problem that is generally applicable to a large number of users. <<Understood. Thanks for getting back to me. Please keep me in touch with developments.