Traceability report: separate entry for authorization
Currently, the authorization of the Traceability report is linked to the Organization structure.
I would like to suggest to create a separate authorization for the Traceability report under: Administration – System Initialization – Authorizations – General Authorizations – Users/Groups – User Authorization - Produmex
Patrick Reynaert
-
Official comment
Hi everyone,
I wanted to take a moment to address this thread and provide some clarity.
To ensure transparency, I’d like to reiterate that the only official source to verify whether a feature request is on our roadmap is our https://boyum-it.notion.site/Logistics-175be94de47e8100afebfeaebd37ab0e Logistics roadmap website. When we publish features there, we make a commitment to delivering them. However, we cannot guarantee that every request will be included, even if it's a great idea, as prioritization is based on multiple factors, including:
- Product strategy and vision
- Overall priority compared to other roadmap items
- Resource availability
- Existing workarounds that may already address the need
That said, I personally agree that this feature request was a valuable one. I also imagine that some of you may have created custom reports to mitigate the issue.
Coinciding with Francine’s last comment, I’ve been working to allocate time for simpler enhancements through initiatives like reactivating the Quality of Life program. This initiative specifically aims to address the most upvoted feature requests from the community that, while not fully aligned with the company’s strategy, can still be implemented in a low-effort way. I continue to review and respond to community posts a few times a year, so while I may not engage as frequently as I’d like, please know that I do read your feedback.
Workaround & Resolution:
As a workaround, you could activate the authorization of the OS and hide the OSE menu as shown in the attached image.
However, the good news is that this request was officially resolved in version 2024.04 (ticket 206848 in the http://wiki.produmex.name/doku.php?id=implementation:releasenotes:202404). I encourage you to upgrade to version 2024.04 or later to take advantage of this improvement.
From 2024.04 onwards a user which has full authorization for the ¨Tracking tracing Search¨ and no authorization for ¨Organization structure¨ is allowed to open the traceability report:
Thank you for your patience and engagement. Your feedback is always valuable in shaping the future of our product!
-
We think this is a good idea, and have plans to implement it in the future. If our partners agree and up-vote this idea we will see it in a future Quality of Life release.
-
Hello Gil Van den Hauwe,
Is there any update for this authorization? My client also needs a separate authorization for the Traceability report. If we allow to access the Organization Structure to all users, there is too risky for setting and configuration. If we turn off OS, the user cannot access the Traceability report.
-
Hello Gil Van den Hauwe, I see this post was from a year ago. Any development on this request? I am facing the same issue.
Thank you kindly.
-
Hello,
I have the same requirement. The GxP validation does not allow users to modify the quality status transitions what blocks access to the traceability report to most users. A separate authorisation for the Traceability report is a must.
-
Hi guys,
I don't want to burst your bubble but I first reported this issue to Boyum in October, 2019! This is the answer that I got at the time:
"This issue has be placed on the roadmap and will be addressed in the future.
Roadmap items have very low priority and at current Dev is having trouble keeping up with Medium to High priority items."If I were you, I wouldn't hold my breath over this, but If we post enough comments, who knows?
-
HI Miguel,
I was following up on my own ticket number and never noticed that in the release notes for version 2024.04. This is exactly waht we needed.
Thanks!
Please sign in to leave a comment.
Comments
7 comments