[jira] Updated: (OFBIZ-2890) macro to display error messages individually besides each input field
[ https://issues.apache.org/jira/browse/OFBIZ-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abdullah Shaikh updated OFBIZ-2890: --- Attachment: OFBIZ-2890_macro to display error messages individually.patch Added fieldErrors & fieldErrorsMulti macros to commonMacros.ftl, for displaying error messages individually besides each input field. > macro to display error messages individually besides each input field > - > > Key: OFBIZ-2890 > URL: https://issues.apache.org/jira/browse/OFBIZ-2890 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: SVN trunk >Reporter: Abdullah Shaikh >Priority: Trivial > Attachments: OFBIZ-2890_macro to display error messages > individually.patch > > > Added fieldErrors & fieldErrorsMulti to commonMacros.ftl, to display error > messages individually besides each input field. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (OFBIZ-2110) Add initialAccount field to SalesOpportunity entity
So long as we're in agreement that outstanding issues shouldn't be closed solely due to a lack of activity. Regards Scott HotWax Media http://www.hotwaxmedia.com On 2/09/2009, at 6:32 PM, Jacques Le Roux (JIRA) wrote: [ https://issues.apache.org/jira/browse/OFBIZ-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750293 #action_12750293 ] Jacques Le Roux commented on OFBIZ-2110: To speed up things, seems to work :) Add initialAccount field to SalesOpportunity entity --- Key: OFBIZ-2110 URL: https://issues.apache.org/jira/browse/OFBIZ-2110 Project: OFBiz Issue Type: Bug Components: order Affects Versions: SVN trunk Reporter: Vince Clark Assignee: Jacques Le Roux Priority: Minor Attachments: SalesOpportunityEntity.patch There is a field in the SalesOpportunity form to link to a Party but no field in the entity to store it in. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. smime.p7s Description: S/MIME cryptographic signature
[jira] Created: (OFBIZ-2890) macro to display error messages individually besides each input field
macro to display error messages individually besides each input field - Key: OFBIZ-2890 URL: https://issues.apache.org/jira/browse/OFBIZ-2890 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Reporter: Abdullah Shaikh Priority: Trivial Added fieldErrors & fieldErrorsMulti to commonMacros.ftl, to display error messages individually besides each input field. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-2838) ServiceUtil.getUserLogin tests on null but not empty
[
https://issues.apache.org/jira/browse/OFBIZ-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-2838.
--
Resolution: Fixed
Fix Version/s: SVN trunk
Release Branch 9.04
Assignee: Al Byers
Thanks for report Al,
Fixed in trunk at r810370 and R9.04 at r810375.
> ServiceUtil.getUserLogin tests on null but not empty
>
>
> Key: OFBIZ-2838
> URL: https://issues.apache.org/jira/browse/OFBIZ-2838
> Project: OFBiz
> Issue Type: Bug
> Components: framework
>Reporter: Al Byers
>Assignee: Al Byers
> Fix For: Release Branch 9.04, SVN trunk
>
>
> Line 587 in ServiceUtil.getUserLogin is:
> if (runAsUser != null) {
> but i got an empty string passed in.
> Should use UtilValidate.isNotEmpty?
> I could change it, but I don't think I have ever touched core code and don't
> wish to start.
> -Al
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Splitting "Main New Feature" page into multiple pages
Hi Hans, Before answering : I have sent a message to user ML about docbook, what do you think about an "easy" editor ? Jacques From: "Hans Bakker" Somebody put a comment on the list that there should be a 'base' list i.e. a list of all functions in the system. If we would use the docbook xml format then. this new feature list and a 'base' list can be created avoiding duplicate text. That means when a new feature is created, it can be documented in the base list and a reference to it can be added to the 'main New Feature' list. The base text can also consist out of included text from the help screens. perhaps i get too carried away? On Wed, 2009-09-02 at 12:59 +0700, Hans Bakker wrote: Perhaps at the same time convert it to the docbook format and put it in ofbiz? In confuence a link can be put to the actual document similar like: http://demo.ofbiz.org/cmssite/cms/APACHE_OFBIZ_HTML ? regards, Hans On Wed, 2009-09-02 at 10:23 +0530, Ashish Vijaywargiya wrote: > Hello Jacques & Others, > > This issue has been discussed before few days but we didn't reach to some > final conclusion AFAIK. > Lets plan how best we can arrange the content of "Main New Feature" page. > > This page is becoming large day by day so opening this page in edit mode > takes long time. > I remembered that in last discussion Vikas Mayur(as I remembered but I could > be wrong) has suggested to split this on year basis. > > The content of each year can be put in separate page and the link for the > navigation to those pages can be kept either at the top or bottom of this > page. > Lets finalize this thing in this thread and plan to do the needful ASAP. > > Please let me know your thoughts on this. > > -- > Ashish -- Antwebsystems.com: Quality OFBiz services for competitive rates
[jira] Commented: (OFBIZ-2110) Add initialAccount field to SalesOpportunity entity
[ https://issues.apache.org/jira/browse/OFBIZ-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750293#action_12750293 ] Jacques Le Roux commented on OFBIZ-2110: To speed up things, seems to work :) > Add initialAccount field to SalesOpportunity entity > --- > > Key: OFBIZ-2110 > URL: https://issues.apache.org/jira/browse/OFBIZ-2110 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: SVN trunk >Reporter: Vince Clark >Assignee: Jacques Le Roux >Priority: Minor > Attachments: SalesOpportunityEntity.patch > > > There is a field in the SalesOpportunity form to link to a Party but no field > in the entity to store it in. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Splitting "Main New Feature" page into multiple pages
Somebody put a comment on the list that there should be a 'base' list i.e. a list of all functions in the system. If we would use the docbook xml format then. this new feature list and a 'base' list can be created avoiding duplicate text. That means when a new feature is created, it can be documented in the base list and a reference to it can be added to the 'main New Feature' list. The base text can also consist out of included text from the help screens. perhaps i get too carried away? On Wed, 2009-09-02 at 12:59 +0700, Hans Bakker wrote: > Perhaps at the same time convert it to the docbook format and put it in > ofbiz? In confuence a link can be put to the actual document similar > like: http://demo.ofbiz.org/cmssite/cms/APACHE_OFBIZ_HTML ? > > regards, > Hans > > On Wed, 2009-09-02 at 10:23 +0530, Ashish Vijaywargiya wrote: > > Hello Jacques & Others, > > > > This issue has been discussed before few days but we didn't reach to some > > final conclusion AFAIK. > > Lets plan how best we can arrange the content of "Main New Feature" page. > > > > This page is becoming large day by day so opening this page in edit mode > > takes long time. > > I remembered that in last discussion Vikas Mayur(as I remembered but I could > > be wrong) has suggested to split this on year basis. > > > > The content of each year can be put in separate page and the link for the > > navigation to those pages can be kept either at the top or bottom of this > > page. > > Lets finalize this thing in this thread and plan to do the needful ASAP. > > > > Please let me know your thoughts on this. > > > > -- > > Ashish -- Antwebsystems.com: Quality OFBiz services for competitive rates
[jira] Commented: (OFBIZ-2110) Add initialAccount field to SalesOpportunity entity
[ https://issues.apache.org/jira/browse/OFBIZ-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750289#action_12750289 ] Scott Gray commented on OFBIZ-2110: --- Why? > Add initialAccount field to SalesOpportunity entity > --- > > Key: OFBIZ-2110 > URL: https://issues.apache.org/jira/browse/OFBIZ-2110 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: SVN trunk >Reporter: Vince Clark >Assignee: Jacques Le Roux >Priority: Minor > Attachments: SalesOpportunityEntity.patch > > > There is a field in the SalesOpportunity form to link to a Party but no field > in the entity to store it in. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Splitting "Main New Feature" page into multiple pages
Perhaps at the same time convert it to the docbook format and put it in ofbiz? In confuence a link can be put to the actual document similar like: http://demo.ofbiz.org/cmssite/cms/APACHE_OFBIZ_HTML ? regards, Hans On Wed, 2009-09-02 at 10:23 +0530, Ashish Vijaywargiya wrote: > Hello Jacques & Others, > > This issue has been discussed before few days but we didn't reach to some > final conclusion AFAIK. > Lets plan how best we can arrange the content of "Main New Feature" page. > > This page is becoming large day by day so opening this page in edit mode > takes long time. > I remembered that in last discussion Vikas Mayur(as I remembered but I could > be wrong) has suggested to split this on year basis. > > The content of each year can be put in separate page and the link for the > navigation to those pages can be kept either at the top or bottom of this > page. > Lets finalize this thing in this thread and plan to do the needful ASAP. > > Please let me know your thoughts on this. > > -- > Ashish -- Antwebsystems.com: Quality OFBiz services for competitive rates
[jira] Commented: (OFBIZ-2110) Add initialAccount field to SalesOpportunity entity
[ https://issues.apache.org/jira/browse/OFBIZ-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750278#action_12750278 ] Jacques Le Roux commented on OFBIZ-2110: If nobody cares I will close this issue... > Add initialAccount field to SalesOpportunity entity > --- > > Key: OFBIZ-2110 > URL: https://issues.apache.org/jira/browse/OFBIZ-2110 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: SVN trunk >Reporter: Vince Clark >Assignee: Jacques Le Roux >Priority: Minor > Attachments: SalesOpportunityEntity.patch > > > There is a field in the SalesOpportunity form to link to a Party but no field > in the entity to store it in. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Splitting "Main New Feature" page into multiple pages
+1. Good idea ! Jacques From: "Ashish Vijaywargiya" Hello Jacques & Others, This issue has been discussed before few days but we didn't reach to some final conclusion AFAIK. Lets plan how best we can arrange the content of "Main New Feature" page. This page is becoming large day by day so opening this page in edit mode takes long time. I remembered that in last discussion Vikas Mayur(as I remembered but I could be wrong) has suggested to split this on year basis. The content of each year can be put in separate page and the link for the navigation to those pages can be kept either at the top or bottom of this page. Lets finalize this thing in this thread and plan to do the needful ASAP. Please let me know your thoughts on this. -- Ashish
Splitting "Main New Feature" page into multiple pages
Hello Jacques & Others, This issue has been discussed before few days but we didn't reach to some final conclusion AFAIK. Lets plan how best we can arrange the content of "Main New Feature" page. This page is becoming large day by day so opening this page in edit mode takes long time. I remembered that in last discussion Vikas Mayur(as I remembered but I could be wrong) has suggested to split this on year basis. The content of each year can be put in separate page and the link for the navigation to those pages can be kept either at the top or bottom of this page. Lets finalize this thing in this thread and plan to do the needful ASAP. Please let me know your thoughts on this. -- Ashish
Re: svn commit: r810343 - /ofbiz/trunk/applications/order/widget/ordermgr/CustRequestForms.xml
don't worry about itif you not make errors you do not work That is why I make a lot of errors.. :-) Regards, Hans On Wed, 2009-09-02 at 16:22 +1200, Scott Gray wrote: > Thanks Hans, I've checked all the other form that I added those > parameters to and fixed one that was incorrect. > > Regards > Scott > > On 2/09/2009, at 2:42 PM, hans...@apache.org wrote: > > > Author: hansbak > > Date: Wed Sep 2 02:42:42 2009 > > New Revision: 810343 > > > > URL: http://svn.apache.org/viewvc?rev=810343&view=rev > > Log: > > viewindex not for this service > > > > Modified: > >ofbiz/trunk/applications/order/widget/ordermgr/CustRequestForms.xml > > > > Modified: ofbiz/trunk/applications/order/widget/ordermgr/ > > CustRequestForms.xml > > URL: > > http://svn.apache.org/viewvc/ofbiz/trunk/applications/order/widget/ordermgr/CustRequestForms.xml?rev=810343&r1=810342&r2=810343&view=diff > > = > > = > > = > > = > > = > > = > > = > > = > > == > > --- ofbiz/trunk/applications/order/widget/ordermgr/ > > CustRequestForms.xml (original) > > +++ ofbiz/trunk/applications/order/widget/ordermgr/ > > CustRequestForms.xml Wed Sep 2 02:42:42 2009 > > @@ -528,8 +528,6 @@ > > > field="lookupPartyId"/> > > > field="custRequest.custRequestDate"/> > > > > - > field="viewIndex"/> > > - > field="viewSize"/> > > > > > > > > > > > -- Antwebsystems.com: Quality OFBiz services for competitive rates
Re: svn commit: r810343 - /ofbiz/trunk/applications/order/widget/ordermgr/CustRequestForms.xml
Thanks Hans, I've checked all the other form that I added those parameters to and fixed one that was incorrect. Regards Scott On 2/09/2009, at 2:42 PM, hans...@apache.org wrote: Author: hansbak Date: Wed Sep 2 02:42:42 2009 New Revision: 810343 URL: http://svn.apache.org/viewvc?rev=810343&view=rev Log: viewindex not for this service Modified: ofbiz/trunk/applications/order/widget/ordermgr/CustRequestForms.xml Modified: ofbiz/trunk/applications/order/widget/ordermgr/ CustRequestForms.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/order/widget/ordermgr/CustRequestForms.xml?rev=810343&r1=810342&r2=810343&view=diff = = = = = = = = == --- ofbiz/trunk/applications/order/widget/ordermgr/ CustRequestForms.xml (original) +++ ofbiz/trunk/applications/order/widget/ordermgr/ CustRequestForms.xml Wed Sep 2 02:42:42 2009 @@ -528,8 +528,6 @@ field="lookupPartyId"/> field="custRequest.custRequestDate"/> -field="viewIndex"/> -field="viewSize"/> smime.p7s Description: S/MIME cryptographic signature
Re: svn commit: r809984 - in /ofbiz/trunk/applications/accounting: ./ data/ entitydef/ script/org/ofbiz/accounting/ script/org/ofbiz/accounting/finaccount/ script/org/ofbiz/accounting/ledger/ servic
I do have privilege of this page Sumit and it is restricted for all except Committers IMO. Please send me the information - I will take it from there and will update this page ASAP. -- Ashish On Tue, Sep 1, 2009 at 7:23 PM, Sumit Pandit wrote: > Thanks Ashish for commit this patch, As a next step when I hit at > http://docs.ofbiz.org/x/XxQ for update - it opened in read only mode for > my login. I think it is required specific privileges to update this > document. > Please look at it once. > > -- > Thanks And Regards > Sumit Pandit > > On 01-Sep-09, at 5:21 PM, ash...@apache.org wrote: > > Author: ashish >> Date: Tue Sep 1 11:51:29 2009 >> New Revision: 809984 >> >> URL: http://svn.apache.org/viewvc?rev=809984&view=rev >> Log: >> Applied patch from jira issue OFBIZ-2877 - Add a new field nanmed - >> "statusId" to "GlReconciliation" entity. >> Thanks Parimal & Sumit for the Contribution. >> >> Please don't forget to update the info about migration on: >> http://docs.ofbiz.org/x/XxQ. >> >> Added: >> >> ofbiz/trunk/applications/accounting/script/org/ofbiz/accounting/UpgradeServices.xml >> (with props) >> ofbiz/trunk/applications/accounting/servicedef/services_upgrade.xml >> (with props) >> Modified: >> ofbiz/trunk/applications/accounting/data/AccountingTypeData.xml >> ofbiz/trunk/applications/accounting/data/DemoGlSetupData.xml >> ofbiz/trunk/applications/accounting/entitydef/entitymodel.xml >> ofbiz/trunk/applications/accounting/ofbiz-component.xml >> >> ofbiz/trunk/applications/accounting/script/org/ofbiz/accounting/finaccount/FinAccountServices.xml >> >> ofbiz/trunk/applications/accounting/script/org/ofbiz/accounting/ledger/GeneralLedgerServices.xml >> ofbiz/trunk/applications/accounting/servicedef/secas_ledger.xml >> ofbiz/trunk/applications/accounting/servicedef/services_ledger.xml >> >> ofbiz/trunk/applications/accounting/webapp/accounting/finaccounttrans/FinAccountTrans.ftl >> ofbiz/trunk/applications/accounting/widget/FinAccountForms.xml >> ofbiz/trunk/applications/accounting/widget/GlForms.xml >> >> Modified: ofbiz/trunk/applications/accounting/data/AccountingTypeData.xml >> URL: >> http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/data/AccountingTypeData.xml?rev=809984&r1=809983&r2=809984&view=diff >> >> == >> --- ofbiz/trunk/applications/accounting/data/AccountingTypeData.xml >> (original) >> +++ ofbiz/trunk/applications/accounting/data/AccountingTypeData.xml Tue >> Sep 1 11:51:29 2009 >> @@ -1051,4 +1051,10 @@ >>> enumTypeId="STR_CRDT_ACT" hasTable="N" parentTypeId=""/> >>> enumId="FIN_ACCOUNT" sequenceId="01" enumTypeId="STR_CRDT_ACT"/> >>> enumId="BILLING_ACCOUNT" sequenceId="02" enumTypeId="STR_CRDT_ACT"/> >> + >> + >> + >> +> statusCode="CREATED" sequenceId="11" description="Created"/> >> +> statusCode="RECONCILED" sequenceId="12" description="Reconciled"/> >> +> statusIdTo="GLREC_RECONCILED" transitionName="Set Created to Reconciled"/> >> >> >> Modified: ofbiz/trunk/applications/accounting/data/DemoGlSetupData.xml >> URL: >> http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/data/DemoGlSetupData.xml?rev=809984&r1=809983&r2=809984&view=diff >> >> == >> --- ofbiz/trunk/applications/accounting/data/DemoGlSetupData.xml >> (original) >> +++ ofbiz/trunk/applications/accounting/data/DemoGlSetupData.xml Tue Sep >> 1 11:51:29 2009 >> @@ -400,8 +400,8 @@ >> >> >> >> -> glReconciliationName="demoGlReconciliation" glAccountId="00" >> organizationPartyId="Company" reconciledBalance="75000.00" >> reconciledDate="2009-08-08 20:03:14.000"/> >> -> glReconciliationName="testGlReconciliation" glAccountId="00" >> organizationPartyId="Company" reconciledDate="2009-08-12 20:03:14.000"/> >> +> glReconciliationName="demoGlReconciliation" glAccountId="00" >> statusId="GLREC_RECONCILED" organizationPartyId="Company" >> reconciledBalance="75000.00" reconciledDate="2009-08-08 20:03:14.000"/> >> +> glReconciliationName="testGlReconciliation" glAccountId="00" >> statusId="GLREC_CREATED" organizationPartyId="Company" >> reconciledDate="2009-08-12 20:03:14.000"/> >> >>> glAccountCategoryId="9301" fromDate="2009-07-08 11:54:03.8" >> amountPercentage="50"/> >>> glAccountCategoryId="9302" fromDate="2009-07-08 11:54:03.8" >> amountPercentage="20"/> >> >> Modified: ofbiz/trunk/applications/accounting/entitydef/entitymodel.xml >> URL: >> http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/entitydef/entitymodel.xml?rev=809984&r1=809983&r2=809984&view=diff >> >> == >> --- ofbiz/trunk/applications/accounting/entitydef/entitymodel.xml >> (original) >> +++ ofbiz/trunk/applications/accounting/entitydef/entitymodel.xml Tue Sep >> 1 11:51:29 2009 >> @@ -2181,6 +21
Re: action list in form inheritance
I added patch for attributes to jira ticket : https://issues.apache.org/jira/browse/OFBIZ-2889 Please review when you get a chance. I added prepend option to mirror append option earlier. This would allow child to do somethings and then hand over to parent actions. prepend form actions to list of parent form actions 'super' element is certainly powerful. One can also call super multiple times and all the nice goodies. I think power user and non power user needs need not be exlusive. One could develop 'super' element and do custom calling in leaf form. Default 'override' strategy would not come in the way. To me it is still power user and so did not build it up myself. Harmeet - Original Message - From: "Adrian Crum" To: dev@ofbiz.apache.org Sent: Tuesday, September 1, 2009 3:38:46 PM GMT -05:00 US/Canada Eastern Subject: Re: action list in form inheritance One of the nice things about an element is you can place it anywhere in the child form's actions. In other words, run some actions, call parent actions, run some more actions. -Adrian David E Jones wrote: > > I'll admit that this is fairly subjective, and one can guess at what > most people would find intuitive, but as for my subjectivity it says > that additional extends-* attributes would be better. On the other hand, > there are a lot of attributes on the form elements, but I guess that's > another topic really... > > -David > > > On Sep 1, 2009, at 11:53 AM, Harmeet Bedi wrote: > >> You have to look at form attributes to see how to extend. So seeing >> related extends attributes - extends-actions and extends-row-actions >> may help a person understand potential options with extend. >> >> I feel goal should be to help new users become more efficient and make >> behavior assumptions more visible. I feel 'super' element may help >> power users but does not reduce curve. >> >> Harmeet >> >> >> - Original Message - >> From: "Bob Morley" >> To: dev@ofbiz.apache.org >> Sent: Tuesday, September 1, 2009 10:03:01 AM GMT -05:00 US/Canada Eastern >> Subject: Re: action list in form inheritance >> >> >> I really like the super idea. Here is a proposal: >> >> - add support for the "super" element (or some reasonable name) to both >> actions and row-actions >> - add a new attribute "override" to the actions and row-actions. Its >> only >> value would be "true" (it would be nice to have attribute minimization >> here >> so we could have no attribute value) >> - if the "override" attribute is not included on an actions or >> row-actions >> block that has a parent, a warning should be produced to the developer >> informing them they should add that attribute >> >> Reasons: >> - most flexibility >> - most visibility >> - does no harm (unless you count warning messages :) ) >> >> The thing I do not like about the current approach is that you are >> going to >> bury more attributes on an already bloated form. The new attributes are >> going to have defaults (for backwards compat) so no one is going to >> set them >> anyway. These attributes, if used, should be on the rows and row-actions >> elements IMHO (but I prefer the proposal above). >> >> >> David E Jones-4 wrote: >>> >>> >>> Yes, that would be another way... ie don't call parent form actions >>> unless it is explicitly specific as opposed to calling it unless >>> something says not to call it. >>> >>> -David >>> >>> >>> On Aug 31, 2009, at 5:23 PM, Adrian Crum wrote: >>> Maybe what the actions section needs is an element that would duplicate super(). -Adrian >>> >> >> -- >> View this message in context: >> http://www.nabble.com/action-list-in-form-inheritance-tp25217949p25240756.html >> >> >> Sent from the OFBiz - Dev mailing list archive at Nabble.com. >> > >
[jira] Created: (OFBIZ-2889) action list in form inheritance
action list in form inheritance --- Key: OFBIZ-2889 URL: https://issues.apache.org/jira/browse/OFBIZ-2889 Project: OFBiz Issue Type: Improvement Reporter: Harmeet Bedi Fix For: SVN trunk Attachments: ModelForm.java.diff, widget-form.xsd.diff Purpose: make inheritance options more flexible and document them better for end user consumption. Following XSD attributes If form derives from parent, form actions may override existing parent form actions, append to parent form actions or ignore parent form actions append form actions to list of parent form actions prepend form actions to list of parent form actions If action block exists, ignore parent action list. If action block does not exist use the parent action list Ignore parent form actions. Same as override with no actions specified in actions block. same for Attaching patches for xsd and ModelForm -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2889) action list in form inheritance
[ https://issues.apache.org/jira/browse/OFBIZ-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harmeet Bedi updated OFBIZ-2889: Attachment: widget-form.xsd.diff ModelForm.java.diff > action list in form inheritance > --- > > Key: OFBIZ-2889 > URL: https://issues.apache.org/jira/browse/OFBIZ-2889 > Project: OFBiz > Issue Type: Improvement >Reporter: Harmeet Bedi > Fix For: SVN trunk > > Attachments: ModelForm.java.diff, widget-form.xsd.diff > > > Purpose: make inheritance options more flexible and document them better for > end user consumption. > Following XSD attributes > > > If form derives from parent, form actions > may > override existing parent form actions, append to parent > form actions or ignore > parent form actions > > > > > > append form actions to list of > parent form actions > > > > > prepend form actions to list of > parent form actions > > > > > If action block exists, ignore > parent action list. > If action block does not exist use > the parent action list > > > > > > Ignore parent form actions. > Same as override with no actions > specified in actions block. > > > > > > > same for > > > > Attaching patches for xsd and ModelForm -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2888) Reserved words used for field names in PaymentGatewayOrbital
Reserved words used for field names in PaymentGatewayOrbital Key: OFBIZ-2888 URL: https://issues.apache.org/jira/browse/OFBIZ-2888 Project: OFBiz Issue Type: Bug Affects Versions: SVN trunk Environment: Linux, Java 1.6, Postgresql 8.3 with driver postgresql-8.3-604.jdbc4.jar Reporter: Anne Jessel Priority: Minor On starting Rev 809782 of trunk, I see the following warnings: 2009-09-02 09:05:03,747 (main) [ DelegatorImpl.java:176:WARN ] =-=-=-=-= Found 2 warnings when checking the entity definitions: 2009-09-02 09:05:03,748 (main) [ DelegatorImpl.java:178:WARN ] [FieldNameRW] Column name PASSWORD of entity PaymentGatewayOrbital is a reserved word. 2009-09-02 09:05:03,748 (main) [ DelegatorImpl.java:178:WARN ] [FieldNameRW] Column name CLASS of entity PaymentGatewayOrbital is a reserved word. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: action list in form inheritance
One of the nice things about an element is you can place it anywhere in the child form's actions. In other words, run some actions, call parent actions, run some more actions. -Adrian David E Jones wrote: I'll admit that this is fairly subjective, and one can guess at what most people would find intuitive, but as for my subjectivity it says that additional extends-* attributes would be better. On the other hand, there are a lot of attributes on the form elements, but I guess that's another topic really... -David On Sep 1, 2009, at 11:53 AM, Harmeet Bedi wrote: You have to look at form attributes to see how to extend. So seeing related extends attributes - extends-actions and extends-row-actions may help a person understand potential options with extend. I feel goal should be to help new users become more efficient and make behavior assumptions more visible. I feel 'super' element may help power users but does not reduce curve. Harmeet - Original Message - From: "Bob Morley" To: dev@ofbiz.apache.org Sent: Tuesday, September 1, 2009 10:03:01 AM GMT -05:00 US/Canada Eastern Subject: Re: action list in form inheritance I really like the super idea. Here is a proposal: - add support for the "super" element (or some reasonable name) to both actions and row-actions - add a new attribute "override" to the actions and row-actions. Its only value would be "true" (it would be nice to have attribute minimization here so we could have no attribute value) - if the "override" attribute is not included on an actions or row-actions block that has a parent, a warning should be produced to the developer informing them they should add that attribute Reasons: - most flexibility - most visibility - does no harm (unless you count warning messages :) ) The thing I do not like about the current approach is that you are going to bury more attributes on an already bloated form. The new attributes are going to have defaults (for backwards compat) so no one is going to set them anyway. These attributes, if used, should be on the rows and row-actions elements IMHO (but I prefer the proposal above). David E Jones-4 wrote: Yes, that would be another way... ie don't call parent form actions unless it is explicitly specific as opposed to calling it unless something says not to call it. -David On Aug 31, 2009, at 5:23 PM, Adrian Crum wrote: Maybe what the actions section needs is an element that would duplicate super(). -Adrian -- View this message in context: http://www.nabble.com/action-list-in-form-inheritance-tp25217949p25240756.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Re: action list in form inheritance
I'll admit that this is fairly subjective, and one can guess at what most people would find intuitive, but as for my subjectivity it says that additional extends-* attributes would be better. On the other hand, there are a lot of attributes on the form elements, but I guess that's another topic really... -David On Sep 1, 2009, at 11:53 AM, Harmeet Bedi wrote: You have to look at form attributes to see how to extend. So seeing related extends attributes - extends-actions and extends-row-actions may help a person understand potential options with extend. I feel goal should be to help new users become more efficient and make behavior assumptions more visible. I feel 'super' element may help power users but does not reduce curve. Harmeet - Original Message - From: "Bob Morley" To: dev@ofbiz.apache.org Sent: Tuesday, September 1, 2009 10:03:01 AM GMT -05:00 US/Canada Eastern Subject: Re: action list in form inheritance I really like the super idea. Here is a proposal: - add support for the "super" element (or some reasonable name) to both actions and row-actions - add a new attribute "override" to the actions and row-actions. Its only value would be "true" (it would be nice to have attribute minimization here so we could have no attribute value) - if the "override" attribute is not included on an actions or row- actions block that has a parent, a warning should be produced to the developer informing them they should add that attribute Reasons: - most flexibility - most visibility - does no harm (unless you count warning messages :) ) The thing I do not like about the current approach is that you are going to bury more attributes on an already bloated form. The new attributes are going to have defaults (for backwards compat) so no one is going to set them anyway. These attributes, if used, should be on the rows and row- actions elements IMHO (but I prefer the proposal above). David E Jones-4 wrote: Yes, that would be another way... ie don't call parent form actions unless it is explicitly specific as opposed to calling it unless something says not to call it. -David On Aug 31, 2009, at 5:23 PM, Adrian Crum wrote: Maybe what the actions section needs is an element that would duplicate super(). -Adrian -- View this message in context: http://www.nabble.com/action-list-in-form-inheritance-tp25217949p25240756.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
[jira] Closed: (OFBIZ-2726) cannot add new requirement from workeffort screens
[ https://issues.apache.org/jira/browse/OFBIZ-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-2726. -- Resolution: Fixed Done for R4.0 at r810157 > cannot add new requirement from workeffort screens > -- > > Key: OFBIZ-2726 > URL: https://issues.apache.org/jira/browse/OFBIZ-2726 > Project: OFBiz > Issue Type: Bug >Affects Versions: Release Branch 4.0, Release Branch 9.04, SVN trunk >Reporter: chris snow >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Release Branch 4.0, Release Branch 9.04, SVN trunk > > > The workeffort app requirement screens have the option to assign an existing > requirement or create a new requirement for the work effort. However, when > trying to add a new requirement from the workeffort screens, I get the error > message: > The following required parameter is missing: > [createWorkRequirementFulfillment.requirementId] > The work around is to add the requirement through the order application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: action list in form inheritance
You have to look at form attributes to see how to extend. So seeing related extends attributes - extends-actions and extends-row-actions may help a person understand potential options with extend. I feel goal should be to help new users become more efficient and make behavior assumptions more visible. I feel 'super' element may help power users but does not reduce curve. Harmeet - Original Message - From: "Bob Morley" To: dev@ofbiz.apache.org Sent: Tuesday, September 1, 2009 10:03:01 AM GMT -05:00 US/Canada Eastern Subject: Re: action list in form inheritance I really like the super idea. Here is a proposal: - add support for the "super" element (or some reasonable name) to both actions and row-actions - add a new attribute "override" to the actions and row-actions. Its only value would be "true" (it would be nice to have attribute minimization here so we could have no attribute value) - if the "override" attribute is not included on an actions or row-actions block that has a parent, a warning should be produced to the developer informing them they should add that attribute Reasons: - most flexibility - most visibility - does no harm (unless you count warning messages :) ) The thing I do not like about the current approach is that you are going to bury more attributes on an already bloated form. The new attributes are going to have defaults (for backwards compat) so no one is going to set them anyway. These attributes, if used, should be on the rows and row-actions elements IMHO (but I prefer the proposal above). David E Jones-4 wrote: > > > Yes, that would be another way... ie don't call parent form actions > unless it is explicitly specific as opposed to calling it unless > something says not to call it. > > -David > > > On Aug 31, 2009, at 5:23 PM, Adrian Crum wrote: > >> Maybe what the actions section needs is an element that would >> duplicate super(). >> >> -Adrian >> > -- View this message in context: http://www.nabble.com/action-list-in-form-inheritance-tp25217949p25240756.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
[jira] Commented: (OFBIZ-2374) OFBiz deployment on Glassfish v2.1
[ https://issues.apache.org/jira/browse/OFBIZ-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749975#action_12749975 ] Jacques Le Roux commented on OFBIZ-2374: Hi Vadiraj, I will ASAS I will get a chance... > OFBiz deployment on Glassfish v2.1 > -- > > Key: OFBIZ-2374 > URL: https://issues.apache.org/jira/browse/OFBIZ-2374 > Project: OFBiz > Issue Type: New Feature > Components: framework > Environment: All platforms and Operating systems on which OFBiz is > known to run. >Reporter: Vadiraj Deshpande >Assignee: Jacques Le Roux > Fix For: SVN trunk > > Attachments: glassfish21.patch, glassfish21.patch, glassfish21.patch, > glassfish21_new.patch > > Original Estimate: 120h > Remaining Estimate: 120h > > First class Galssfish support for OFBiz is a required feature. For anyone who > wants to use OFBiz with Glassfish, there should be easy way to generate > configuration files and OFBiz should get deployed well on the server. This > support should match or exceed the OFBiz support for other Java EE servers > such as JBoss. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-2887) Move the migration services in proper file.
[ https://issues.apache.org/jira/browse/OFBIZ-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Vijaywargiya closed OFBIZ-2887. -- Resolution: Fixed Thanks Pairmal - Done at r810078. -- Ashish > Move the migration services in proper file. > --- > > Key: OFBIZ-2887 > URL: https://issues.apache.org/jira/browse/OFBIZ-2887 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Assignee: Ashish Vijaywargiya > Fix For: SVN trunk > > Attachments: OFBIZ-2887.patch > > > Need to move the Migration services to proper places - > Please move - migrateStatusToFinAccountTrans and migrateFixedAssetMaintMeter > to accounting -> services_upgrade.xml file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2468) Links to delete Product promo category and product promo product are not working
[ https://issues.apache.org/jira/browse/OFBIZ-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749925#action_12749925 ] Jacques Le Roux commented on OFBIZ-2468: Actually it's not the same issue I guess (after having a look at the patch) but I guess it's good anyway to keep it open as a reminder for the issue Derek signaled. > Links to delete Product promo category and product promo product are not > working > > > Key: OFBIZ-2468 > URL: https://issues.apache.org/jira/browse/OFBIZ-2468 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Release Branch 9.04, SVN trunk >Reporter: Ashish Nagar >Assignee: Ashish Vijaywargiya > Fix For: Release Branch 9.04, SVN trunk > > Attachments: EditProductPromoRules.patch, screenshot-1.jpg > > > Links to delete Product promo category and product promo product are not > working. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (OFBIZ-2468) Links to delete Product promo category and product promo product are not working
[ https://issues.apache.org/jira/browse/OFBIZ-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reopened OFBIZ-2468: Derek is right, it's not really fixed (using r810015) > Links to delete Product promo category and product promo product are not > working > > > Key: OFBIZ-2468 > URL: https://issues.apache.org/jira/browse/OFBIZ-2468 > Project: OFBiz > Issue Type: Sub-task > Components: product >Affects Versions: Release Branch 9.04, SVN trunk >Reporter: Ashish Nagar >Assignee: Ashish Vijaywargiya > Fix For: Release Branch 9.04, SVN trunk > > Attachments: EditProductPromoRules.patch, screenshot-1.jpg > > > Links to delete Product promo category and product promo product are not > working. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: action list in form inheritance
I really like the super idea. Here is a proposal: - add support for the "super" element (or some reasonable name) to both actions and row-actions - add a new attribute "override" to the actions and row-actions. Its only value would be "true" (it would be nice to have attribute minimization here so we could have no attribute value) - if the "override" attribute is not included on an actions or row-actions block that has a parent, a warning should be produced to the developer informing them they should add that attribute Reasons: - most flexibility - most visibility - does no harm (unless you count warning messages :) ) The thing I do not like about the current approach is that you are going to bury more attributes on an already bloated form. The new attributes are going to have defaults (for backwards compat) so no one is going to set them anyway. These attributes, if used, should be on the rows and row-actions elements IMHO (but I prefer the proposal above). David E Jones-4 wrote: > > > Yes, that would be another way... ie don't call parent form actions > unless it is explicitly specific as opposed to calling it unless > something says not to call it. > > -David > > > On Aug 31, 2009, at 5:23 PM, Adrian Crum wrote: > >> Maybe what the actions section needs is an element that would >> duplicate super(). >> >> -Adrian >> > -- View this message in context: http://www.nabble.com/action-list-in-form-inheritance-tp25217949p25240756.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Re: svn commit: r809984 - in /ofbiz/trunk/applications/accounting: ./ data/ entitydef/ script/org/ofbiz/accounting/ script/org/ofbiz/accounting/finaccount/ script/org/ofbiz/accounting/ledger/ serviced
Thanks Ashish for commit this patch, As a next step when I hit at http://docs.ofbiz.org/x/XxQ for update - it opened in read only mode for my login. I think it is required specific privileges to update this document. Please look at it once. -- Thanks And Regards Sumit Pandit On 01-Sep-09, at 5:21 PM, ash...@apache.org wrote: Author: ashish Date: Tue Sep 1 11:51:29 2009 New Revision: 809984 URL: http://svn.apache.org/viewvc?rev=809984&view=rev Log: Applied patch from jira issue OFBIZ-2877 - Add a new field nanmed - "statusId" to "GlReconciliation" entity. Thanks Parimal & Sumit for the Contribution. Please don't forget to update the info about migration on: http://docs.ofbiz.org/x/XxQ . Added: ofbiz/trunk/applications/accounting/script/org/ofbiz/accounting/ UpgradeServices.xml (with props) ofbiz/trunk/applications/accounting/servicedef/ services_upgrade.xml (with props) Modified: ofbiz/trunk/applications/accounting/data/AccountingTypeData.xml ofbiz/trunk/applications/accounting/data/DemoGlSetupData.xml ofbiz/trunk/applications/accounting/entitydef/entitymodel.xml ofbiz/trunk/applications/accounting/ofbiz-component.xml ofbiz/trunk/applications/accounting/script/org/ofbiz/accounting/ finaccount/FinAccountServices.xml ofbiz/trunk/applications/accounting/script/org/ofbiz/accounting/ ledger/GeneralLedgerServices.xml ofbiz/trunk/applications/accounting/servicedef/secas_ledger.xml ofbiz/trunk/applications/accounting/servicedef/services_ledger.xml ofbiz/trunk/applications/accounting/webapp/accounting/ finaccounttrans/FinAccountTrans.ftl ofbiz/trunk/applications/accounting/widget/FinAccountForms.xml ofbiz/trunk/applications/accounting/widget/GlForms.xml Modified: ofbiz/trunk/applications/accounting/data/ AccountingTypeData.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/data/AccountingTypeData.xml?rev=809984&r1=809983&r2=809984&view=diff = = = = = = = = == --- ofbiz/trunk/applications/accounting/data/AccountingTypeData.xml (original) +++ ofbiz/trunk/applications/accounting/data/AccountingTypeData.xml Tue Sep 1 11:51:29 2009 @@ -1051,4 +1051,10 @@ enumTypeId="STR_CRDT_ACT" hasTable="N" parentTypeId=""/> enumCode="FINACCOUNT" enumId="FIN_ACCOUNT" sequenceId="01" enumTypeId="STR_CRDT_ACT"/> enumCode="BILLACCOUNT" enumId="BILLING_ACCOUNT" sequenceId="02" enumTypeId="STR_CRDT_ACT"/> + + + +statusTypeId="GLREC_STATUS" statusCode="CREATED" sequenceId="11" description="Created"/> +statusTypeId="GLREC_STATUS" statusCode="RECONCILED" sequenceId="12" description="Reconciled"/> +statusIdTo="GLREC_RECONCILED" transitionName="Set Created to Reconciled"/> Modified: ofbiz/trunk/applications/accounting/data/DemoGlSetupData.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/data/DemoGlSetupData.xml?rev=809984&r1=809983&r2=809984&view=diff = = = = = = = = == --- ofbiz/trunk/applications/accounting/data/DemoGlSetupData.xml (original) +++ ofbiz/trunk/applications/accounting/data/DemoGlSetupData.xml Tue Sep 1 11:51:29 2009 @@ -400,8 +400,8 @@ fromDate="2001-01-01 00:00:00.0" conversionFactor="0.7"/> -glReconciliationName="demoGlReconciliation" glAccountId="00" organizationPartyId="Company" reconciledBalance="75000.00" reconciledDate="2009-08-08 20:03:14.000"/> -glReconciliationName="testGlReconciliation" glAccountId="00" organizationPartyId="Company" reconciledDate="2009-08-12 20:03:14.000"/> +glReconciliationName="demoGlReconciliation" glAccountId="00" statusId="GLREC_RECONCILED" organizationPartyId="Company" reconciledBalance="75000.00" reconciledDate="2009-08-08 20:03:14.000"/> +glReconciliationName="testGlReconciliation" glAccountId="00" statusId="GLREC_CREATED" organizationPartyId="Company" reconciledDate="2009-08-12 20:03:14.000"/> glAccountCategoryId="9301" fromDate="2009-07-08 11:54:03.8" amountPercentage="50"/> glAccountCategoryId="9302" fromDate="2009-07-08 11:54:03.8" amountPercentage="20"/> Modified: ofbiz/trunk/applications/accounting/entitydef/ entitymodel.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/entitydef/entitymodel.xml?rev=809984&r1=809983&r2=809984&view=diff = = = = = = = = == --- ofbiz/trunk/applications/accounting/entitydef/entitymodel.xml (original) +++ ofbiz/trunk/applications/accounting/entitydef/entitymodel.xml Tue Sep 1 11:51:29 2009 @@ -2181,6 +2181,7 @@ + @@ -2191,6 +2192,9 @@ name="Party"> name="partyId"/> + name="StatusItem"> + + http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting
Re: End of month : Main New features
Thanks guys! I just got back my ADSL connection I should be able to help a bit more... Also I feel a bit nervous, these is really something happening with this brain extension (aka web), Marshall McLuhan is so right (at least I got some time to read these last times :o) Jacques From: "Ashish Vijaywargiya" Updated the content on which I worked in last month - I see that Sumit has also provided details inside Accounting component. Thanks Sumit for taking care of that - I appreciate your help in filling that area. -- Ashish On Sun, Aug 30, 2009 at 1:34 PM, Jacques Le Roux wrote: Please devs, don't forget to add your changes in Main New features with a short explanation http://docs.ofbiz.org/display/OFBIZ/Main+New+features Thanks Jacques PS : Webslinger ?
[jira] Assigned: (OFBIZ-2887) Move the migration services in proper file.
[ https://issues.apache.org/jira/browse/OFBIZ-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Vijaywargiya reassigned OFBIZ-2887: -- Assignee: Ashish Vijaywargiya > Move the migration services in proper file. > --- > > Key: OFBIZ-2887 > URL: https://issues.apache.org/jira/browse/OFBIZ-2887 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Assignee: Ashish Vijaywargiya > Fix For: SVN trunk > > Attachments: OFBIZ-2887.patch > > > Need to move the Migration services to proper places - > Please move - migrateStatusToFinAccountTrans and migrateFixedAssetMaintMeter > to accounting -> services_upgrade.xml file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2887) Move the migration services in proper file.
[ https://issues.apache.org/jira/browse/OFBIZ-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parimal Gain updated OFBIZ-2887: Attachment: OFBIZ-2887.patch Attached patch for the work. Thanks Sumit for Reporting. > Move the migration services in proper file. > --- > > Key: OFBIZ-2887 > URL: https://issues.apache.org/jira/browse/OFBIZ-2887 > Project: OFBiz > Issue Type: Improvement > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > Attachments: OFBIZ-2887.patch > > > Need to move the Migration services to proper places - > Please move - migrateStatusToFinAccountTrans and migrateFixedAssetMaintMeter > to accounting -> services_upgrade.xml file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: End of month : Main New features
Thank you Ashish :) -- Regards Sumit Pandit On 01-Sep-09, at 6:41 PM, Ashish Vijaywargiya wrote: Updated the content on which I worked in last month - I see that Sumit has also provided details inside Accounting component. Thanks Sumit for taking care of that - I appreciate your help in filling that area. -- Ashish On Sun, Aug 30, 2009 at 1:34 PM, Jacques Le Roux >wrote: Please devs, don't forget to add your changes in Main New features with a short explanation http://docs.ofbiz.org/display/OFBIZ/Main+New+features Thanks Jacques PS : Webslinger ?
Re: End of month : Main New features
Updated the content on which I worked in last month - I see that Sumit has also provided details inside Accounting component. Thanks Sumit for taking care of that - I appreciate your help in filling that area. -- Ashish On Sun, Aug 30, 2009 at 1:34 PM, Jacques Le Roux wrote: > Please devs, don't forget to add your changes in Main New features with a > short explanation > > http://docs.ofbiz.org/display/OFBIZ/Main+New+features > > Thanks > > Jacques > PS : Webslinger ?
deleting features
In https://localhost:8443/catalog/control/EditProductFeatures?productId=FA-001 Ofbiz permits the deletion of features from product variant. Since the feature has a from/thru date, I would expect that the user would simply retire the feature if unneeded rather than deletion. Could someone confirm this? tia -- View this message in context: http://www.nabble.com/deleting-features-tp25239836p25239836.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
[jira] Commented: (OFBIZ-2884) Issue in CustomTimePeriod demo data.
[ https://issues.apache.org/jira/browse/OFBIZ-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749873#action_12749873 ] Ashish Vijaywargiya commented on OFBIZ-2884: Sumit it is done at r809990 (RB9.04). In future please select trunk & Release Branch 9.04 in "Affects Versions" & "Fix Version" blocks - This helps to understand the area where particular patch will be applied. For example please refer jira issue: https://issues.apache.org/jira/browse/OFBIZ-2840 Thanks! -- Ashish > Issue in CustomTimePeriod demo data. > > > Key: OFBIZ-2884 > URL: https://issues.apache.org/jira/browse/OFBIZ-2884 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Release Branch 9.04 >Reporter: Sumit Pandit >Assignee: Ashish Vijaywargiya > Fix For: SVN trunk > > Attachments: OFBIZ_2884.patch > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > Jira issue is created for discussion at user mailing list - subject - "Issue > in Accounting Demo Data for Entity - CustomTimePeriod". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-2877) Add a new field nanmed - "statusId" to "GlReconciliation" entity.
[ https://issues.apache.org/jira/browse/OFBIZ-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Vijaywargiya closed OFBIZ-2877. -- Resolution: Fixed Thanks Parimal & Sumit - Done at r809984. -- Ashish > Add a new field nanmed - "statusId" to "GlReconciliation" entity. > - > > Key: OFBIZ-2877 > URL: https://issues.apache.org/jira/browse/OFBIZ-2877 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Assignee: Ashish Vijaywargiya > Fix For: SVN trunk > > Attachments: OFBIZ-2877.patch, OFBIZ-2877.patch > > > Add a new field to GlReconciliation entity, statusId; Purpose to add this > field is to identify Reconciliation status - it is in Created or Reconciled > status. > This will affect in following area - > Entity changes - > 1) Update entity definition. > 2) Seed data for status - Created and Reconciled. > 3) Status Valid change. > Service Changes - > 1) Need to write a migration service which will set the status of > GlReconciliation based on following criteria - > If reconciliationBalance = null -> set status to "CREATED" > If reconciliationBalance != null -> set status to "RECONCILED" > 2) Implement a new service - setGlReconciliationStatus > 3) createGlReconciliation > on create a new GlReconciliation record set its status to default > "CREATED" if statusId not existed in parameters. > 4) createGlReconciliationEntry > It will out a optional field - statusId = RECONCILED if > GlReconcilition.statusId == CREATED. > then Call an eca from it - setGlReconciliationStatus if > parameters.statusId existed. > 5) Service which assign FinAccountTrans to GlReconciliation - Before > assignment need to verify that GlReconciliation.statusId == CREATED. > 6) Everywhere status should change by rule of StatusValid change. > UI Changes - > 1) Add a field statusId at create/update/list glreconciliation form. > 2) Assign FinAccountTrans to GlReconciliation - in dropdown show only those > GlReconciliations whose statusId == Created. > 3) And every place where it is require. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2374) OFBiz deployment on Glassfish v2.1
[ https://issues.apache.org/jira/browse/OFBIZ-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749862#action_12749862 ] Vadiraj commented on OFBIZ-2374: Hi Jacques, Thanks for your review comments. I have updated the patch. Please re-look and commit the files . Please do write to me if you have further review comments.. I would be happy to address them. :) -Vadiraj. > OFBiz deployment on Glassfish v2.1 > -- > > Key: OFBIZ-2374 > URL: https://issues.apache.org/jira/browse/OFBIZ-2374 > Project: OFBiz > Issue Type: New Feature > Components: framework > Environment: All platforms and Operating systems on which OFBiz is > known to run. >Reporter: Vadiraj Deshpande >Assignee: Jacques Le Roux > Fix For: SVN trunk > > Attachments: glassfish21.patch, glassfish21.patch, glassfish21.patch, > glassfish21_new.patch > > Original Estimate: 120h > Remaining Estimate: 120h > > First class Galssfish support for OFBiz is a required feature. For anyone who > wants to use OFBiz with Glassfish, there should be easy way to generate > configuration files and OFBiz should get deployed well on the server. This > support should match or exceed the OFBiz support for other Java EE servers > such as JBoss. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2887) Move the migration services in proper file.
Move the migration services in proper file. --- Key: OFBIZ-2887 URL: https://issues.apache.org/jira/browse/OFBIZ-2887 Project: OFBiz Issue Type: Improvement Components: accounting Affects Versions: SVN trunk Reporter: Sumit Pandit Fix For: SVN trunk Need to move the Migration services to proper places - Please move - migrateStatusToFinAccountTrans and migrateFixedAssetMaintMeter to accounting -> services_upgrade.xml file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2884) Issue in CustomTimePeriod demo data.
[ https://issues.apache.org/jira/browse/OFBIZ-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749858#action_12749858 ] Sumit Pandit commented on OFBIZ-2884: - Thank you very much Ashish for your quick commit and Jacopo for your response on mailing list, I think this should also reflect to the 9.04 please verify if possible. -- Regards Sumit Pandit > Issue in CustomTimePeriod demo data. > > > Key: OFBIZ-2884 > URL: https://issues.apache.org/jira/browse/OFBIZ-2884 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Release Branch 9.04 >Reporter: Sumit Pandit >Assignee: Ashish Vijaywargiya > Fix For: SVN trunk > > Attachments: OFBIZ_2884.patch > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > Jira issue is created for discussion at user mailing list - subject - "Issue > in Accounting Demo Data for Entity - CustomTimePeriod". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2878) Returning an exception at - FinAccount main page.
[ https://issues.apache.org/jira/browse/OFBIZ-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749857#action_12749857 ] Sumit Pandit commented on OFBIZ-2878: - Now I am not able to reporduce the bug, so move forward and will close this issue. > Returning an exception at - FinAccount main page. > - > > Key: OFBIZ-2878 > URL: https://issues.apache.org/jira/browse/OFBIZ-2878 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > > r808858 - Returning an exception at - > https://localhost:8443/accounting/control/FinAccountMain -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-2878) Returning an exception at - FinAccount main page.
[ https://issues.apache.org/jira/browse/OFBIZ-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Pandit closed OFBIZ-2878. --- Resolution: Fixed > Returning an exception at - FinAccount main page. > - > > Key: OFBIZ-2878 > URL: https://issues.apache.org/jira/browse/OFBIZ-2878 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit > Fix For: SVN trunk > > > r808858 - Returning an exception at - > https://localhost:8443/accounting/control/FinAccountMain -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2877) Add a new field nanmed - "statusId" to "GlReconciliation" entity.
[ https://issues.apache.org/jira/browse/OFBIZ-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parimal Gain updated OFBIZ-2877: Attachment: OFBIZ-2877.patch Thanks Ashish and Sumit for suggestion. Here is the updated patch with separate files for migration services in Accounting component. > Add a new field nanmed - "statusId" to "GlReconciliation" entity. > - > > Key: OFBIZ-2877 > URL: https://issues.apache.org/jira/browse/OFBIZ-2877 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Assignee: Ashish Vijaywargiya > Fix For: SVN trunk > > Attachments: OFBIZ-2877.patch, OFBIZ-2877.patch > > > Add a new field to GlReconciliation entity, statusId; Purpose to add this > field is to identify Reconciliation status - it is in Created or Reconciled > status. > This will affect in following area - > Entity changes - > 1) Update entity definition. > 2) Seed data for status - Created and Reconciled. > 3) Status Valid change. > Service Changes - > 1) Need to write a migration service which will set the status of > GlReconciliation based on following criteria - > If reconciliationBalance = null -> set status to "CREATED" > If reconciliationBalance != null -> set status to "RECONCILED" > 2) Implement a new service - setGlReconciliationStatus > 3) createGlReconciliation > on create a new GlReconciliation record set its status to default > "CREATED" if statusId not existed in parameters. > 4) createGlReconciliationEntry > It will out a optional field - statusId = RECONCILED if > GlReconcilition.statusId == CREATED. > then Call an eca from it - setGlReconciliationStatus if > parameters.statusId existed. > 5) Service which assign FinAccountTrans to GlReconciliation - Before > assignment need to verify that GlReconciliation.statusId == CREATED. > 6) Everywhere status should change by rule of StatusValid change. > UI Changes - > 1) Add a field statusId at create/update/list glreconciliation form. > 2) Assign FinAccountTrans to GlReconciliation - in dropdown show only those > GlReconciliations whose statusId == Created. > 3) And every place where it is require. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2874) improvement on human res leave management
[ https://issues.apache.org/jira/browse/OFBIZ-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwan de FERRIERES updated OFBIZ-2874: -- Attachment: partyProfile.png OFBIZ-2874.diff this new patch adds a block in the EmployeeProfile which list the employee leaves I've attached screenshots of the leave calendar and the leave block > improvement on human res leave management > - > > Key: OFBIZ-2874 > URL: https://issues.apache.org/jira/browse/OFBIZ-2874 > Project: OFBiz > Issue Type: Improvement > Components: humanres >Affects Versions: SVN trunk >Reporter: Erwan de FERRIERES >Assignee: Ashish Vijaywargiya >Priority: Minor > Fix For: SVN trunk > > Attachments: leaveCalendar.png, OFBIZ-2874.diff, OFBIZ-2874.diff, > partyProfile.png > > > For the moment in ofbiz, we only have the possibility to create leaves. > this patch will allow users to add a status on the leaves (required / > rejected / accepted / cancelled). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2886) Add support on advanced search functionality.
[ https://issues.apache.org/jira/browse/OFBIZ-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749842#action_12749842 ] Amit Sharma commented on OFBIZ-2886: Thanks to Mridul Pathak for implementation hints, Ratnesh Upadhyay for suggesting improvements and Rishi Solanki for review patch. Regards, Amit Sharma > Add support on advanced search functionality. > - > > Key: OFBIZ-2886 > URL: https://issues.apache.org/jira/browse/OFBIZ-2886 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: SVN trunk >Reporter: Amit Sharma >Priority: Minor > Fix For: SVN trunk > > Attachments: OFBIZ-2886.patch > > > Enhancement on advanced search functionality for product component. > --Add two "Internal Name" and "Product Name" field so that user can search > according to these constraints. > --Display list of all products when no constraints will be given. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2874) improvement on human res leave management
[ https://issues.apache.org/jira/browse/OFBIZ-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwan de FERRIERES updated OFBIZ-2874: -- Attachment: leaveCalendar.png > improvement on human res leave management > - > > Key: OFBIZ-2874 > URL: https://issues.apache.org/jira/browse/OFBIZ-2874 > Project: OFBiz > Issue Type: Improvement > Components: humanres >Affects Versions: SVN trunk >Reporter: Erwan de FERRIERES >Assignee: Ashish Vijaywargiya >Priority: Minor > Fix For: SVN trunk > > Attachments: leaveCalendar.png, OFBIZ-2874.diff > > > For the moment in ofbiz, we only have the possibility to create leaves. > this patch will allow users to add a status on the leaves (required / > rejected / accepted / cancelled). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2877) Add a new field nanmed - "statusId" to "GlReconciliation" entity.
[ https://issues.apache.org/jira/browse/OFBIZ-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749836#action_12749836 ] Sumit Pandit commented on OFBIZ-2877: - Thank you Parimal for patch, Here a quick change - please create a new file in Accounting component ( services_upgrade.xml) and move the Migration service in it. Thanks Ashish Vijaywargiya for your review and suggestion. > Add a new field nanmed - "statusId" to "GlReconciliation" entity. > - > > Key: OFBIZ-2877 > URL: https://issues.apache.org/jira/browse/OFBIZ-2877 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Assignee: Ashish Vijaywargiya > Fix For: SVN trunk > > Attachments: OFBIZ-2877.patch > > > Add a new field to GlReconciliation entity, statusId; Purpose to add this > field is to identify Reconciliation status - it is in Created or Reconciled > status. > This will affect in following area - > Entity changes - > 1) Update entity definition. > 2) Seed data for status - Created and Reconciled. > 3) Status Valid change. > Service Changes - > 1) Need to write a migration service which will set the status of > GlReconciliation based on following criteria - > If reconciliationBalance = null -> set status to "CREATED" > If reconciliationBalance != null -> set status to "RECONCILED" > 2) Implement a new service - setGlReconciliationStatus > 3) createGlReconciliation > on create a new GlReconciliation record set its status to default > "CREATED" if statusId not existed in parameters. > 4) createGlReconciliationEntry > It will out a optional field - statusId = RECONCILED if > GlReconcilition.statusId == CREATED. > then Call an eca from it - setGlReconciliationStatus if > parameters.statusId existed. > 5) Service which assign FinAccountTrans to GlReconciliation - Before > assignment need to verify that GlReconciliation.statusId == CREATED. > 6) Everywhere status should change by rule of StatusValid change. > UI Changes - > 1) Add a field statusId at create/update/list glreconciliation form. > 2) Assign FinAccountTrans to GlReconciliation - in dropdown show only those > GlReconciliations whose statusId == Created. > 3) And every place where it is require. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-2886) Add support on advanced search functionality.
[ https://issues.apache.org/jira/browse/OFBIZ-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Sharma updated OFBIZ-2886: --- Attachment: OFBIZ-2886.patch Here's the patch for this issue. -- Regards Amit Sharma > Add support on advanced search functionality. > - > > Key: OFBIZ-2886 > URL: https://issues.apache.org/jira/browse/OFBIZ-2886 > Project: OFBiz > Issue Type: Improvement > Components: product >Affects Versions: SVN trunk >Reporter: Amit Sharma >Priority: Minor > Fix For: SVN trunk > > Attachments: OFBIZ-2886.patch > > > Enhancement on advanced search functionality for product component. > --Add two "Internal Name" and "Product Name" field so that user can search > according to these constraints. > --Display list of all products when no constraints will be given. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2886) Add support on advanced search functionality.
Add support on advanced search functionality. - Key: OFBIZ-2886 URL: https://issues.apache.org/jira/browse/OFBIZ-2886 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: SVN trunk Reporter: Amit Sharma Priority: Minor Fix For: SVN trunk Enhancement on advanced search functionality for product component. --Add two "Internal Name" and "Product Name" field so that user can search according to these constraints. --Display list of all products when no constraints will be given. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OFBIZ-2877) Add a new field nanmed - "statusId" to "GlReconciliation" entity.
[ https://issues.apache.org/jira/browse/OFBIZ-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Vijaywargiya reassigned OFBIZ-2877: -- Assignee: Ashish Vijaywargiya > Add a new field nanmed - "statusId" to "GlReconciliation" entity. > - > > Key: OFBIZ-2877 > URL: https://issues.apache.org/jira/browse/OFBIZ-2877 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Affects Versions: SVN trunk >Reporter: Sumit Pandit >Assignee: Ashish Vijaywargiya > Fix For: SVN trunk > > Attachments: OFBIZ-2877.patch > > > Add a new field to GlReconciliation entity, statusId; Purpose to add this > field is to identify Reconciliation status - it is in Created or Reconciled > status. > This will affect in following area - > Entity changes - > 1) Update entity definition. > 2) Seed data for status - Created and Reconciled. > 3) Status Valid change. > Service Changes - > 1) Need to write a migration service which will set the status of > GlReconciliation based on following criteria - > If reconciliationBalance = null -> set status to "CREATED" > If reconciliationBalance != null -> set status to "RECONCILED" > 2) Implement a new service - setGlReconciliationStatus > 3) createGlReconciliation > on create a new GlReconciliation record set its status to default > "CREATED" if statusId not existed in parameters. > 4) createGlReconciliationEntry > It will out a optional field - statusId = RECONCILED if > GlReconcilition.statusId == CREATED. > then Call an eca from it - setGlReconciliationStatus if > parameters.statusId existed. > 5) Service which assign FinAccountTrans to GlReconciliation - Before > assignment need to verify that GlReconciliation.statusId == CREATED. > 6) Everywhere status should change by rule of StatusValid change. > UI Changes - > 1) Add a field statusId at create/update/list glreconciliation form. > 2) Assign FinAccountTrans to GlReconciliation - in dropdown show only those > GlReconciliations whose statusId == Created. > 3) And every place where it is require. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-2885) field are not set correctly
field are not set correctly --- Key: OFBIZ-2885 URL: https://issues.apache.org/jira/browse/OFBIZ-2885 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: Matarazzo Angelo Priority: Minor In component://common/widget/CommonScreens.xml#GlobalDecorator these fields are setted but component://common/webcommon/includes/header.ftl component://common/webcommon/includes/footer.ft component://common/webcommon/includes/appbar.ftl component://common/webcommon/includes/messages.ftl don't exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-2884) Issue in CustomTimePeriod demo data.
[ https://issues.apache.org/jira/browse/OFBIZ-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Vijaywargiya closed OFBIZ-2884. -- Resolution: Fixed Thanks Sumit - Done at r809913. -- Ashish > Issue in CustomTimePeriod demo data. > > > Key: OFBIZ-2884 > URL: https://issues.apache.org/jira/browse/OFBIZ-2884 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: Release Branch 9.04 >Reporter: Sumit Pandit >Assignee: Ashish Vijaywargiya > Fix For: SVN trunk > > Attachments: OFBIZ_2884.patch > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > Jira issue is created for discussion at user mailing list - subject - "Issue > in Accounting Demo Data for Entity - CustomTimePeriod". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
