It would be an error to say that low-code platforms are an exclusive prerogative of BPM systems. In a wide sense, any modern platform already is low-code. Computers do not operate on a level of programming languages. They just execute sequences of binary commands. In this sense, any programming language, even low-level one, such as assembler, already is a low-code platform, which compiles high level human readable programming code into native binary command flows of computers.
On a higher level, for at least past 20 years, all modern development environments dedicate to graphical IDE simplifying routine code writing. Nearly every modern coding platform is low-code platform. The trend is especially evident in GUI design in its most wide sense. Therefore, in vast majority of programming tasks low-code platforms are not a disruptive innovation but long established and commonly accepted mainstream.
BPM brings low-code platforms to the next level of abstraction where they operate not on technical aspects of implementation but high-level business logic. The success of this mission crucially depends on elimination of disruption introduced by the platform. Successful low-code BPM platform must ensure guaranteed compatibility of widest technology set utilized by modern enterprises and complete transparency of transition from high-level BPM view to low-level programming access. Such an adaptive platform reconciles contradictory views of versatile stakeholders in an organization.
Alas, many real BPM platforms pay too little attention to transparency and integration. This largely explains a compromised reputation of BPM as of disruptive technology. If low-code platform is too disruptive, it just indicates low quality of the platform in question and in no way generalizes to typical and universal case.