Custom API Usage

custom api usage is typically for use when only the base gimmal link enterprise api product is installed usage of the gimmal link enterprise (s)earch (c)reate (r)ead (u)pdate (d)elete api platform within sap is outlined in detail the gimmal link enterprise developer guide when using the scrud api set in a custom scenario and you have docmanager installed on your system, this section is may not relevant as you are encouraged to leverage docmanager rules to control api usage in the scenario you have only the base cms api installed, you may choose to utilized the creation of custom api rules to house relevant config, especially the mandatory input parameters for the scrud api set such as cms profile, cms use tag, repository id, location, etc, allowing you to leverage a unique "label" you are responsible for what you use the available fields for as well the retrieval of them, as the scrud api set will only log itself in the gimmal link enterprise api gateway by default in terms of functionality to create a custom api rule when docmanager is not installed, enter transaction /dflow/sys and choose the menu path configure >api rules >custom please also consult the gimmal link enterprise developer guide for more information