Changes for page eMagiz State Generation

Last modified by Erik Bakker on 2024/08/13 12:05

From version 27.1

edited by Erik Bakker
on 2024/08/08 15:48

Change comment: There is no comment for this version

To version 28.1

edited by Erik Bakker
on 2024/08/13 08:04

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -57,7 +57,7 @@
  A state can most logically be created in a central place through which the data flows. The reason for this, is that such a place has all the required information flowing through its processes to generate stateful data.
--The state store is implemented inside the eMagiz runtime using the H2 database for now. For time related operations another technology is used (Esper), and the functionality is only available on Docker based runtimes (to be release end Q2 2022). You wil find the specific Stateful components inside the Flow Designer as we use in eMagiz to model the flow. Aligned with the general concept of low-code developnment in eMagiz. For State store models, the current data modeling capabilities will be used.
++The state store is implemented inside the eMagiz runtime using various support objects. Once you have agreed on the license you can find store items in the store and components inside the Flow Designer as we use in eMagiz to model the flow. Aligned with the general concept of low-code developnment in eMagiz. For State store models, the current data modeling capabilities will be used.
  === 3.3 Use Cases ===