I think its ok if you follow the bpm.job-executor that already exists, something this way:
bpm:
job-executor:
acquire-doing- row-lock: true
Maybe “row lock” says more about what we do (we lock the row on acquisition).
If we only “skip locked” but never lock the row, it wouldnt do anything.
If the prop name talks about what we want to do, its easier to implement it in another way if some databases doesnt support or work this same way with the skip locked