0045638: Extend state actions and hooks to allow usage and return of Global State

Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #45638		[ All Revisions ] [ Back to Issue ]
Summary	0045638: Extend state actions and hooks to allow usage and return of Global State

Revision	2020-12-23 13:58 by cberner
Description	Currently, model actions and hooks in mobile.core only support state at the model level(not counting Global Actions), and return a part of the State, the one regarding the model. This is a limitation for other tasks, as such, an extension should be made on those hooks to accept and return the modified state, completely, that means, if a Global State is provided, it should apply the same changes as before, but return the modified Global State, not just the part regarding the model. This should be done in the scope of org.openbravo.mobile.core module.

Revision	2020-12-22 17:16 by cberner
Description	Currently, model action hooks in mobile.core only support state at the model level(not counting Global Actions), and return a part of the State, the one regarding the model. This is a limitation for other tasks, as such, an extension should be made on those hooks to accept and return the modified state, completely, that means, if a Global State is provided, it should apply the same changes as before, but return the modified Global State, not just the part regarding the model. This should be done in the scope of org.openbravo.mobile.core module.

Revision	2020-12-22 15:42 by cberner
Description	Currently, actions in mobile.core only support state at the model level(not counting Global Actions), and return a part of the State, the one regarding the model. This is a limitation for other tasks, as such, an extension should be made on those actions to accept and return the modified state, completely, that means, if a Global State is provided, it should apply the same changes as before, but return the modified Global State, not just the part regarding the model. This should be done in the scope of org.openbravo.mobile.core module.