Q:

Is it possible that "ProblemFact" be a shadow variable in Optaplanner

I am new to optaplanner using 7.2.0.  
I have a question on chaining for vehicle route planning.  
Does it mandate that the shadow variable need to have a annotation @planningentity even if its a problem fact? 
Consider an example: 
I have techs and jobs to be assigned for tech.  
For me Tech (problem fact) needs to be assigned for job (planning) i am following VRP as its closely relates to it.  I am following chaining (with both job and tech forms chain with tech being anchor). 
I came across the documentation about shadow variable.  
My question is, can a "ProblemFact" POJO be defined as planning entity and still legal ? 

A:

A shadow variable is a field or a property (=getter/setter).  A problem fact is a class.  A planning entity is also class (that is not a problem fact and visa versa). 
So, I presume the question is: "Can have I have shadow variable with a type that is a problem fact?"  The answer is yes.