Hello all,

The customer I am working with will be using project roles as part of their purchase authorisation workflow. 

As part of our testing, we have purposefully not assigned or created project roles to understand the impacts of the authorisations if we have missing basic data. 

It is a concern that as a result of not having project roles/project roles assigned, the purchase order correcty identifies the authorisation rule ID that should be triggered, however the system is not able to pull through the authorisation steps. This means that we are then allowed to release the purchase order as the authorisation rule does not get triggered. 

Our expectations would be that if there is missing basic data, but the correct authorisation rule ID is being identidied on the PO, that the system would error upon the release of the PO.

We had also attempted creating a ‘Catch All’ authorisation rule (all parameters switched on) to see if the system would instead identify this as the rule to be triggered instead of the project authorisation but this was not the case.

Has anyone who has implemented or is in the process of implementing project roles as part of their purchase order authorisations faced similiar challenges? And if so, is this a bug?