| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 43fc03b0-b37f-33f0-b945-0936bf447179 |
|---|
| key | PMP-79546 |
|---|
|
...
Background and strategic fit
The purpose of this Integration is to pull the Location information. This data can be further used while hitting other APIs)
(as request parameter). This document provides information on how the the end Users can consume the API
Assumptions
- ProcessMAP system User permissions would not be considered while exposing the data
- Data will be shown in Readable JSON format
- User accessing this endpoint through a valid Token & ConsumerId, provided by ProcessMAP, will have access to complete data
- The "Level" property in the output JSON will have the levels and sublevels separated by a "/" till the last level where the location belongs to.
- If the user does not pass any Level Name as the parameter then all locations of the system will be displayed .
- If the user passes any level name as the parameter, then all locations under that level will be displayed.
- If any level available in multiple categories and mapped to a single location, display anyone mapping enterprise heiarchy of the location.
...
Location Field List and Mapping
| Product Field Name | Description | Field Type and Size |
|---|
| Location Name |
Represents location name | NVARCHAR(50)Represents location codeNVARCHAR(50) | Represents Database LocationIdCity | Represents Location Represents Location Address | | Country |
|
|
| State/Province |
|
|
| City |
State | Represents Location State | Country | Represents Location Country | Zip | Represents Location Zip | Level | Represents the Level Hierarchy in flat format[when rootname is passed in parameter]
|
|
| County |
|
|
| Postal/Zip Code |
|
|
| Location Status |
|
|
| Business Type |
|
|
| Operation Type |
|
|
| Industry Description |
|
|
| Comments |
|
|
Errors/Validation Messages
...