Process

Schema

• The same concept of Widgets are used here in Process & Process locker

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

  • It is basically the collection of Processes which will be called based on some rules. Every Locker will have a token which will be shared with Widget.
  • Here we assumed that Widgets & 'Process' 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 processes , he will create a order of his process according to some scenario based on some rules. Like If he have three process P1, P2, P3. then which process will called first and which process 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 Widget.
  • Only published lockers can have token, So no-publish -> no token -> no mapping to Widget.

• resource_token is the token of Resource with which Process is mapped.

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