You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2019/05/20 08:19:00 UTC
[jira] [Closed] (OFBIZ-10899) Have an Auditor party with associated
AUDITOR SecurityGroup permissions in all DEMO instances
[ https://issues.apache.org/jira/browse/OFBIZ-10899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Le Roux closed OFBIZ-10899.
-----------------------------------
Resolution: Implemented
Fix Version/s: Upcoming Branch
Thanks Pierre,
Your patch is in trunk at revision: 1859535
> Have an Auditor party with associated AUDITOR SecurityGroup permissions in all DEMO instances
> ---------------------------------------------------------------------------------------------
>
> Key: OFBIZ-10899
> URL: https://issues.apache.org/jira/browse/OFBIZ-10899
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL APPLICATIONS
> Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, Release Branch 18.12
> Reporter: Pierre Smits
> Assignee: Jacques Le Roux
> Priority: Major
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-10899-AuditorData.patch
>
>
> While doing an implementation for a rental company (with involvement of an external accountant/auditor), I came across the aspect that there is no default security group regarding auditors. These parties, in general, have only view permissions on the UI elements (screens/menu-items/forms and templates).
> In order to help the (potential) adopters to choose OFBiz, it would be smart to have such a party, with the proposed SecurityGroup (and the appropriate permissions) in play in any of our demo instances.
> Not only for the aspect mentioned above, but also for seeing whether other improvements can occur (e.g. create buttons visible to 'VIEW' only permission holders).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)