The inventory has a limited list of characters which are used in part codes. For example: while 0 is a valid part code character, neither o nor O are.
Currently the tooling outright rejects bad characters, however it should be fairly easy to detect the presence of these characters and provide a clearer message to the user.
Follow-on steps from this might be:
also checking whether a part code exists with the "corrected" name
just redirecting the query/operation onwards with the "corrected" name
The latter in particularly needs deeper consideration as it trains users that these invalid characters are in fact valid, which would likely lead to them not writing part codes clearly in their proper form and/or not being aware of the intentionally limited alphabet at all. Both of these could cause considerable confusion when the tooling refers to one spelling but users are expecting another.
This task therefore is explicitly only about improving the messaging to users and not about changing the current behaviour.
The inventory has a limited list of characters which are used in part codes. For example: while
0is a valid part code character, neitheronorOare. Currently the tooling outright rejects bad characters, however it should be fairly easy to detect the presence of these characters and provide a clearer message to the user.Follow-on steps from this might be:
The latter in particularly needs deeper consideration as it trains users that these invalid characters are in fact valid, which would likely lead to them not writing part codes clearly in their proper form and/or not being aware of the intentionally limited alphabet at all. Both of these could cause considerable confusion when the tooling refers to one spelling but users are expecting another.
This task therefore is explicitly only about improving the messaging to users and not about changing the current behaviour.