AFF for Lock Objects (ENQU)

[anne-hobbs]

No description provided.

[cla-assistant]

All committers have signed the CLA.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[schneidermic0]

Thanks @anne-hobbs for your contribution. 👍

In a first iteration I went only over the example file and added some suggestions/ideas/questions there.

[uenal-akkaya]

The lock mode in primaryTable -> lockMode can also be empty, so that nothing is selected. This should be also reflected in the AFF.

This does not apply to secondaryTables->lockMode.
Edit: The empty value can also be specified for secondaryTables->lockMode

[anne-hobbs]

The lock mode in primaryTable -> lockMode can also be empty, so that nothing is selected. This should be also reflected in the AFF.

This does not apply to secondaryTables->lockMode.

ENQU can be active with initial lock mode -> how do we reflect this in AFF?
Secondary tables can also have an initial lock mode.

[anne-hobbs]

Question regarding JSON Generation - left is the build result from here, right is the result from our Dev System. Something is running differently as I think the ENUM values for lock mode should be part of the JSON Schema, no?

[huber-nicolas]

Question regarding JSON Generation - left is the build result from here, right is the result from our Dev System. Something is running differently as I think the ENUM values for lock mode should be part of the JSON Schema, no?

the annotation "! $values { @link zah_aff_enqu_v1.data:co_lock_modes } is not correct.
Here zah_aff_enqu_v1 is not known

Yes, the enums should be in the json schema.

[uenal-akkaya]

@anne-hobbs We need to change the zero to big letter o for the lock mode text of 'R':
'R' Promote optimistic lock; transform from '0' to 'E'
'R' Promote optimistic lock; transform from 'O' to 'E'

The question regarding knowing what 'X' or 'R' or else is the same issue as in SAP GUI or ADT as before. So no need of change here.