Creating an OpenEdge ABL Service using 11.7.0 environment - Forum - Kendo UI Builder - Progress Community

Creating an OpenEdge ABL Service using 11.7.0 environment

 Forum

Creating an OpenEdge ABL Service using 11.7.0 environment

  • Hi All,

    In order to develop a Kendo UI Builder web app or build a mobile app using Telerik Platform or use a third party web/mobile framework to communicate with OpenEdge data via JSDO, we need to have an OpenEdge backend service which will facilitate us bringing data from OpenEdge database via REST or Web transports.

    The process of creating an ABL Service in Progress Developer Studio has been enhanced in OpenEdge 11.7.0. This document provides list of different steps involved in creating an ABL service using OpenEdge 11.7.0 environment.

    Please find document in following location:

    https://community.progress.com/community_groups/openedge_kendo_ui_builder/m/documents/3363

    Thanks and Regards,

    Anil Kumar.

  • What would be helpful to add to this document is a list of available annotations that can be added to a resource operation within a service (method-level), which alters behavior in KUIB. Notably, how to define a semantic type and a foreign key relation. These are not easily found in the documentation, but this document would be a good place for such related materials.

  • Hello Dustin,

    Thank you for your feedback.

    The "Kendo UI Builder FAQ" in the wiki section now has a reference to the foreign key annotation:

    community.progress.com/.../2926.kendo-ui-builder-faq

    Perhaps, we could add another item there for semantic type and the other available annotations in general.

    Thank you and regards,

    Edsel

  • Here is additional information.

    The following section in the documentation provides information on the annotations:

    documentation.progress.com/.../index.html

    Annotations:

    @openapi.openedge.entity.foreignkey

    @openapi.openedge.entity.primarykey

    @openapi.openedge.entity.required

    @openapi.openedge.entity.property ( table reference element in the catalog )

    @openapi.openedge.entity.field.property ( field element in the catalog)

    @openapi.openedge.method.property ( method element in the catalog)

    Notes:

    - The annotations are reflected in the catalog.

    - The semanticType uses the field property annotation.

    - The JFP support uses the method property.

    I hope this helps.

  • Thank you, Edsel. That is tremendously useful to have side-by-side with the attached document.