Widgets

Schema

• Concept of Widget locker is introduced because we needs to tell VRT what Widget it can load on its initiation.

  • Here we assumed that VRT & Widgets are on different servers so they have no direct relation between them so we can't map them using any Fk,M2M relations.
  • So admin will first create its widgets , he will create a order of his widgets according to some scenario based on some rules. Like If he have three widgets W1, W2, W3. then which widgets will called first and which widgets will be called on basis of any rule etc etc.
  • So though we will store his this entire scenario in a locker and tell him this is what you have created and if you are sure this is what you want then publish this.
  • Once published, locker cannot be updated or changed.
  • After publish we will assign every locker a token and this token will be mapped with VRT.
  • Only published lockers can have token, So no-publish -> no token -> no mapping to VRT.

• token field will store the token of Process Locker it supposed to load when it will be initiated. So its not Widget token but Process Locker token.

• Widget will also log its own life cycle using logging model.