Actually, the previous versions of the FMEServerJobSubmitter had a slightly broken logic, where e.g. the _numFeaturesOutput attribute would be exposed even when Wait for jobs to complete = No, which didn't make any sense.
Now, the attributes are dynamic according to how you set the "Wait for job" parameter.
Wait for jobs to complete = No
Wait for jobs to complete = Yes
Based on the fact that your output port is called "Submitted" and not "Succeeded", I'm guessing Wait for jobs to complete = No in your workspace. If you change it around, you should get back the missing attributes.
Actually, the previous versions of the FMEServerJobSubmitter had a slightly broken logic, where e.g. the _numFeaturesOutput attribute would be exposed even when Wait for jobs to complete = No, which didn't make any sense.
Now, the attributes are dynamic according to how you set the "Wait for job" parameter.
Wait for jobs to complete = No
Wait for jobs to complete = Yes
Based on the fact that your output port is called "Submitted" and not "Succeeded", I'm guessing Wait for jobs to complete = No in your workspace. If you change it around, you should get back the missing attributes.
@david_r - thanks for the update - but you don't get the succeeded / failed if
wait for job to complete is a published parameter
@david_r - thanks for the update - but you don't get the succeeded / failed if
wait for job to complete is a published parameter
Ah, that's an interesting edge case, thanks for pointing that out.
It kinda makes sense, however, since parameters aren't resolved before you actually execute the workspace. But still, I can see how that's annoying in this case.