-
Couldn't load subscription status.
- Fork 1
docs: user guide for dashboard version and operation group creation from CSV file #47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
docs: user guide for dashboard version and operation group creation from CSV file #47
Conversation
docs/Portal User Guide.md
Outdated
| - **serviceName** - required column; name of the service (e.g., account-mgmt-core), will be used to identify the relevant package in APIHUB. | ||
| - **serviceVersion** - required column; version of the specified service; package of this version will be included into dashboard. Only one service version must be specified for a specific service, i.e. CSV file must not contain the same service name with different version. If there will be different versions of one service, then only one package version will be included into dashboard. | ||
| - **method** - HTTP method of the REST API operation (e.g., GET, POST, PATCH, DELETE). | ||
| - **path** - endpoint of the API operation (e.g., /accountManagement/v2/billingAccount). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is probably a good idea to describe how path parameters should be specified in the path.
| - **API Type**: Set to rest. | ||
| - **Group Type**: Set to manual. | ||
|
|
||
| ### Report Generation: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can a user see this report?
| If such situation occurs during configuration of dashboard version, the system highlights all conflicted packages. If you do not resolve conflicts manually and publish such dashboard version, the system will automatically resolve conflicts and will skip some link(s) to the conflicted package. After publication of dashboard version, you can see in Packages menu if some link(s) to package version(s) were automatically skipped. | ||
|
|
||
| ## Configure Dashboard and Operation Groups by Importing CSV File | ||
| This functionality allows you to configure both dashboards and operation groups directly by uploading a CSV file. You can use this method to automatically create dashboard version and operation groups based on the data provided in the CSV file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add some description of the use case for which this functionality could be used?
Updated UG with Dashboard Version & Operation Group Creation from CSV.