[docs] Supplier docs (concept, reference, flows) - #71
Draft
github-actions[bot] wants to merge 1 commit into
Draft
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Deploying coredocs with
|
| Latest commit: |
797b7c8
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2ac259ea.coredocs.pages.dev |
| Branch Preview URL: | https://docs-supplier-org-5ec6af7e47.coredocs.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ezhuthachan
Closes the request in #64:
/document Access & Governance/Supplier.No
<doc-types>was given, so all three layers are written.Files added
Authored in
version-3.0, mirrored byte-identical toversion-3.1:concepts/access-governance/supplier.mdxreferences/access-governance/supplier.mdxflows/access-governance/add-a-supplier.mdxflows/access-governance/update-a-supplier.mdxflows/access-governance/_category_.json(new flow domain folder)Changed:
versioned_sidebars/version-3.0-sidebars.jsonandversioned_sidebars/version-3.1-sidebars.json— the flow sidebar is a manual list, so an Access & Governance category with the two new flow ids was appended. No existing document was rewritten.Two flows were written because the slug was a resource, not a task: the frontend supplier admin screen supports exactly create and edit.
Sources traced
code/care:care/emr/resources/organization/spec.py—OrganizationTypeChoices.product_supplier, the base/write/update/read specs.care/emr/models/organization.py—OrganizationCommonBasefields and caches.care/emr/api/viewsets/organization.py—authorize_create/authorize_update/authorize_destroy, and the OTP queryset limit.care/security/authorization/organization.py—can_create_organization_obj,can_manage_organization_obj, andget_accessible_organizations(which makes every supplier readable by any user).care/security/permissions/organization.py— permission display names and role lists.care/emr/models/supply_request.py,care/emr/models/supply_delivery.py, and the two order write specs undercare/emr/resources/inventory/— thesupplierFK and its type validation.code/care_fe:src/components/ui/sidebar/admin-nav.tsx— Admin → Organizations → Suppliers.src/Routers/routes/adminRoutes.tsx,src/pages/Admin/organizations/AdminOrganizationList.tsx— the flat supplier list, search box, and mobile selector.src/pages/Admin/organizations/components/AdminOrganizationFormSheet.tsx— the Name and Description fields and the button labels.public/locale/en.json— every UI label used in the flows.Left out (not verifiable)
src/config/keyboardShortcuts.jsondefines none for the supplier screens.can_manage_organization, but the supplier detail panel inAdminOrganizationList.tsxrenders only the edit sheet, so there is no verified user path.Validation
npm run build—[SUCCESS]forenandml, exit code 0.