Changes for page eMagiz State Generation
Last modified by Erik Bakker on 2024/08/13 12:05
From version 31.1
edited by Erik Bakker
on 2024/08/13 12:05
on 2024/08/13 12:05
Change comment:
There is no comment for this version
To version 30.1
edited by Erik Bakker
on 2024/08/13 12:04
on 2024/08/13 12:04
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -57,7 +57,7 @@ 57 57 58 58 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. 59 59 60 -The state store is implemented inside the eMagiz runtime using various support objects. Once you have procured the license you can find[[store items(Navigation)>>doc:Main.eMagizStore.Accelerators.WebHome||target="blank"]]and components inside the Flow Designer.Thesecanbeused to model theflow.60 +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. 61 61 62 62 === 3.3 Use Cases === 63 63