[
https://issues.apache.org/jira/browse/OFBIZ-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849725#comment-17849725
]
Jacques Le Roux edited comment on OFBIZ-13101 at 5/28/24 11:57 AM:
-------------------------------------------------------------------
Hi [~jleroux]
re:
{quote}So [~pierresmits], in what
<<Removing this duplicate also improves the experience for users with only VIEW
permissions, like auditor in the demo site.>>
Could you please explain, that's the most important point IMO
{quote}
Given that action triggers to create, update, expire or delete something must
be on permission conditions, a user with only VIEW permissions should not see
such action triggers. Like the one in this PR, the majority of link definitions
in screens xml files are without any kind of permission condition. As such,
they diminish the experience of such a user, as in most of those cases, the
user will see the screen/form to perform the action including the action
trigger on the presented form. If and when the user then activates the trigger
(add, updated, submit, etc.) on the form, that user is presented with '
{quote}The Following Errors Occurred:
You haven't the permission for the service createAgreementItem, reason : Access
refused
{quote}
message. Which could lead to unnecessary call to the DEVOPS team (and wasted
time/effort). Thus, it is preferred not to show such action triggers at all to
that kind of user. IMO, the best user experience is based on process flows (and
its screens/forms/etc. when there is no ambiguity.
I trust the above answers your question.
Best regards,
was (Author: pfm.smits):
Hi [~jleroux]
re:
{quote}So [~pierresmits], in what
Removing this duplicate also improves the experience for users with only VIEW
permissions, like auditor in the demo site.
Could you please explain, that's the most important point IMO
{quote}
Given that action triggers to create, update, expire or delete something must
be on permission conditions, a user with only VIEW permissions should not see
such action triggers. Like the one in this PR, the majority of link definitions
in screens xml files are without any kind of permission condition. As such,
they diminish the experience of such a user, as in most of those cases, the
user will see the screen/form to perform the action including the action
trigger on the presented form. If and when the user then activates the trigger
(add, updated, submit, etc.) on the form, that user is presented with '
{quote}The Following Errors Occurred:
You haven't the permission for the service createAgreementItem, reason : Access
refused
{quote}
message. Which could lead to unnecessary call to the DEVOPS team (and wasted
time/effort). Thus, it is preferred not to show such action triggers at all to
that kind of user. IMO, the best user experience is based on process flows (and
its screens/forms/etc. when there is no ambiguity.
I trust the above answers your question.
Best regards,
> Duplicate action trigger in Manufacturing
> -----------------------------------------
>
> Key: OFBIZ-13101
> URL: https://issues.apache.org/jira/browse/OFBIZ-13101
> Project: OFBiz
> Issue Type: Sub-task
> Components: manufacturing
> Reporter: Pierre Smits
> Assignee: Jacques Le Roux
> Priority: Major
> Fix For: Upcoming Branch
>
>
> On the 'FndProductionRun' an action trigger to create something is shown.
> This links to CreateProductionRun. This action trigger is already available
> via the MainActionMenu.
> Removing this duplicate also improves the experience for users with only VIEW
> permissions, like auditor in the demo site.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
