[ https://issues.jboss.org/browse/WFLY-3724?page=com.atlassian.jira.plugin.... ] Enrique González Martínez commented on WFLY-3724: ------------------------------------------------- I don't think this behavior can be considered a bug. Partition properties are available through xml substitution and they are in step scope. Extracted from the JavaDoc jsr 352 -> 10.9.7 JobOperator::getParameters(execID) "Returns job parameters for a specified job instance. These are the key/value pairs specified when the instance was originally created by the start method." That means the properties passed during creation: JobOperator::start(jobXMLName, jobParameters). It does not mention anything about partition plan properties available to the job parameters or job properties (through the JobContext). The specification states that: jsr352 -> 10.9.4 PartitionPlan PartitionPlan::getPartitionProperties() "Gets array of Partition Properties objects for Partitions. These can be used in Job XML substitution using substitution expressions with the syntax: #{partitionPlan['propertyName']} Each element of the Properties array returned can be used to resolving substitutions for a single partition. In the typical use case, each Properties element will have a similar set of property names, with a substitution potentially resolving to the corresponding value for each partition." jsr 352 -> 8.8.1.4 partitionPlan Substitution Operator "The partitionPlan substitution operator resolves to the value of the partition plan property with the specified target name from the PartitionPlan returned by the PartitionMapper Partition plan properties are in scope only for the step to which the partition plan is defined. The partitionPlan operator is resolved separately for each partition before the partition execution begins. " -- This message was sent by Atlassian JIRA (v6.3.1#6329)