...
The MDM service reads the data from a set of JSON files from a pre-specified location. It can either be an online location (readable JSON files from online) or an offline (JSON files stored in local memory). The JSON files should conform to a prescribed format. The data is stored in a map and tenantID of the file serves as a key.
...
| Expand |
|---|
BasePath:/mdms/v1/[API endpoint] Method POST /_create
Creates or Updates Master Data on github GitHub as JSON files MDMSCreateRequest Request Info + Body ParameterMasterDetail — Details of the master data that is to be created or updated on githubGithub.
MasterDetail Input Field | Description | Mandatory | Data Type |
|---|
tenantId | Unique id for a tenant. | Yes | String | filePath | file-path on git where master data is to be created or updated | Yes | String | masterName | Master Data name to be created or updated | Yes | String | masterData | content to be written on to the Config file | Yes | Object |
MdmsCreateResponse Response Info
Method POST /_search
This method fetches a list of masters for a specified module and tenantId. MDMSCriteriaReq - Request Info + Body ParameterMdmsCriteria — Details of module and master which need to be searched using MDMS.
Input Field | Description | Mandatory | Data Type |
|---|
tenantId | Unique id for a tenant | Yes | String | moduleDetails | module for which master data is required | Yes | Array |
RequestInfo should be used to carry meta-information about the requests to the server as described in the fields below. All DIGIT APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation. Input Field | Description | Mandatory | Data Type |
|---|
apiId | unique API ID | Yes | String | ver | API version - for HTTP based request this will be same as used in path | Yes | String | ts | time in epoch format: int64 | Yes | Long | action | API action to be performed like _create, _update, _search (denoting POST, PUT, GET) or _oauth etc | Yes | String | DID | Device ID from which the API is called | No | String | Key | API key (API key provided to the caller in case of server to server communication) | No | String | msgId | Unique request message id from the caller | Yes | String | requestorId | UserId of the user calling | No | String | authToken | //session/jwt/saml token/oauth token - the usual value that would go into HTTP bearer token | Yes | String |
ResponseInfo should be used to carry metadata information about the response from the server. apiId, ver, and msgId in ResponseInfo should always correspond to the same values in the respective request's RequestInfo. Input Field | Description | Mandatory | Data Type |
|---|
apiId | unique API ID | Yes | String | ver | API version | Yes | String | ts | response time in epoch format: int64 | Yes | Long | resMsgId | unique response message-id (UUID) - will usually be the correlation id from the server | No | String | msgId | message-id of the request | No | String | status | status of request processing - to be enhanced in future to include IN PROGRESS Enum: SUCCESSFUL or FAILED | Yes | String |
|
| View file |
|---|
| name | html-documentation-MDMS.zip |
|---|
|
...