This file contains several settings that determine some details about validation of XPDL files:
AllowUndefinedStart - if set to false, TWE will require that process and activity set graphs must have at least one starting activity. Otherwise, you will be able to create graphs without starting points, and TWE will not complain. You may have noticed that TWE also considers activity with only circular incoming transition to be the starting point of the graph, so this regards only to graph structures similar to the one bellow:
AllowUndefinedEnd - if set to false, TWE will require that process and activity set graphs must have at least one ending activity. Otherwise, you will be able to create graphs without ending points, and TWE will not complain. You may have noticed that TWE also considers activity with only circular outgoing transition to be the ending point of the graph, so this regards only to graph structures similar to the one bellow:
ValidateSubFlowReferences - if set to true, TWE will consider an error if SubFlow activity does not reference to the valid process from the XPDL or one of the XPDLs referenced through external package concept.
If you know that you will create XPDLs where you'll use SubFlow activities to reference a remote process definition, you should set this property to false, in order not to have validation errors reported.
ValidatePerformerExpressions - if set to true, TWE will consider a warning if activity's performer is not a reference to an existing Participant and it's expression does not look like valid performer expression.
ValidateActualParameterExpressions - if set to true, TWE will consider a warning if actual parameter is not a reference to an existing variable (DataField or FormalParameter) and it's expression does not look like valid actual parameter expression.
ValidateConditionExpressions - if set to true, TWE will consider a warning if transition's condition does not look like valid expression.
ValidateDeadlineExpressions - if set to true, TWE will consider a warning if deadline condition does not look like valid expression.
ValidateUnusedVariables - if set to true, TWE will consider a warning if XPDL variable (DataField or WorkflowProcess's FormalParameter) are not used anywhere (as actual parameter or inside expression).
ValidateConditionByType - if set to true, TWE will generate a warning in following cases:
Condition type is not defined, and there is condition expression defined
Condition type is 'DEFAULT_EXCEPTION' and there is condition expression defined
Condition type is 'OTHERWISE' and there is condition expression defined
Condition type is 'EXCEPTION' and there is no condition expression defined
Condition type is 'CONDITION' and there is no condition expression defined