Hi all, Today we had an architecture meeting regarding the traveling asset permission use case. People who attended the meeting are - Store (Nuwan, Ruchira, Manuranga, Sameera), AppFactory (Dimuth), Greg (Senaka), Mobile (Dulitha), API Manager (NuwanD), Paul.
*The problem (brief description of the problem with the use case) -* When an asset is inserted by a developer from the publisher the developer will have CRUD privilege to the inserted asset. When the application moves to the review state except for view operation all the other permissions are transferred to the reviewer. *Points discussed in the meeting* - Senaka stated that the current method used in products are copying the asset and performing the permission that way - Proposed model involved in using SCXML language to configure the asset permissions and life cycles state changes. - Three executors will be written to support this. First executor is an executor that will do the permission changes (it will be written by the Store team and will be later contributed to the Greg code base) - Other two executors are - to execute a javascript function, and invoke an endpoint (WebService, REST call) Another meeting with Paul was proposed for his next visit regarding the role of an RXT and whether we should mix UI configuration in it. If I missed anything please add to this thread. Thanks. -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email [email protected] <[email protected]>* * ~Mobile +94712112165* * ~Website dulithawijewantha.com * * ~Blog blog.dulithawijewantha.com<http://dulichan.github.io/chan/> * * ~Twitter @dulitharw <https://twitter.com/dulitharw>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
