Modules
...
Grants & Configurations
Master Data
11 min
all the global master data files are uploaded and managed here managing and maintaining a master can be a difficult task users were dependent on how to create and add new masters also, there was no option to reuse an existing master there are 2 ways how masters can be uploaded master management portal upload master's via api master management portal the file containing the master data can be uploaded to the configuration engine docid\ jbnpso4 vmjzos6z mb5r by uploading a csv or xlsx file once this file is uploaded it can be seen on the portal with details like master name, file size, description, the date it was last updated on, etc the uploaded master file(s) can be edited as well as removed according to requirement creating new master data in admin go to the 'master data' section under the 'grants\&config' tab choose the 'create new' option enter the 'master name' and 'description' upload the master file from your device click on 'save' this master data can be used in the conditional dropdown docid\ homwmoumcven8vskcej w element if the realm has no master data file present in it then the master upload will not work for the element uploading masters using apis? there are 2 simple steps to upload masters login upload login master why login? the user who is uploading a master needs to be authorized to upload a master, if there is no authorization the same can lead to unauthorized access and potential harm request curl location request post 'https //go preproduction signzy app/api/backopsusers/login' \\ \ header 'content type application/json' \\ \ data raw '{ "username" " username ", "password" " password ", "realm" " realm name " }' response { "userid" " userid ", "applicationid" " app id ", "id" " auth toke ", "data" { "id" " id ", "name" " name ", "username" " username ", "email" " email ", "mobile" "xxxxxxxxxxxx", "realm" " realm name ", "isdormant" true/false, "applicationid" " appid ", } upload master request curl location request post 'https //backops go preproduction signzy app/api/master buckets' \\ \ header 'content type application/json' \\ \ header 'authorization auth token ' \\ \ data raw '{ "link" "persist link for the master sheet(xls)", "type" "conditionaldropdown", "applicationid" " application id of the realm", "name" " master name " }' response { "message" "we have recieved your request, you can check status for further updates", "status" 200 } 400 422 { "error" { "statuscode" 422, "name" "unprocessableentityerror", "message" "the request body is invalid see error object `details` property for more info ", "code" "validation failed", "details" \[ { "path" "/type", "code" "enum", "message" "must be equal to one of the allowed values", "info" { "allowedvalues" \[ "conditionaldropdown" ] } } ] } } getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at help\@signzy com