INSA
  • Tutorials
  • Documentation
  • Api Documentation
  • Changelog
Show / Hide Table of Contents
  • Scenario Engine
    • What is a scenario Engine?
    • Main Definitions
      • Scenario
      • Transition
      • Sensor
      • Effector
      • Context
    • All Definitions
      • Comment
      • Complex Sequence
      • Context
      • Decision Tree
      • Effector
      • Event
      • Event Context
      • External Context
      • External Scenario
      • Function
      • Node
      • Net
      • Petri-Net
      • Place
      • Safe Petri-Net
      • Scenario
      • Scenario Context
      • Sensor
      • Sequence
      • State
      • State Machine
      • Token
      • Token Assign
      • Token Merge
      • Token Split
      • Transition
    • How to deal with asynchronous events?
  • Relation Engine
    • What is a relation Engine?
  • Scenario with Relation

Token

A token, or sequence context is a context that represents data/variables that will flow through the scenario. Tokens are useful to handle variability and represent execution context when a scenario is running.

Tokens are initialized in initial sequences and can be modified, splitted or merged when entering or exiting transitions and sub-sequences using various functions.

A transition can have more than one token as input (coming from the upstream sequences).

A transition can have more than one token as output (going to the downstream sequences).

A fusion policy, called Token Merge describes the way the transition merges the upstream tokens.

A distribution policy, called Token Assign describes the tokens that are created for each downstream sequence.

INSA     IRISA     Inria     Ouest Valorisation Back to top