Scribd
Upload
93 views2 pages

The Ultimate C - C4H450 - 04 - SAP Certified Integration Associate - SAP Cloud For Customer

C_C4H450_04 - SAP Certified Integration Associate – SAP Cloud for Customer Certification Exam Credential. Automatically Drawing Primary Key Values for Managed Business Objects The managed runtime framework can now automatically generate key values in scenarios with UUID keys if managed numbering is defined in the behavior definition. Syntax for defining managed numbering in the behavior definition: New Options for Action and Function Results The BO runtime framework now supports results for act

Uploaded by

Stefan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
93 views2 pages

The Ultimate C - C4H450 - 04 - SAP Certified Integration Associate - SAP Cloud For Customer

C_C4H450_04 - SAP Certified Integration Associate – SAP Cloud for Customer Certification Exam Credential. Automatically Drawing Primary Key Values for Managed Business Objects The managed runtime framework can now automatically generate key values in scenarios with UUID keys if managed numbering is defined in the behavior definition. Syntax for defining managed numbering in the behavior definition: New Options for Action and Function Results The BO runtime framework now supports results for act

Uploaded by

Stefan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
You are on page 1/ 2

The Ultimate C_C4H450_04 - SAP Certified

Integration Associate – SAP Cloud for Customer

C_C4H450_04 - SAP Certified Integration Associate – SAP Cloud for Customer Certification
Exam Credential. Automatically Drawing Primary Key Values for Managed Business Objects
The managed runtime framework can now automatically generate key values in scenarios with UUID
keys if managed numbering is defined in the behavior definition.

Syntax for defining managed numbering in the behavior definition:


New Options for Action and Function Results
The BO runtime framework now supports results for actions and functions other than $self. The results
can be entities of the same BO the action is defined for, entities of other BOs, or result structures. To
differentiate between result entities and result structures the syntax element entity has been introduced.

In addition, you can now create actions, for which the action consumer can decide whether the result shall
be returned completely or only parts of it, for example the keys only. Such an action must be marked with
the keyword selective in the behavior definition.

define behavior for CDSEntity


Action with result entity
Action with result structure
action ActionName result [cardinality] OutputStructure
Action with selective result
action ActionName result selective [cardinality] entity OutputEntity
For more information, see Actions.

Reporting Messages in ADJUST_NUMBERS and SAVE


The implicit returning parameter REPORTED is now available for the methods adjust_numbers and save.
By filling this parameter you can report information or success messages after the point of no return in the
save sequence.

For more information, see ADJUST_NUMBERS and SAVE.


Documenting Behavior Definitions
Now you can document behavior definitions in the Knowledge Transfer Document editor.

From the Project Explorer, select the behavior definition you want to document. Use the context menu to
create a knowledge transfer document.
Defining the Service Namespace for OData Services
You can now define the OData service namespace in service definitions with the annotation
@OData.schema.name.

For more information, see OData Annotations.

Filling the Result Parameter for Actions


A runtime check is introduced to enforce the proper assignment of result values in action implementations
when result parameters are declared in the corresponding action definition. Whereas actions returned the
input entity if the result parameter was not filled in the action implementation before 1911, they now
return the value of the result parameter as specified in the action definition and exactly according to its
implementation.

To avoid that a Fiori UI shows initial values, if nothing is returned, you must fill the result parameter for
all actions.

For more information, see Developing Actions and Implementing the SET_STATUS_BOOKED Action.

Navigating More Than One Step in OData Requests


It is now possible to navigate to associated entities using more than one navigation for both, V2 and V4
services.
Example
To request the booking supplements for the booking entity with BookingID 5 of the travel with TravelID
1, use the following syntax.

<service_URL>/Travel('1')/to_Booking('5')/to_BookingSupplement
You can link an unlimited number of entities in one OData request.

You might also like