The following image shows you the architecture of the Jump interface for FLOCs.
-
Rows from 20 through 28 - They define the Token URL and all necessary parameters.
-
Rows from 29 through 32 - They define all API calls and Web Client URLs for the Jump interface for FLOCs.
-
Row 29 - It defines an API call to find a corresponding Tag for a selected FLOC. You can view the information in SDx by:
-
Searching for a Tag with the same name as FLOC
-
Searching for the SAP ID of a FLOC stub object (when the Tag and FLOC names are different)
-
-
Row 32 - It defines a call to expand documents from Tag to be listed in SAP:
-
You can expand the documents by giving different inputs, such as relationships and edges, and they can be separated by commas. For example, if the value is $top = 1000, it allows you to expand a maximum of 1000 documents in a single view.
-
-
Rows 30 and 31 - They define Web Client URLs to view documents and document InfoMap.
-
A Web Client URL for Tag InfoMap is defined in the code, not in the parameter table.
-
All API calls must be tested on Postman before sending the Excel file to the SAP team.
-
For more information on the usage of the variables, see System variables.
