Official Content

This article describes all the necessary steps to declare, inside an API object called APICustomers, a GetByKey service that returns all the information of a certain customer.

Consider a Knowledge Base containing:

1) A Customer Transaction object:


Note: The Customer Transaction has Automatic data population.

2) An API object called APICustomers. In its Service Source tab, it already contains a declared service that maps an external name exposed as a service (ListCustomers) with the internal implementation in the KB (the CustomerList Data Provider):


Now, suppose you need to define another service (method) named GetByKey, as part of the APICustomers object, to bring the information of a particular Customer received as a parameter (the customer identifier). 

To do so, first set the Customer Transaction as a Business Component.

After that, create a new Procedure object and name it CustomerGetByKey. 

In the Procedure Rules section, define a Parm rule as follows:

Parm(in:&CustomerId, out:&Customer);

In the Procedure Source, define the following code:

If &Customer.Fail()
    &Customer.CustomerName= "Invalid data"
  • &CustomerId is a variable based on the CustomerId attribute.
  • &Customer is a variable based on the Customer Business Component data type.

Next, go to the APICustomers API object, and inside its Service Source declare the new method (GetByKey) under the ListCustomers method:

    GetByKey(in:&CustomerId, out:&Customer, out:&Messages)=> CustomerGetByKey(&CustomerId, &Customer);

The GetByKey method uses input and output parameters represented by variables, so these variables must also be defined in the API object Variables section.

Note that in the service declaration, the &Messages variable is an out parameter and it is not mentioned in the implementation. This is supported. This kind of variable can be assigned in the AFTER event of the service.

The next step is to define the Events in the Events section of the APICustomers API object.

For each defined method, such as GetByKey, you can define their respective Events: Before and After.

Event GetByKey.Before
    If &CustomerId < 0

Event GetByKey.After
    If &Customer.CustomerId= 0
        &Message.Type= MessageTypes.Error
        &Message.Description= format("There was an error loading Customer Information &1.",&CustomerId)
        &RestCode= 404

Remember that &RestCode is a predefined variable that you need to set to customize the returned HTTP Status Code.

The order of events executed when calling the GetByKey method is as follows:

  1. Event 'Before'
  2. Event 'GetByKey.Before'
  3. GetByKey method (CustomerGetByKey Procedure internally)
  4. Event 'GetByKey.After'
  5. Event 'After' 

Below you can see all the steps being executed:


Last update: April 2024 | © GeneXus. All rights reserved. GeneXus Powered by Globant