Common.DraftXxx: sync with RAP implementation

[ralfhandl]

1. DiscardAction is no longer experimental
2. AdditionalNewActions is no longer experimental
3. EditAction has a new optional parameter „PreserveChanges“ (Edm.Boolean)

• The action can provide an optional parameter “PreserveChanges” of type “Edm.Boolean” that may be used to ensure outdated drafts of another user are not overwritten (see below).

4. NewAction and AdditionalNewActions have an optional parameter “ResultIsActiveEntity” (Edm.Boolean)

• The action can provide an optional parameter "ResultIsActiveEntity" of type Edm.Boolean to indicate whether via the action a draft or an active instance should be created. Default is “false”, i.e. the creation of a draft instance.

5. DraftNode: PreparationAction is deprecated

• @RaizoC wonders if the complete annotation “DraftNode” is deprecated as it is always empty (in the meantime). That a node is activated via and belongs to the draft root is indicated via a separate annotation DraftActivationVia. @MarcelWaechter: can you confirm the annotation “DraftNode” is NOT used any more in FE V4 (and V2)?

6. ShareAction has a new parameter “ShareAll” (Edm.Boolean)

[RaizoC]

To be consistent may the following sentence should also be changed: "New drafts may also be created by POSTing an empty entity without any properties to the entity set."

"New drafts may also be created by POSTing an entity with property IsActiveEntity=false (default) to the entity set."

In fact also during the creation of a draft root already properties may be set or even have to be set if the "requiredProperties" annotation is used. Therefore the statement with an "empty entity" is not correct.

[HeikoTheissen]

Purely typographical review

[RaizoC]

If we do not deprecate the complete "DraftNode" (which is only used as tag and thus redundant to "DraftActivationVia", we should at least remove or deprecate the ValidationFunction inside that was never used.

Typographically OK

[ralfhandl]

we should at least remove or deprecate the ValidationFunction

That is already deprecated:

odata-vocabularies/vocabularies/Common.xml

Lines 1136 to 1146 in c941c4e

	<Property Name="ValidationFunction" Type="Common.QualifiedName">
	<Annotation Term="Core.Revisions">
	<Collection>
	<Record>
	<PropertyValue Property="Kind" EnumMember="Core.RevisionKind/Deprecated" />
	<PropertyValue Property="Description" String="Separate validation without side-effects is not useful" />
	</Record>
	</Collection>
	</Annotation>
	<Annotation Term="Core.Description" String="Function that validates whether a draft document is ready for activation" />
	</Property>

@RaizoC Should we deprecate the whole DraftNode now?

[ralfhandl]

@RaizoC Should we deprecate the whole DraftNode now?

Deprecated the term

[RaizoC]

@RaizoC Should we deprecate the whole DraftNode now?

Deprecated the term

I would deprecate it as it only adds redundancy, but we @MarcelWaechter should confirm.