- 
    Type:
Feature Request
 - 
    Resolution: Unresolved
 - 
    Priority:
L3 - Default
 - 
    None
 - 
    Affects Version/s: None
 - 
    Component/s: engine
 - 
    None
 
User Story (Required on creation):
I want to be informed when a process instance has been started and initial variables have been set.
Functional Requirements (Required before implementation):
An event is published after initial variables have been set on a new process instance
Technical Requirements (Required before implementation):
- Define a new event entity that reflects the desired state, e.g., HistoricProcessInstanceInitVariablesSetEvent.
 - Fire the new event after the variables are set on a new process instance. The variables are set in PvmExecutionImpl line 276 .
 
Limitations of Scope (Optional):
Hints (optional):
- The desired behavior could be achieved with the HistoricProcessInstanceStartEvent until 7.12
 - With 
CAM-10978, the following was changed in 7.13:- The HistoricProcessInstanceStartEvent is now fired first.
 - The variables are set (see: PvmExecutionImpl line 276 ).
 - The HistoricVariableUpdateEvent instances are fired.
 
 CAM-10978leads to the execution having no variables when the HistoricProcessInstanceStartEvent is processed. This refactoring was done to ensure correct ordering of the Historic events, i.e. a HistoricProcessInstanceStartEvent is fired before any HistoricVariableUpdateEventEntity instances are fired.