Commit Graph
28281 Commits
Author SHA1 Message Date
Pierre Smits f3775bde2d Improved: Request Roles - VIEW permissions (OFBIZ-12495) (#448)
Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the Request Roles screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions.
https://localhost:8443/ordermgr/control/requestroles?custRequestId=9000

Modified: CustRequestScreens.xml
- screen RequestRoles, restructured to work with permissions.
2022-01-20 13:25:36 +01:00
Pierre Smits 935dbbbb78 Improved: Move edit of Request to RequestSubTabBar (OFBIZ-12494) (#447)
In general, a <object>TabBar menu is intended to give users access to overviews related to the <object>. And a <object>SubTabBar menu is intended to give users access to actions to be performed on the <object>, like status changes, adding new related records, etc.
The menu-item for editing a request is currently located in the RequestTabBar menu in OrderMenus.xml.
Given that this menu-item is intended for users with UPDATE permissions and to give those users access to a screen to edit the data, this menu-item must move to the RequestSubTabBar menu.

modified: OrderMenus.xml
- menu RequestTabBar, removed menu-item editRequest (moved to RequestSubTabBar), additional cleanup
- menu RequestSubTabBar, added menu-item editRequest, added permission condition, additional cleanup
2022-01-20 13:21:44 +01:00
Pierre Smits f34a796857 Improved: Config Screen - VIEW permission (OFBIZ-12493) (#446)
Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the config item screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions.
See (test with): https://localhost:8443/catalog/control/EditProductConfigItem?configItemId=SC00000

modified:
- ConfigScreens.xml - restructured screen EditProductConfigItem to work with permissions
- ConfigForms.xml - added form ProductConfigItem for users with VIEW permission
2022-01-20 13:18:07 +01:00
Pierre Smits 761a56f23e Improved: Store Screen - VIIEW permission (OFBIZ-12492) (#445)
Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the store screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions.
See (test with): https://localhost:8443/catalog/control/EditProductStore?productStoreId=9000

mdified:
StoreScreens.xml - restructured screen EditProductStore to work with permissions
StoreFirms - added form ProductStore for users with VIEW permissions
2022-01-20 13:09:55 +01:00
Pierre Smits 81df0433bb Improved: Catalog Screen - VIEW permissions (OFBIZ-12491) (#444)
Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the catalog screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions.
See (test with): https://localhost:8443/catalog/control/EditProdCatalog?prodCatalogId=DemoCatalog

modified:
- CatalogScreens.xml
restructured screen EditProductCatalog vis-a-vis permissions
- ProdCatalogForms.xml
added form Catalog for users with VIEW permission
2022-01-20 13:08:19 +01:00
Pierre Smits 456df81cfe Improved: PaymentGroup Payments - VIEW permissions (OFBIZ-12502) (#457)
Currently, a user with only 'VIEW' permissions, as
demonstrated in trunk demo with userId = auditor,
accessing the Payment Group Payments screen, sees
editable fields and/or triggers (to requests)
reserved for users with 'CREATE' or 'UPDATE' permissions.

To see/test:
https://localhost:8443/accounting/control/EditPaymentGroupMember?paymentGroupId=9000

Modified: PaymentGroupScreens.xml
restructured screen ditPaymentGroupMember to work with permissions
2022-01-20 12:02:44 +01:00
Pierre Smits f6625639b5 Improved: Category Products - VIEW permissions (OFBIZ-12490) (#443)
Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the category products screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions.
See (test with): https://localhost:8443/catalog/control/EditCategoryProducts?productCategoryId=100

modified:
- CategoryScreens.xml
restructured EditCategoryProducts vis-a-vis permissions, additional cleanup
- CategoryForms.xml
added grid CategoryProducts for users with VIEW permissions
2022-01-20 12:00:27 +01:00
Pierre Smits 2a1438acc7 Improved: Product Prices - VIEW permissions (OFBIZ-12489) (#442)
* Improved: Product Prices - VIEW permissions (OFBIZ-12489)

Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the product prices screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions.
See (test with): https://localhost:8443/catalog/control/EditProductPrices?productId=WG-9943

Modified:
- ProductScreens.xml - restructured for working with permissions
- ProductForms.xml - added grid ProductPrices for users with VIEW permissions

* Improved: Product Prices - VIEW permissions (OFBIZ-12489)

Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the product prices screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions.
See (test with): https://localhost:8443/catalog/control/EditProductPrices?productId=WG-9943

modified: ProductForms.xml
added display type to fields
2022-01-20 11:56:03 +01:00
Pierre Smits 906f0637bb Improved: VIEW permissions - Agreement (OFBIZ-12488) (#441)
Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the agreement screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions.
See (test with): https://localhost:8443/accounting/control/EditAgreement?agreementId=DS-1000-SALES

Modified:
- AgreementScreens.xml
restructured EditAgreement screen regarding permissions, additional cleanup
- AgreementForms.xml
added form Agreement for users with VIEW permission, additional cleanup, label harmonisation
2022-01-20 11:54:12 +01:00
Pierre Smits b53d56f8eb Improved: VIEW permissions - BillingAccount roles (OFBIZ-12487) (#440)
Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the billing account roles screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions.
See (test with): https://localhost:8443/accounting/control/EditBillingAccountRoles?billingAccountId=9010

Modified:
BillingAccountScreens.xml, re EditBillingAccountRoles:
- added permission rules for CREATE/UPDATE
- restructured section and widget/fail-widget elements, additional cleanup
BillingAccountForms.xml
- added grid BillingAccountRoles (based on ListBillingAccountRoles)
- additional cleanup/label harmonisation
2022-01-20 11:47:36 +01:00
Jacques Le Roux 343438784c Improved: Use NPM with gradle to get external JS dependencies (OFBIZ-11960)
This replaces jquery-ui-timepicker-addon-1.6.3 by its equivalent from npm.

It should be noted that the 1.6.3 version is the EOL and
jquery-ui-timepicker-addon is no longer maintained.

Despite that according to
https://snyk.io/advisor/npm-package/jquery-ui-timepicker-addon
it's still a good choice, notably there are known no security issues.

I tried to use https://www.npmjs.com/package/jquery-datetimepicker instead
but crossed too much issues and let it go.
2022-01-20 10:11:24 +01:00
Pierre Smits 8c37ca2664 Improved: Move edit of Payment Group to SubTabBar (OFBIZ-12501) (#456)
In general, a <object>TabBar menu is intended to give
users access to overviews related to the <object>.
And a <object>SubTabBar menu is intended to give
users access to actions to be performed on the <object>,
like status changes, adding new related records, etc.
The menu-item for editing a payment group  is currently
located in the PaymentGroupTabBar menu in AccountingMenus.xml.
The menu item  belongs in the PaymentGroupSubTabBar

Improved: AccountingMenus.xml
PaymentGroupTabBar: removed menu item to edit the payment group, additonal cleanup
PaymentGroupSubTabBar: Added menu iteem to edit the payment group, additional cleanup
2022-01-18 15:48:14 +01:00
Pierre Smits 7787757d8f Improved: PaymentGroup - action items visible to viewer (OFBIZ-12486) (#439)
Menu items to perform actions in PaymentGroupSubTabBar are visible to users with only VIEW permissions. As shows when logged in with userId = auditor.

Modified: AccountingMenus.xml
added permissions rules to menu-items of PaymentGroupSubTabBar
2022-01-18 13:10:38 +01:00
Pierre Smits a4602d33fc Improved: Payment Group Common Decorator (OFBIZ-12463) (#438)
title of a payment group is shown below its menu(s)

Modified: CommonScreens.xml
- restructured CommonPaymentGroupDecorator, additional clean-up
2022-01-18 11:20:23 +01:00
Jacques Le Roux 495733f764 Improved: Use gradlew npm_outdated gradle-node-plugin taks to check outdated scripts (OFBIZ-12480)
Forgot to put back _form in OfbizUtil.js. THis is necessary for query-ui (1.13.0)
cf. OFBIZ-12480

Coincidentally removes trailing blanks
2022-01-18 10:43:26 +01:00
Jacques Le Roux d088f954b5 Improved: removes unused for 1,4 years CHANGELOG.adoc file
It can still be revivified from the Git log.
See https://lists.apache.org/thread/b9627b89zjc8qkym5kq2ycnh3cfllzlz for details
2022-01-17 13:38:29 +01:00
Pierre SmitsandJacques Le Roux 8fbc698542 Improved: Party - MainActionMenus (OFBIZ-12482) (#437)
* Improved: Party - MainActionMenus (OFBIZ-12482)

Currently the create buttons for the main objects of the party component are located within the find and other widgets/templates of those objects.
In order to improve the usability of OFBiz (and thus the appeal of it for adopters and users) these create buttons/links/etc. should be in a main action menu visible at all times when a user is working within the component.

Modified:
PartyMenus.xml: added MainActionMenu
CommonScreens.xml: included MainActionMenu where appropriate
CommunicationEventScreens.xml: included MainActionMenu where appropriate
PartyClassificationScreens.xml: included MainActionMenu where appropriate
PartyInvitationScreens.xml: included MainActionMenu where appropriate
VisitScreens.xml: included MainActionMenu where appropriate

* Uses PartyCreateNewPerson instead of CommonNew & CommonPerson

Co-authored-by: Jacques Le Roux <jacques.le.roux@les7arts.com>
2022-01-16 18:39:17 +01:00
Pierre Smits 4b19137635 Improved: List and Grid (OFBIZ-11345) (#436)
According to the definition in widget-form.xsd the use of a combination of a form with type="list" is deprecated in favour of a grid.
Refactor various list forms into grids.
Refactor various list form references in screens.

Modified:
InventoryForms.xml: from form definition with list ref to grid definition with list ref, additional clean-up
FacilityScreens.xml: from form ref to grid ref , additional cleanup
2022-01-16 15:11:10 +01:00
Pierre Smits 092f8f532a Improved: List and Grid (OFBIZ-11345) (#423)
According to the definition in widget-form.xsd the use of a combination of a
form with type="list" is deprecated in favour of a grid.
Refactor various list forms into grids.
Refactor various list form references in screens.

Modified:
SubscriptionScreens.xml: from form ref to grid ref , additional cleanup
SubscriptionForms.xml: from form definition with list ref to grid definition
with list ref, additional clean-up

jleroux: some modification after pushing previous commit from GH

In previous commit I noticed that Pierre used the CommonProduct label that I
committed for Pierre's "Adding som Dutch translations to common labels."
OFBIZ-6016

I did not notice then that there was already a more complete ProductProduct
label. I see no reason to create a new CommonProduct label. So I copied 2 lines
not present in ProductProduct from CommonProduct and removed the "nl" line that
is a duplicate of the "en" line.

With Michael we already said to Pierre that we don't like to review, before
pushing PR, not related changes mixed with what is announced by the title. It
complicates the review. I still remember being admonished by David E. Jones when
committing as a new committer doing the same. In the same David's spirit I see
no necessity to remove empty lines when it complicates the review...

Long story short, better make 2 different PR when such things is really
necessary...

I did not remove the <sub-hyperlink from communicationEventId lookup in
SubscriptionForms.xml. I checked there are 21 other cases like that in code.

Also better to remember to have lines not longer than 80 chars in commit comment.

All the rest is OK with me
2022-01-16 14:58:32 +01:00
Pierre Smits 5b909e41e2 Improved: List and Grid (OFBIZ-11345) (#423)
* Improved: List and Grid (OFBIZ-11345)

According to the definition in widget-form.xsd the use of a combination of a form with type="list" is deprecated in favour of a grid.
Refactor various list forms into grids.
Refactor various list form references in screens.

Modified:
SubscriptionScreens.xml: from form ref to grid ref , additional cleanup
SubscriptionForms.xml: from form definition with list ref to grid definition with list ref, additional clean-up

* Improved: List and Grid (OFBIZ-11345)

According to the definition in widget-form.xsd the use of a combination of a form with type="list" is deprecated in favour of a grid.
Refactor various list forms into grids.
Refactor various list form references in screens.

Modified:
SubscriptionScreens.xml: from form ref to grid ref , additional cleanup
SubscriptionForms.xml: from form definition with list ref to grid definition with list ref, additional clean-up
2022-01-16 14:05:55 +01:00
Pierre Smits 1ba999e528 Improved: Routing (Task) Screens - consistency in ux (OFBIZ-12500) (#452)
Currently, when accessing screens related to production schemas and schema tasks (routing and routing tasks) in Manufacturing, the title of the shown object is below the menu items for that object (as shown in image attached).
To get to a more consistent user experience, this should be above the menu items for the object, like is done in many other screens in OFBiz.

modified: RoutingScreens.xml
CommonRoutingDecorator: moved title of object to above its menu, additional cleanup
CommonRoutingTaskDecorator: moved title of object to above its menu, additional cleanup
2022-01-16 12:00:09 +01:00
Jacques Le Roux d599d7718b Improved: no functional change, labels improvements
In French, and maybe other languages, there is not only one word for new.
There are nouveau (masculine), nouvelle (féminine) and nouvel (masculine followed
by a word starting with a vowel)

Here are few related changes with misc. labels, and use of these labels in
MainActionMenu of marketing order and catalog menus
2022-01-16 10:28:20 +01:00
Jacques Le Roux 8a9596be84 Improved: no functional change, labels improvements
In French, and maybe other languages, there is not only one word for new.
There are nouveau (masculine), nouvelle (féminine) and nouvel (masculine followed
by a word starting with a vowel)

Here are few related changes with existing AccountingUiLabels, HumanResUiLabel
changes and a new CommonUiLabels French labels improvements and use of
HumanResNew* labels in MainActionMenu of HumanresMenus.xml

Also alongside replaces tabs by spaces in HumanResUiLabel
2022-01-16 08:51:03 +01:00
Jacques Le Roux c3fa39ce8e Improved: no functional change, labels improvements
In French, and maybe other languages, there is not only one word for new.
There are nouveau (masculine), nouvelle (féminine) and nouvel (masculine followed
by a word starting with a vowel)

This takes that into account by using rather
ManufacturingNewRouting and ManufacturingNewRoutingTask than
uiLabelMap.CommonNew and uiLabelMap.ManufacturingRoutingn same for
ManufacturingNewRoutingTask

I'll certainly do more when possible (all cases are not traduced)
2022-01-15 13:51:07 +01:00
Jacques Le Roux 5115b9b29e Improved: no functional change, removes tests in GH actions
Adding testIntegration in the GH Gradle process does not work.

For a reason I'll not dig in, it ALWAYS fails at:
Cannot find service [indexProductsFromContent] location class
(org.apache.ofbiz.content.search.SearchServices)
2022-01-15 12:25:59 +01:00
Pierre Smits 52678afeae Improved: Routing Screens - remove redundant action triggers (OFBIZ-12497) (#449)
* Improved: Routing Screens - remove redundant action triggers (OFBIZ-12497)

With the inclusion of the MainActionMenu for the Manufacturing application, several screens in RoutingScreens.xml now have redundant and obsolete action triggers also available in the MainActionMenu.
These action triggers must be removed, as these don't adhere to common permission conventions or are redundant.

Modified: RoutingScreens.xml
- removed action triggers from various routing and routing task screens, as well as their surrounding style widget elements.
- additional clean-up

* Additional removal of trigger action
2022-01-15 12:09:15 +01:00
Pierre Smits 0f77436a53 Improved: Invoice Screens = consistency in ux (OFBIZ-12498) (#450)
The majority of the invoice screens have grids encapsulated by a screenlet widget with a title. However some do not have this.

Modified: InvoiceScreens.xml
- screen InvoiceRoles - have grids in screenlet with title
- screen InvoiceTerms - have grids in screenlet with title
2022-01-15 10:50:04 +01:00
Jacques Le Roux fcf7c725c0 Improved: no functional change, add tests to GH actions
Buildbot is stale at the moment and it's better to not rely only on it.
This adds testIntegration to the GH Gradle process
2022-01-15 10:01:12 +01:00
Jacques Le Roux a5dc85c2a5 Tested: no functional change; just change VERSION to check BB config
With last commits BB config for R22 is stale
Back to 2022-01-01 when things worked
To test last schedulers changes
2022-01-14 09:41:26 +01:00
Jacques Le Roux afa56b0d24 Tested: no functional change; just change VERSION to check BB config
BB config for R22 is stale, checking trunk is still OK
2022-01-13 15:27:25 +01:00
Jacques Le Roux 0202b2b090 Fixed: Use NPM with gradle to get external JS dependencies (OFBIZ-11960)
Reverts build.gradle from previous commit ("Updates flot from 0.8.2 to 4.2.2
using npm"). It was mistakenly pushed then :/
2022-01-11 08:40:20 +01:00
Jacques Le Roux 7f7026e5da Improved: makes a French label consistent on the page
Both "Points d'accord commercial" and "Liste des articles de l'accord" were used
Now only "article" is used no longer "point"
2022-01-10 10:36:00 +01:00
Pierre Smits bbe64fa19e Improved: Move edit of invoice header to InvoiceSubTabBar (OFBIZ012440) (#409)
In general, a <object>TabBar menu is intended to give users access to overview related to the <object>. And a <object>SubTabBar menu is intended to give users to actions to be performed on the <object>, like status changes, adding new records, etc.
The menu-item for editing the invoice header (aptly translated as 'Header') is currently located in the InvoiceTabBar menu in AccountingMenus.xml.
Given that this menu-item is intended for users with UPDATE permissions and to give those users access to a screen to edit the data, this menu-item must move to the InvoiceSubTabBar menu

Modified: AccountingMenus.xml
- moved 'edit' menu-item for invoice from InvoiceTabBar menu to InvoiceSubTabBar menu. adjusted label.
2022-01-10 10:23:50 +01:00
Pierre Smits 70a9ef70d7 Improved: Have a Menu in Catalog featuring actions to create the main objects (OFBIZ-11774) (#433)
Currently the create buttons for the main objects of the catalog components are located within the find and profile widgets/templates of those object.
In order to improve the usability of OFBiz (and thus the appeal of it for adopters and users) these create buttons/links/etc. should be in a main action menu visible at all times when a user is working within the component.

added: main action menu, having menu-items for
- new product process
- new store process
- new catalog process
- new category process
subject to catalog create permissions

added: decorator section for inclusion of main action menu where appropriate

Some cleanup
2022-01-09 15:54:54 +01:00
Pierre Smits 9bf15d0a49 Fixed: Store Group screen don't connect with grids (OFBIZ-12481) (#435)
Screen EditProductStoreGroupAndAssoc does not connect with grid forms referenced.

Modified: StoreScreens.xml
moved from form references to grid references
removed screen duplicate
additional cleanup
2022-01-09 15:51:11 +01:00
Pierre Smits a9adf8de71 Improved: List and Grid (OFBIZ-11345) (#434)
According to the definition in widget-form.xsd the use of a combination of a form with type="list" is deprecated in favour of a grid.
Refactor various list forms into grids.
Refactor various list form references in screens.

Modified:
ShipmentGatewayConfigScreens.xml: from form ref to grid ref , additional cleanup
ShipmentGatewayConfigForms.xml: from form definition with list ref to grid definition with list ref, additional clean-up
2022-01-09 09:19:06 +01:00
Jacques Le Roux c3a6636e40 Improved: Use gradlew npm_outdated gradle-node-plugin taks to check outdated scripts (OFBIZ-12480)
I just tried g npm_outdated undocumented Gradle task and got this result*:

> Task :npm_outdated
Package         Current  Wanted  Latest  Location
dompurify         2.3.3   2.3.4   2.3.4  ofbiz-framework
jquery            3.5.1   3.6.0   3.6.0  ofbiz-framework
jquery-migrate    3.3.1   3.3.2   3.3.2  ofbiz-framework
jquery-ui-dist   1.12.1  1.13.0  1.13.0  ofbiz-framework

This updates accordingly. I keep this task open as an umbrella tasks for similar
subtasks in future like we have OFBIZ-10213
2022-01-08 13:04:10 +01:00
Jacques Le Roux 83d0880ab8 Improved: Use NPM with gradle to get external JS dependencies (OFBIZ-11960)
Updates flot from 0.8.2 to 4.2.2 using npm
2022-01-08 11:18:40 +01:00
Pierre Smits 1b0b723887 Improved: List and Grid (OFBIZ-11345) (#432)
Refactor various list forms into grids.
Refactor various list form references in screens.

Modified:
FacilityGroupScreens.xml: from form ref to grid ref , additional cleanup
FacilityGroupForms.xml: from form definition with list ref to grid definition with list ref, additional clean-up
2022-01-08 08:59:28 +01:00
Pierre Smits bcd23f784b Improved: List and Grid (OFBIZ-11345) (#431)
According to the definition in widget-form.xsd the use of a combination
of a form with type="list" is deprecated in favour of a grid.
Refactor various list forms into grids.
Refactor various list form references in screens.

Modified:
FacilityScreens.xml: from form ref to grid ref , additional cleanup
FacilityForms.xml: from form definition with list ref to grid definition with list ref, additional clean-up
2022-01-07 09:47:03 +01:00
Pierre Smits dcef04cfe2 Improved: VIEW permissions FinAccount mutations (OFBIZ-12451) (#410)
Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the Financial Account mutations screen  sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions.
See (test with):
https://demo-trunk.ofbiz.apache.org/accounting/control/EditFinAccount?finAccountId=ABN_CHECKING
https://demo-trunk.ofbiz.apache.org/accounting/control/FindPaymentsForDepositOrWithdraw

Modified:
- FinAccountScreens.xml: work with permissions, added ref to mutations template for user with VIEW permission
Added:
- Mutations.ftl template.
2022-01-07 09:03:05 +01:00
bjugl 4ae01b94f1 Improved: Replace ELRTE plugin with Trumbowyg (OFBIZ-10093) (#425)
Thanks: Jacques for inspiration and guidance, Aditya Sharma for sharing
thoughts and visions and Ingo Richter for finding this gem.

- changed grid 'EditProductPriceRulesCondition' list-name to reflect
correct list
2022-01-07 12:16:27 +05:30
Pierre Smits b9af0ccb09 Improved: Remove unused labels from AccountingUiLabels.xml (OFBIZ-9352) (#413)
Removing unused labels from AccountingUiLabels.xml
Checked screens, forms, templates, scripts and java code
2022-01-06 17:19:35 +01:00
Pierre Smits 583ccf966d Improved: VIEW permissions BillingAccount (OFBIZ-12457) (#414)
Currently, a user with only 'VIEW' permissions, as demonstrated in trunk demo with userId = auditor, accessing the billing account screen, sees editable fields and/or triggers (to requests) reserved for users with 'CREATE' or 'UPDATE' permissions.
See (test with): https://demo-trunk.ofbiz.apache.org/accounting/control/EditBillingAccount?billingAccountId=9010

Modified:
BillingAccountScreens.xml
- screen EditBillingAccount: restructured to work with view permissions
- screen CommonBillingAccountDecorator: added label visible to all billing account screens
- additional cleanup
BillingAccountForms.xml
- added form BillingAccount for users with VIEW permission
- additional cleanup
2022-01-06 17:14:10 +01:00
Pierre Smits a22aff5659 Improved: Invoice - CommonInvoiceDecorator (OFBIZ-12458) (#415)
Modified: InvoiceScreens.xml
- moved invoice menus to pre-body decorator section
- moved label to above menus for the invoice
- additional cleanup
2022-01-06 16:58:46 +01:00
Pierre Smits 6e46892a6f Improved: Agreement - CommonAgreementDecorator (OFBIZ-12462) (#418)
title of an agreement is shown below its menu(s).

Modified: AgreementScreens.xml
moved label involving agreement title to pre-body decorator-section
2022-01-06 16:47:05 +01:00
Pierre Smits c7ebb3ffbf Improved: List and Grid (OFBIZ-11345) (#426)
According to the definition in widget-form.xsd the use of a combination of a form with type="list" is deprecated in favour of a grid.
Refactor various list forms into grids.
Refactor various list form references in screens.

Modified:
ShippingScreens.xml in product: from form ref to grid ref , additional cleanup
ShippingForms.xml: from form definition with list ref to grid definition with list ref, additional clean-up
2022-01-06 12:00:31 +01:00
Pierre Smits 2779c99bce Improved: Have a menu in Marketing featuring actions to create main objects (OFBIZ-11783) (#428)
Currently the create buttons for the main objects of the marketing application are located
within find and profile widgets/templates of those objects.

In order to improve the usability of this application, OFBiz,
and thus the appeal of it for adopters and users, these create buttons/links/etc.
should be in a main action menu visible at all times when a user is working within
the application of the component.

Modified:
MarketingMenus.xml - added MainActionMenu
To following screens - added ref to MainActionMenu, clean-up
CommonScreens.xml
ContactListScreens.xml
DataSourceScreens.xml
MarketingCampaignScreens.xml
MarketingReportScreens.xml
SegmentScreens.xml
TrackingCodeScreens.xml
2022-01-06 11:58:45 +01:00
Pierre Smits 75aeb494a0 Improved: Have a Menu in Humanres featuring actions to create the main objects (OFBIZ-11777) (#429)
Currently the create buttons for the main objects of the humanres plugin are located within find and profile widgets/templates of those objects.

In order to improve the usability of this plugin, OFBiz (and thus the appeal of it for adopters and users) these create buttons/links/etc. should be in a main action menu visible at all times when a user is working within the web appliclation of the component.

Modified:
HumanresMenus.xml - added MainActionMenu
To following screens - added ref to MainActionMenu, clean-up
CommonScreens.xml
EmplLeaveScreens.xml
EmployeeScreens.xml
EmploymentScreens.xml
PartyQualScreens.xml
PartyResumeScreens.xml
PartySkillsScreens.xml
PerfReviewScreens.xml
2022-01-06 11:56:26 +01:00
Pierre Smits 4f18c3f0f1 Improved: Dutch translations (OFBIZ-10363) (#430)
some cleanup (duplicate) and improved Dutch translations
2022-01-06 11:23:44 +01:00