PDM is a document control system. if you are using its revisioning system(s), you can only revision/version things at the file level, not down to the individual configuration(s). i.e. the entire file gets the %nextrevision%.
Then why would each configuration have its own revision in the first place? Here is one assembly that has 7 configurations. Each of them has their own data card and a revision. They are just all linked to the same letter. I do not see why they would have their own data cards if they were not able to be different from one another. They have different information in the other fields too.
there are several bits of information that all get loosely referred to as "revision".
- configuration specific custom properties
- file level custom properties
- PDM variables
- PDM file revision
through variable mappings and transition actions these are generally tied together. but #4 is limited to 1 per file. so even if your transition incremented the revision and you mapped it to just one configuration specific custom property, the transition would only ever show a rev change to that one configuration - even though PDM would be assigning a new rev to the whole file with each transition action.