With this latest release, we have introduced the ability to name a pipeline to simplify identification and retrieval, along with some minor optimizations.
New Feature:
Users can now name a vendor master pipeline and modify the pipeline name directly from the API and/or within the SDP User Console UI, improving the identification and retrieval of specific pipelines.
Naming a Pipeline and Modifying a Pipeline Name within the SDP User Console UI
If a user has uploaded a single file on the File Uploader page, the new Pipeline Name text box will appear. Pipeline names are limited to 50 characters and should help the user to clearly identify the contents of that pipeline. This is an optional field.
Users can sort/filter by Pipeline Name on the dashboard.
The Pipeline Name can be modified at any time using the pencil icon on the Pipeline Overview page.
Naming a Pipeline and Modifying a Pipeline Via API
As called out in the updated API documentation, users may choose to add an optional pipeline_name when submitting an inputVmData request
The pipeline name can be modified via the SDP User Console UI or by using the new modifyPipelineName mutation.
Minor Optimizations:
Normalized Attribute Naming Conventions and Formatting
Attribute naming conventions have been normalized across API operations. This includes:
- CAGE Code = cage_code
- DUNS = duns_number
- Taxpayer ID = taxpayer_id
- SAM UEI = sam_uei
- addressLine = street_address
Query and Mutation input and output are now consistently using snake_case.
The downloadable vendor master template on the File Uploader page in the SDP User Console has been updated to reflect these modifications, as has the API documentation.