Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0018878Openbravo ERP01. General setuppublic2011-10-26 12:362022-02-01 08:08
dmitry_mezentsev 
Triage Platform Base 
normalminoralways
newopen 
5
 
 
Core
No
0018878: Role assigned by default to the user during Initial Client Setup process should not have access to advanced functionality window
Full list of advanced windows will be attached later to this ticket.

At the same time in order to enable easy functionality discovery by users another role (sth like <Client> Advanced Admin) with access to all windows (including advance ones) should also be created.

For example, in Procurement Management - "Create Purchase Invoices from Deliveries" window is an advanced feature so it should not be available by default for the user created during Initial Client Setup.

For example, in Master Data Management - "Salary Category" and "Total Product Template Report" windows are advanced features.

No tags attached.
has duplicate defect 0018964 closed jonalegriaesarte "Create Purchase Invoices from Deliveries" should not be accessible to "Openbravo Admin" role as this is an advanced feature 
has duplicate defect 00159423.0RC4 closed naiaramartinez 3.0RC3: Screens Shipping Company and Freight Category are in 3.0, yet the shipping info removed from Goods Receipt/shipment 
Issue History
2011-10-26 12:36dmitry_mezentsevNew Issue
2011-10-26 12:36dmitry_mezentsevAssigned To => eduardo_Argal
2011-10-26 12:36dmitry_mezentsevModules => Core
2011-10-26 12:52dmitry_mezentsevDescription Updatedbug_revision_view_page.php?rev_id=2839#r2839
2011-11-03 16:10psanjuanRelationship addedrelated to 0018964
2011-11-03 16:12psanjuanDescription Updatedbug_revision_view_page.php?rev_id=2871#r2871
2011-11-03 16:13psanjuanRelationship replacedhas duplicate 0018964
2011-11-03 17:51psanjuanAssigned Toeduardo_Argal => alostale
2011-11-03 17:51psanjuanSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=2875#r2875
2011-11-08 13:07RenateNieuwkoopNote Added: 0042676
2011-11-08 15:53dmitry_mezentsevNote Added: 0042677
2011-11-15 11:34hgbotCheckin
2011-11-15 11:34hgbotNote Added: 0042823
2011-11-15 12:19hgbotCheckin
2011-11-15 12:19hgbotNote Added: 0042826
2011-11-15 12:19hgbotCheckin
2011-11-15 12:19hgbotNote Added: 0042827
2011-11-15 12:27hgbotCheckin
2011-11-15 12:27hgbotNote Added: 0042828
2011-11-15 12:47hgbotCheckin
2011-11-15 12:47hgbotNote Added: 0042830
2011-11-22 03:50hudsonbotCheckin
2011-11-22 03:50hudsonbotNote Added: 0043027
2011-11-22 03:50hudsonbotCheckin
2011-11-22 03:50hudsonbotNote Added: 0043028
2011-11-22 03:50hudsonbotCheckin
2011-11-22 03:50hudsonbotNote Added: 0043029
2011-11-22 03:50hudsonbotCheckin
2011-11-22 03:50hudsonbotNote Added: 0043030
2011-11-22 03:50hudsonbotCheckin
2011-11-22 03:50hudsonbotNote Added: 0043031
2011-11-24 19:32dmitry_mezentsevNote Added: 0043198
2012-02-28 08:51hgbotCheckin
2012-02-28 08:51hgbotNote Added: 0045497
2012-03-02 15:39hudsonbotCheckin
2012-03-02 15:39hudsonbotNote Added: 0045966
2012-03-20 18:12naiaramartinezRelationship addedrelated to 0015942
2012-03-20 18:20naiaramartinezRelationship replacedhas duplicate 0015942
2017-04-10 14:37alostaleAssigned Toalostale => platform
2022-02-01 08:08alostaleAssigned Toplatform => Triage Platform Base

Notes
(0042676)
RenateNieuwkoop   
2011-11-08 13:07   
I suggest a name like 'superuser' per module. For example there is a finance department that all have access to the 'finance' role. One senior member of the team would have a 'superuser finance' role that gives access to advanced screens for finance.
Likewise in the sales department all employees have access to the 'sales' role. One senior member has access to a 'superuser sales' role that give access to advanced screens for sales management.
I can't see a role that has access to all advanced screens, since it would mean that whoever has that role is supposed to know advanced functionality for all areas and I don't see that as being realistic.
(0042677)
dmitry_mezentsev   
2011-11-08 15:53   
Renate,

I think there are 2 ways that roles are used:
1. In day to day operations when OB is implemented. For this we have Standard Roles dataset shipped with Core. It represents very generic roles. That is its goal, we should not over complicate it (so I would not add more options into it). But still Standard Roles are of a great help to our customers to use them as a starting point and to build on top of them.
2. During product evaluation. As we can see for this case the best role is the admin role. People evaluating would like to browse across the application, across different functional areas, and forcing them to switch roles to do it is a pain. Actually we had this experience before of putting by default Finance Role and there were a lot of complains on it. Now Admin role is the default one. But this Admin role is not consistent with the out-of-the-box Openbravo because it has access to some windows that provide features that are not enabled in some other application windows (like Salary Category window is active but Salary Category Tab is not in BP). So with this FR we would like to make all the things coherent - if feature is disabled in application by default it should not be by default visible (you would need to do some changes - change default role, enable tabs and so on).
(0042823)
hgbot   
2011-11-15 11:34   
Repository: erp/devel/pi
Changeset: 15d911f25076a2b779c796048f7fb6d7d89333a2
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Tue Nov 15 11:33:06 2011 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/15d911f25076a2b779c796048f7fb6d7d89333a2 [^]

related to issue 18878: Added advanced feature definition

---
M modules/org.openbravo.advpaymentmngt/src-db/database/sourcedata/AD_FORM.xml
M modules/org.openbravo.advpaymentmngt/src-db/database/sourcedata/AD_PROCESS.xml
M modules/org.openbravo.client.application/src-db/database/model/tables/OBUIAPP_PARAMETER.xml
M modules/org.openbravo.client.application/src-db/database/model/tables/OBUIAPP_VIEW_IMPL.xml
M modules/org.openbravo.client.application/src-db/database/sourcedata/AD_COLUMN.xml
M modules/org.openbravo.client.application/src-db/database/sourcedata/AD_FIELD.xml
M modules/org.openbravo.client.application/src-db/database/sourcedata/AD_WINDOW.xml
M modules/org.openbravo.client.application/src-db/database/sourcedata/OBUIAPP_VIEW_IMPL.xml
M modules/org.openbravo.client.kernel/src-db/database/sourcedata/AD_WINDOW.xml
M modules/org.openbravo.client.myob/src-db/database/sourcedata/AD_WINDOW.xml
M modules/org.openbravo.financial.paymentreport/src-db/database/sourcedata/AD_PROCESS.xml
M modules/org.openbravo.reports.ordersawaitingdelivery/src-db/database/sourcedata/AD_PROCESS.xml
M modules/org.openbravo.service.datasource/src-db/database/sourcedata/AD_WINDOW.xml
M modules/org.openbravo.service.integration.google/src-db/database/model/functions/OBSEIG_UPDATE_ACCESS.xml
M modules/org.openbravo.service.integration.google/src-db/database/sourcedata/AD_WINDOW.xml
M modules/org.openbravo.service.integration.google/src-db/database/sourcedata/OBUIAPP_VIEW_IMPL.xml
M src-db/database/model/functions/AD_UPDATE_ACCESS.xml
M src-db/database/model/tables/AD_FORM.xml
M src-db/database/model/tables/AD_PROCESS.xml
M src-db/database/model/tables/AD_ROLE.xml
M src-db/database/model/tables/AD_WINDOW.xml
M src-db/database/model/triggers/AD_ROLE_TRG.xml
M src-db/database/sourcedata/AD_COLUMN.xml
M src-db/database/sourcedata/AD_ELEMENT.xml
M src-db/database/sourcedata/AD_FIELD.xml
M src-db/database/sourcedata/AD_FORM.xml
M src-db/database/sourcedata/AD_PROCESS.xml
M src-db/database/sourcedata/AD_WINDOW.xml
---
(0042826)
hgbot   
2011-11-15 12:19   
Repository: erp/devel/pi
Changeset: 234dc1964e6d485a2e61c0d04338e72570d3566a
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Tue Nov 15 12:18:34 2011 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/234dc1964e6d485a2e61c0d04338e72570d3566a [^]

related to issue 18878: isAdvanced col is mandatory and has check

---
M src-db/database/model/tables/AD_FORM.xml
M src-db/database/model/tables/AD_PROCESS.xml
M src-db/database/model/tables/AD_WINDOW.xml
---
(0042827)
hgbot   
2011-11-15 12:19   
Repository: erp/devel/pi
Changeset: c61120f1c12c60c69254eeec56367795617950bb
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Tue Nov 15 12:19:02 2011 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/c61120f1c12c60c69254eeec56367795617950bb [^]

related to issue 18878: isAdvanced col is mandatory and has check

---
M modules/org.openbravo.client.application/src-db/database/model/tables/OBUIAPP_VIEW_IMPL.xml
---
(0042828)
hgbot   
2011-11-15 12:27   
Repository: erp/devel/pi
Changeset: 014ff1ba6d497dfa4a92f56d707ae04553dcae6f
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Tue Nov 15 12:27:11 2011 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/014ff1ba6d497dfa4a92f56d707ae04553dcae6f [^]

related to issue 18878: recovered deleted fk

---
M modules/org.openbravo.client.application/src-db/database/model/tables/OBUIAPP_PARAMETER.xml
---
(0042830)
hgbot   
2011-11-15 12:47   
Repository: erp/devel/pi
Changeset: bc8969312b17067ba00f4b810cef4154ee57556b
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Tue Nov 15 12:45:27 2011 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/bc8969312b17067ba00f4b810cef4154ee57556b [^]

related to issue 18878: added boolean check to ad_role.isAdvanced

---
M src-db/database/model/tables/AD_ROLE.xml
---
(0043027)
hudsonbot   
2011-11-22 03:50   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/ebd713dfe507 [^]

Maturity status: Test
(0043028)
hudsonbot   
2011-11-22 03:50   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/ebd713dfe507 [^]

Maturity status: Test
(0043029)
hudsonbot   
2011-11-22 03:50   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/ebd713dfe507 [^]

Maturity status: Test
(0043030)
hudsonbot   
2011-11-22 03:50   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/ebd713dfe507 [^]

Maturity status: Test
(0043031)
hudsonbot   
2011-11-22 03:50   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/ebd713dfe507 [^]

Maturity status: Test
(0043198)
dmitry_mezentsev   
2011-11-24 19:32   
Asier,

List of advance menu entries is shared with you.
(0045497)
hgbot   
2012-02-28 08:51   
Repository: erp/devel/pi
Changeset: 747f9d62c378b2113b5481eee9d9e66a1414d8ea
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Tue Feb 28 08:50:14 2012 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/747f9d62c378b2113b5481eee9d9e66a1414d8ea [^]

related to issue 18878: Advanced features

  Some fixes/improvements:
    * Fixed update access: previously is added access to advanced features to
      not advanced roles.
    * When executing update access, remove advanced features access from non
      advanced roles.
    * When creating/updating form, processes or window take into account adv
      features to grant access.

---
M src-db/database/model/functions/AD_UPDATE_ACCESS.xml
M src-db/database/model/triggers/AD_FORM_TRG.xml
M src-db/database/model/triggers/AD_PROCESS_TRG.xml
M src-db/database/model/triggers/AD_WINDOW_TRG.xml
---
(0045966)
hudsonbot   
2012-03-02 15:39   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/544d64e0c159 [^]

Maturity status: Test