Memento

Next topic

Author	Message
Monica Giambitto	Thursday 02 December 2010 3:20:41 am Ok, it's been a while I try to understand in a deep way how ez execute and how workflows enter the game. I've tracked down the execution of a module deep down to a single event and back and, here and there, I found references to this "memento" thing. As far as I can see, and due to the fact "memento" means something to remember, I think it's ez way to keep track of the steps of execution. Is there anywhere something that describe better the memento mechanism? Or someone that can explain it? Thanks a lot.
Franck Grenier	Friday 03 December 2010 5:09:10 am Hello, I'm also trying to understand "memento". "Memento" are linked to workflow processes by the "memento_key".They are created by the eZModuleOperationInfo class. For one process, there is a main memento and a child memento. All of my processes do not have a memento. So I do not understand when they are generated and what they are made for. Need help. Developer at Open Wide

Author

Message

Thursday 02 December 2010 3:20:41 am

Ok, it's been a while I try to understand in a deep way how ez execute and how workflows enter the game.

I've tracked down the execution of a module deep down to a single event and back and, here and there, I found references to this "memento" thing. As far as I can see, and due to the fact "memento" means something to remember, I think it's ez way to keep track of the steps of execution. Is there anywhere something that describe better the memento mechanism? Or someone that can explain it?

Thanks a lot.

Franck Grenier

Friday 03 December 2010 5:09:10 am

Hello,

I'm also trying to understand "memento".

"Memento" are linked to workflow processes by the "memento_key".They are created by the eZModuleOperationInfo class. For one process, there is a main memento and a child memento.

All of my processes do not have a memento. So I do not understand when they are generated and what they are made for.

Need help.

Developer at Open Wide