Comments
I was unable to update the comment above, but here are some thoughts. Solution considerations:Create a parameter to activate change management for direct delivery POs and a separate parameter for intercompany POsProcurement and sourcing > Setup > Procurement and sourcing parameters > Default values and parameters FastTab > Change management for purchase orders grouping > "Activate PO workflow for direct delivery POs"Re-visit the change management logic that currently resides on a vendor record. Ex: I may use a vendor for both direct delivery AND inventory POs, the current logic requires me to bypass PO workflow if I want to use that vendor for direct deliveries. However, if I use that same vendor for a regular PO, that setting will allow the regular PO to bypass workflow. It shouldn't be an all or nothing setting. Regular POs should still go through workflow for that vendor.Procurement and sourcing > Vendors > All vendors > Purchase order defaults FastTab > Change management for Purchase Orders > Allow override of settings per purchase orderNew logic is required here to potentially activate or deactivate for direct delivery orders. This new logic can override the Procurement parameters for the vendor. There's opportunity for improvement, but note that it's common for a client to require approval on ALL types of POs (Direct delivery, standard PO, planned PO, etc..)
A third option should be added - let users select whether credit management should be checked against the main customer account, or the invoice account, or both. "Both" because when we are releasing an order for dispatch, we need to knowIs the invoice / Head Office account paying its bills on time?Does the Head Office need to authorise this franchisee's order before we can release it?Thanks for your consideration!
And it seems to be already there (you just choose add users and then you can add Entra ID security group as well and not just users, but if it doesn't find your security group, close the panel and then re-open it so you can add the security group as well) - didn't find this as known bug in the support portal though?
We need this feature ASAP. I have created a duplicate ticket )i didn't know how to search for tickets)/ Requirement - Linking KA's:A KA creator must be able to link multiple KA's together.E.g. KA1 (paint wall) is linked to KA2 (Fix hole).If a KA creator creates a new version of a KA (major or minor version), AND the original KA was linked to another KA (see requirement 1), then the link between KA1 and KA 2 must not be broken.This is important as once a new version is created, you don't want the link broken.If a CRM user searches an KA using the Knowledge Search functionality, and the CRM user opens KA1 (which is linked to KA2). The CRM user must be able to open KA2 and remain the in "search UI".Currently if you link a KA using a URL, it opens the KA entity and displays information/ fields about the entity that is not relevant to an end user.