Global Context

Question

Global Context

Closed this issue 10 years ago · 5 comments

rande commented 11 years ago

There are 2 timeline entities created when using a custom context: one for the context and one named GLOBAL

if the point of GLOBAL is to be able to list all elements from the timeline table, then there is no need of it.

Am I missing something ?

Answer 1 · 2013-09-17T08:03:41.000Z

Yes, by default, all actions are dupplicated on context GLOBAL. But you can deactivate it with configuration.

See spread.on_global_context

Answer 2 · 2013-09-17T11:13:28.000Z

@rande @stephpy we also struggled with this concept, and we're still not sure if we're implementing it 100% correctly. Why would i want to have the same entry in both the GLOBAL and the custom context?

Answer 3 · 2013-09-17T12:47:09.000Z

I had a use case with that.

3 tab uses timeline actions on 3 differents contexts: Contacts, Enterprises, Focus.

but there was a page which group|merge theses contexts. (using GLOBAL context)

We could set spread.on_global_context by default to false.

Answer 4 · 2013-09-17T15:58:16.000Z

hi @pulse00, just for information, I am starting to integrate this bundle into sonata: the next step will be to integrate the notification bundle to start spread service.

http://sonata-project.org/bundles/timeline/master/doc/index.html

Answer 5 · 2013-09-17T16:16:40.000Z

@rande i've seen it. great idea!