-
Notifications
You must be signed in to change notification settings - Fork 9k
[IMP] Purchase: Update RFQ with dependency warnings and new images #12682
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
Conversation
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.
Looks great @slinkous !
Approved with minor nitpicks (:
content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst
Outdated
Show resolved
Hide resolved
content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst
Outdated
Show resolved
Hide resolved
content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst
Outdated
Show resolved
Hide resolved
content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst
Outdated
Show resolved
Hide resolved
content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst
Outdated
Show resolved
Hide resolved
content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst
Outdated
Show resolved
Hide resolved
content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst
Outdated
Show resolved
Hide resolved
92a8d6d
to
12cb8eb
Compare
12cb8eb
to
e8a1d09
Compare
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.
Hi @slinkous
Approving with some comments to consider.
When you're ready can pass to @samueljlieber for merge, thank you!
To auto-populate product information and prices on an |RFQ|, configure products by going to | ||
:menuselection:`Purchase app --> Products --> Products`. Select an existing product, or create a | ||
new one by selecting :guilabel:`New`. Doing so opens the product form, where various sales and | ||
purchasing data can be configured. | ||
:menuselection:`Purchase app --> Products --> Products`. Select an existing product, or create a new | ||
one by selecting :guilabel:`New`. Doing so opens the product form, where sales and purchasing data | ||
can be configured. |
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.
If we're going to touch this section up then I think we can go further.
We can:
- be more concise by removing unnecessary words and instructions
- remove passive language in favor of the active voice
- add time order language to imply an ordered sequence of steps
- be more explicit in cause/effect actions (i.e. if/then/else statements, do this and then this happens, etc.)
- be more specific with certain words and instructions (we don't select the New button because it's not presented as a choice as though it were in a menu with other list items, we click it).
To auto-populate product information and prices on an |RFQ|, configure products by going to | |
:menuselection:`Purchase app --> Products --> Products`. Select an existing product, or create a | |
new one by selecting :guilabel:`New`. Doing so opens the product form, where various sales and | |
purchasing data can be configured. | |
:menuselection:`Purchase app --> Products --> Products`. Select an existing product, or create a new | |
one by selecting :guilabel:`New`. Doing so opens the product form, where sales and purchasing data | |
can be configured. | |
To auto-populate product information and prices on an |RFQ|, first configure the product(s) by going | |
to :menuselection:`Purchase app --> Products --> Products`. In the list, find the existing product, | |
or create a new one by clicking the :guilabel:`New` button. Then, on the product's form, fill in the | |
necessary sales and purchasing data, so it loads across document line items automatically. |
information auto-populate on an |RFQ| each time the product is listed. | ||
In the :guilabel:`Purchase` tab of the product form, click :guilabel:`Add a line` to input the | ||
vendor and their price, to have this information auto-populate on an |RFQ| each time the product is | ||
listed. |
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.
Suggest to pluralize "vendor" to "vendors" and then explain how the order in the list matters (the vendor at the top of the list is preferred across other operations like reordering rules)
To enable or disable columns, click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` | ||
icon on the right side of the header row to reveal a drop-down menu of additional columns that can | ||
be added (or removed) from the :guilabel:`Purchase` tab. |
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.
Essentials content, can remove
It's better to more deeply explain the what default columns mean and how to fill them in correctly.
To enable or disable columns, click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` | |
icon on the right side of the header row to reveal a drop-down menu of additional columns that can | |
be added (or removed) from the :guilabel:`Purchase` tab. |
going to :menuselection:`Purchase app --> Configuration --> Vendor Pricelists`. Click | ||
:guilabel:`New` in the top-left corner. In the :guilabel:`Vendor` section of the pricelist form | ||
that appears, add the product information as it pertains to the vendor. | ||
Alternatively, prices and delivery lead times for existing products can be added by going to |
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.
The explicit "bulk" part here is a useful tip, I don't see the need to remove it?
In addition to view options, the :guilabel:`Requests for Quotation` dashboard provides | ||
:guilabel:`Filters` and :guilabel:`Group By` options, accessible via the search bar drop-down menu. |
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.
essentials content can remove
The :guilabel:`Blanket Order` field refers to long-term purchase agreements on recurring orders with | ||
set pricing. To view and configure blanket orders, head to :menuselection:`Purchase app --> Orders | ||
--> Purchase agreements`. | ||
With the :doc:`Purchase Agreements feature <blanket_orders>` activated, the :guilabel:`Blanket |
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.
I like that we're talking about blanket orders and dropshipping, but at this location in the content, it seems a bit premature since we're simply just trying to create an RFQ? We don't need any of these features enabled in order to create an RFQ...
@samueljlieber branch is ready to merge. Per discussion with Zac, we'll make his suggested changes in a follow-up PR to keep this PR focused on its original goal. |
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.
content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst
Outdated
Show resolved
Hide resolved
Apply suggestions from code review Co-authored-by: Felicia Kuan <[email protected]> fix edits ddfsdf . Update content/applications/inventory_and_mrp/purchase/manage_deals/rfq.rst Co-authored-by: Sam Lieber (sali) <[email protected]>
de0bd81
to
14d0184
Compare
@robodoo r+ |
1 similar comment
@robodoo r+ |
This PR is already reviewed, reviewing it again is useless. |
No description provided.