Re: Question about OrderItem.itemDescription and Product names
Hi Jacopo Here's my opinion: 1. a null itemDescription should be fine for returns if it is fine for orders 2. productName should take be more prominent when creating a new product than internalName, so that if they are the same then the user can leave internalName blank. Then in the back-end apps if internalName is null then productName should be displayed So to clarify, instead of always having internalName set and falling back to that for customers, we should always have productName set and fall back to that for back-end users. What do you think? Scott 2008/5/21 Jacopo Cappellato <[EMAIL PROTECTED]>: > Scott, thanks for your comment... I understand your point of view. > The other options we have, if both productName and descriptions are null: > 1) put the productId in the itemDescription (but it seems not a good option > to me) or > 2) fix the code to work well with a null itemDescription > Or we may require that when we create/update the product, the productName > is set (directly or thru the content... but that would be trickier) > > H... I'm not sure which one is the best approach... probably #2 > > Jacopo > > > > > On May 20, 2008, at 9:16 PM, David E Jones wrote: > > >> Yes, this is a good point. We probably shouldn't populate something the >> customer sees with text from that field. >> >> -David >> >> >> On May 20, 2008, at 12:38 PM, Scott Gray wrote: >> >> Hi Jacopo >>> >>> It doesn't really bother me that much, but it seems funny to me that the >>> system would use something explicitly defined as internal for customer >>> facing pages. As a user I would expect that the customer would never see >>> the contents of that field. >>> >>> Regards >>> Scott >>> >>> 2008/5/21 Jacopo Cappellato <[EMAIL PROTECTED]>: >>> >>> Hi all, I've noticed that the OrderItem.itemDescription is only set if the product's productName is available; I would like to add code so that, if the productName is not set, then the internalName is used. I need this because the OrderItem.itemDescription seems to be required by some screens and some of the return procedures (I got errors trying to return orders with null itemDescriptions). Is it ok? Jacopo >> >
Re: external banking service of credit card payment (Sherlocks by Atos Origin)
Eric, I don't think you need to modify any of the OFBiz classes to implement a payment processor service. The error you are getting may be due to misconfiguration or wrong implementation for service. Thanks, Raj Eric wrote: Hello I'm trying to implement this service. I'm following the WorldPay example. In the response (file : applications/accounting/src ... /thirdparty/worldpay/SelectRespServlet.java) I get an error (line 284) because the request to modify the ORDER_PAYMENT_PREFERENCE table is a INSERT query and not an UPDATE query, so I get ERROR: duplicate key violates unique constraint "pk_order_payment_preference" How can I use an UDPATE query in order to modify the defined row (in ORDER_PAYMENT_PREFERENCE table) and update with the external credit card payment datas from the bank What class / service have I to use in order to record external payments ? Thanks
external banking service of credit card payment (Sherlocks by Atos Origin)
Hello I'm trying to implement this service. I'm following the WorldPay example. In the response (file : applications/accounting/src ... /thirdparty/worldpay/SelectRespServlet.java) I get an error (line 284) because the request to modify the ORDER_PAYMENT_PREFERENCE table is a INSERT query and not an UPDATE query, so I get ERROR: duplicate key violates unique constraint "pk_order_payment_preference" How can I use an UDPATE query in order to modify the defined row (in ORDER_PAYMENT_PREFERENCE table) and update with the external credit card payment datas from the bank What class / service have I to use in order to record external payments ? Thanks
Re: Question about OrderItem.itemDescription and Product names
We could also have a store option to let visible internal names and then use them in that case (a bit convoluted maybe ;o) Jacques From: "Jacopo Cappellato" <[EMAIL PROTECTED]> Scott, thanks for your comment... I understand your point of view. The other options we have, if both productName and descriptions are null: 1) put the productId in the itemDescription (but it seems not a good option to me) or 2) fix the code to work well with a null itemDescription Or we may require that when we create/update the product, the productName is set (directly or thru the content... but that would be trickier) H... I'm not sure which one is the best approach... probably #2 Jacopo On May 20, 2008, at 9:16 PM, David E Jones wrote: Yes, this is a good point. We probably shouldn't populate something the customer sees with text from that field. -David On May 20, 2008, at 12:38 PM, Scott Gray wrote: Hi Jacopo It doesn't really bother me that much, but it seems funny to me that the system would use something explicitly defined as internal for customer facing pages. As a user I would expect that the customer would never see the contents of that field. Regards Scott 2008/5/21 Jacopo Cappellato <[EMAIL PROTECTED]>: Hi all, I've noticed that the OrderItem.itemDescription is only set if the product's productName is available; I would like to add code so that, if the productName is not set, then the internalName is used. I need this because the OrderItem.itemDescription seems to be required by some screens and some of the return procedures (I got errors trying to return orders with null itemDescriptions). Is it ok? Jacopo
Re: Question about OrderItem.itemDescription and Product names
Scott, thanks for your comment... I understand your point of view. The other options we have, if both productName and descriptions are null: 1) put the productId in the itemDescription (but it seems not a good option to me) or 2) fix the code to work well with a null itemDescription Or we may require that when we create/update the product, the productName is set (directly or thru the content... but that would be trickier) H... I'm not sure which one is the best approach... probably #2 Jacopo On May 20, 2008, at 9:16 PM, David E Jones wrote: Yes, this is a good point. We probably shouldn't populate something the customer sees with text from that field. -David On May 20, 2008, at 12:38 PM, Scott Gray wrote: Hi Jacopo It doesn't really bother me that much, but it seems funny to me that the system would use something explicitly defined as internal for customer facing pages. As a user I would expect that the customer would never see the contents of that field. Regards Scott 2008/5/21 Jacopo Cappellato <[EMAIL PROTECTED]>: Hi all, I've noticed that the OrderItem.itemDescription is only set if the product's productName is available; I would like to add code so that, if the productName is not set, then the internalName is used. I need this because the OrderItem.itemDescription seems to be required by some screens and some of the return procedures (I got errors trying to return orders with null itemDescriptions). Is it ok? Jacopo
Re: Question about reserving inventory
If there are multiple facilities for a store and insufficient inventory in any facility reserving (back-order) against the first facility sounds like a good "stop-gap", or default solution. The problem with the multiple facility thing is that there are quite a few ways to reserve across facilities and different companies do things in different ways. Some factors include more central/larger warehouses versus those closer to the point of sale, or closer to where the order will actually be shipped, or whatever. Anyway, I think the change you propose is fine. There is a lot more work to do in this area to possibly fit the needs of a large variety of companies, but that will probably be done one company/variation at a time. With the current design implementors can also write their own multi-facility reservation routines. -David On May 20, 2008, at 10:21 AM, Bilgin Ibryam wrote: Hi all, I'd like to ask a question about "reserveStoreInventory" service. In general this service does the following: If the productStore is "oneInventoryFacility" tries to reserve the inventory in that facility. Otherwise tries to find a facility from ProductStoreFacility list with enough quantity to reserve and reserves there. The bug appears if there is no facility with enough quantities to reserve. In this case there is no reservation and the order can't be issued/invocied/completed. I think if there is no facility with enough quantity, the service should do one of (or a combination of) these 3 options: 1. Behave like productStore with "oneInventoryFacility" and tries to reserve in the facility associated to the store. 2. Take the first facility from the ProductStoreFacility list and tries to reserve there.(The first one should be ok, because there is sequenceNum field) 3. Choose a facility from the ProductStoreFacility list, which have most quantities for the product. I'd like to add code (a combination of 1 and 2) so that, if the productStore has a facilityId reserve there, otherwise choose the first facility from the list and reserve. Is it ok this way? Bilgin
Re: Discussion: move from Beanshell to Groovy
- "Tim Ruppert" <[EMAIL PROTECTED]> wrote: > Yeah - great stuff! Ean, what are your thoughts on GSP? Any other > ideas on the templating side that seem like a big win? We've settled on running Groovy events for most of our page setup that interacts with the OFBiz business logic and then dropping the result into Velocity templates. The benefit there is that Velocity is a much more constrained environment that makes it hard for people with content editing level access to access lower level controls. As you know, we've been working on a templating design that allows a more incremental development approach. We wanted to make the whole page framework a lot more malleable at runtime without requiring a lot of restarts and we have some awesome progress in that department. We definitely want to open this stuff up to the community at large and just need to get some time to produce some introductory documentation and videos so that we aren't trying to answer questions in one-on-one email. We have definitely done some new things with templating that I'm not aware of any other system offering. We've created a system of web site inheritance that allows sites to fractionally override a master template site. This is a very useful way to change the behavior of things like an ecommerce site without having to copy and modify the entire baseline. I really need to dig back into the OFBiz widgets and see what we can do to bond the FormWidget framework into our model. At the same time, I've been evaluating things like Google Gadgets and GWT to see if that is the way to go. For certain, I'm not satisfied with any of the form handling and GUI building we currently have. That's not a reflection on the quality of work that has been done, because there is tons of good stuff there, but rather where I think we need to be to compete with the cutting edge in consumer facing websites. Slight left turn, I think there is very interesting potential in building a gateway between the OFBiz party model and the Open Social initiative. It is hard to say whether that is a portal technology or a GUI technology or both. -- Ean Schuessler, CTO Brainfood.com [EMAIL PROTECTED] - http://www.brainfood.com - 214-720-0700 x 315
Re: Question about OrderItem.itemDescription and Product names
Yes, this is a good point. We probably shouldn't populate something the customer sees with text from that field. -David On May 20, 2008, at 12:38 PM, Scott Gray wrote: Hi Jacopo It doesn't really bother me that much, but it seems funny to me that the system would use something explicitly defined as internal for customer facing pages. As a user I would expect that the customer would never see the contents of that field. Regards Scott 2008/5/21 Jacopo Cappellato <[EMAIL PROTECTED]>: Hi all, I've noticed that the OrderItem.itemDescription is only set if the product's productName is available; I would like to add code so that, if the productName is not set, then the internalName is used. I need this because the OrderItem.itemDescription seems to be required by some screens and some of the return procedures (I got errors trying to return orders with null itemDescriptions). Is it ok? Jacopo
Re: Question about OrderItem.itemDescription and Product names
Hi Jacopo It doesn't really bother me that much, but it seems funny to me that the system would use something explicitly defined as internal for customer facing pages. As a user I would expect that the customer would never see the contents of that field. Regards Scott 2008/5/21 Jacopo Cappellato <[EMAIL PROTECTED]>: > Hi all, > > I've noticed that the OrderItem.itemDescription is only set if the > product's productName is available; I would like to add code so that, if the > productName is not set, then the internalName is used. > I need this because the OrderItem.itemDescription seems to be required by > some screens and some of the return procedures (I got errors trying to > return orders with null itemDescriptions). > > Is it ok? > > Jacopo > >
Re: Question about OrderItem.itemDescription and Product names
+1 On May 20, 2008, at 8:12 AM, Bilgin Ibryam wrote: we could use one of the following fields (in this order): productName description internalName + 1 Bilgin smime.p7s Description: S/MIME cryptographic signature
Question about reserving inventory
Hi all, I'd like to ask a question about "reserveStoreInventory" service. In general this service does the following: If the productStore is "oneInventoryFacility" tries to reserve the inventory in that facility. Otherwise tries to find a facility from ProductStoreFacility list with enough quantity to reserve and reserves there. The bug appears if there is no facility with enough quantities to reserve. In this case there is no reservation and the order can't be issued/invocied/completed. I think if there is no facility with enough quantity, the service should do one of (or a combination of) these 3 options: 1. Behave like productStore with "oneInventoryFacility" and tries to reserve in the facility associated to the store. 2. Take the first facility from the ProductStoreFacility list and tries to reserve there.(The first one should be ok, because there is sequenceNum field) 3. Choose a facility from the ProductStoreFacility list, which have most quantities for the product. I'd like to add code (a combination of 1 and 2) so that, if the productStore has a facilityId reserve there, otherwise choose the first facility from the list and reserve. Is it ok this way? Bilgin
Re: svn commit: r658281 - in /ofbiz/trunk/framework: base/src/base/org/ofbiz/base/util/string/ common/widget/ example/config/ example/webapp/example/WEB-INF/ example/widget/example/ images/webapp/imag
My apologies for the FlexibleStringExpander.java changes - which have
nothing to do with this commit. That was part of another project. I'll
leave them in though.
-Adrian
[EMAIL PROTECTED] wrote:
Author: adrianc
Date: Tue May 20 08:33:22 2008
New Revision: 658281
URL: http://svn.apache.org/viewvc?rev=658281&view=rev
Log:
Improved screen widget Ajax support.
The original Ajax work was a great start, but there were limitations. These
changes open things up a bit: 1) Ajax rendering falls back to plain HTML when
the user has JavaScript disabled. 2) You can have more than one area updated
during an event.
IE7 updates only elements, so be aware of that when using the Ajax
feature.
See the Example component for a demonstration.
Modified:
ofbiz/trunk/framework/base/src/base/org/ofbiz/base/util/string/FlexibleStringExpander.java
ofbiz/trunk/framework/common/widget/CommonScreens.xml
ofbiz/trunk/framework/example/config/ExampleUiLabels.xml
ofbiz/trunk/framework/example/webapp/example/WEB-INF/controller.xml
ofbiz/trunk/framework/example/widget/example/ExampleAjaxScreens.xml
ofbiz/trunk/framework/example/widget/example/ExampleForms.xml
ofbiz/trunk/framework/images/webapp/images/selectall.js
ofbiz/trunk/framework/widget/dtd/widget-form.xsd
ofbiz/trunk/framework/widget/dtd/widget-screen.xsd
ofbiz/trunk/framework/widget/src/org/ofbiz/widget/form/ModelForm.java
ofbiz/trunk/framework/widget/src/org/ofbiz/widget/html/HtmlFormRenderer.java
ofbiz/trunk/framework/widget/src/org/ofbiz/widget/html/HtmlScreenRenderer.java
ofbiz/trunk/framework/widget/src/org/ofbiz/widget/screen/ModelScreenWidget.java
Modified:
ofbiz/trunk/framework/base/src/base/org/ofbiz/base/util/string/FlexibleStringExpander.java
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/framework/base/src/base/org/ofbiz/base/util/string/FlexibleStringExpander.java?rev=658281&r1=658280&r2=658281&view=diff
==
---
ofbiz/trunk/framework/base/src/base/org/ofbiz/base/util/string/FlexibleStringExpander.java
(original)
+++
ofbiz/trunk/framework/base/src/base/org/ofbiz/base/util/string/FlexibleStringExpander.java
Tue May 20 08:33:22 2008
@@ -19,8 +19,6 @@
package org.ofbiz.base.util.string;
import java.io.Serializable;
-import java.text.DateFormat;
-import java.util.Iterator;
import java.util.LinkedList;
import java.util.List;
import java.util.Locale;
@@ -30,7 +28,6 @@
import org.ofbiz.base.util.BshUtil;
import org.ofbiz.base.util.Debug;
import org.ofbiz.base.util.ObjectType;
-import org.ofbiz.base.util.UtilDateTime;
import org.ofbiz.base.util.UtilValidate;
import org.ofbiz.base.util.collections.FlexibleMapAccessor;
import org.ofbiz.base.util.UtilFormatOut;
@@ -48,6 +45,7 @@
* and specified (XXX) currency
*
*/
[EMAIL PROTECTED]("serial")
public class FlexibleStringExpander implements Serializable {
public static final String module = FlexibleStringExpander.class.getName();
Re: External id for purchase order shipments
Bilgin, this is actually a good question... I don't know: let's see if we can get feedback from others. Jacopo On May 20, 2008, at 4:58 PM, Bilgin Ibryam wrote: Do you think that externalId could be needed also in ShipmentItem entity as it is in Order and OrderItem entities? I don't have any scenarios in mind, just asking. Bilgin
[jira] Commented: (OFBIZ-1659) Improve usability of Employment Screen
[ https://issues.apache.org/jira/browse/OFBIZ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598316#action_12598316 ] Ashish Vijaywargiya commented on OFBIZ-1659: Thanks Parimal for your patch. Your patch is in rev # 658268. -- Ashish > Improve usability of Employment Screen > -- > > Key: OFBIZ-1659 > URL: https://issues.apache.org/jira/browse/OFBIZ-1659 > Project: OFBiz > Issue Type: New Feature > Components: humanres >Reporter: Anil K Patel >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: CreateEmployee.patch, HREmployee.patch, > HREmployee.patch, Improvements.patch, Improvements.patch, Improvements.patch, > Improvements.patch, Improvements.patch, Improvements.patch, > improvements.patch, Improvements.patch, Improvements.patch, Improvements.patch > > > Following things can be done to improve usability of Employment screen. > Rename the Employment app menu to Employees > 1) Add Find/List form to find employees in system. > 2) [Create New Employee] This should give a form where we user can input > Person and Contact details and few fields from Employment table. > 3) Employment is a Party Relationship between Party Roles FROM EMPLOYEE TO > INTERNAL ORGANIZATION. To make it easy, values of these two fields should be > Defaulted to these values and I don't see need to show these fields on form. > 4) The Employment.FromPartyId field should have a Party look up that shows > only the Person. > 5) The Employment.ToPartyId field should be a drop down of Parties in > Internal Organization role. > 6) Do not show Termination type and reason fields on Create Employment forms. > 7) Add Terminate Employment button on Update Employment form. On click of > button show a Sub Form that has fields Termination type, Reason and comments > fields. > 8) The Edit form should have FromPartyId read only. > 9) Edit employee screens should have, Summary tab, Employee tab, Employment > and other tabs defined in other jira issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: External id for purchase order shipments
Do you think that externalId could be needed also in ShipmentItem entity as it is in Order and OrderItem entities? I don't have any scenarios in mind, just asking. Bilgin
[jira] Updated: (OFBIZ-1659) Improve usability of Employment Screen
[ https://issues.apache.org/jira/browse/OFBIZ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Vijaywargiya updated OFBIZ-1659: --- Attachment: Improvements.patch Patch from Parimal Gain for the removal of HumanResServices.java file . createPartyQualification service is now in MiniLang :-). -- Ashish Vijaywargiya > Improve usability of Employment Screen > -- > > Key: OFBIZ-1659 > URL: https://issues.apache.org/jira/browse/OFBIZ-1659 > Project: OFBiz > Issue Type: New Feature > Components: humanres >Reporter: Anil K Patel >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: CreateEmployee.patch, HREmployee.patch, > HREmployee.patch, Improvements.patch, Improvements.patch, Improvements.patch, > Improvements.patch, Improvements.patch, Improvements.patch, > improvements.patch, Improvements.patch, Improvements.patch, Improvements.patch > > > Following things can be done to improve usability of Employment screen. > Rename the Employment app menu to Employees > 1) Add Find/List form to find employees in system. > 2) [Create New Employee] This should give a form where we user can input > Person and Contact details and few fields from Employment table. > 3) Employment is a Party Relationship between Party Roles FROM EMPLOYEE TO > INTERNAL ORGANIZATION. To make it easy, values of these two fields should be > Defaulted to these values and I don't see need to show these fields on form. > 4) The Employment.FromPartyId field should have a Party look up that shows > only the Person. > 5) The Employment.ToPartyId field should be a drop down of Parties in > Internal Organization role. > 6) Do not show Termination type and reason fields on Create Employment forms. > 7) Add Terminate Employment button on Update Employment form. On click of > button show a Sub Form that has fields Termination type, Reason and comments > fields. > 8) The Edit form should have FromPartyId read only. > 9) Edit employee screens should have, Summary tab, Employee tab, Employment > and other tabs defined in other jira issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1659) Improve usability of Employment Screen
[ https://issues.apache.org/jira/browse/OFBIZ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598313#action_12598313 ] Ashish Vijaywargiya commented on OFBIZ-1659: Thanks Harsha Chadhar for your patch. Its in trunk rev # 658265. -- Ashish Vijaywargiya > Improve usability of Employment Screen > -- > > Key: OFBIZ-1659 > URL: https://issues.apache.org/jira/browse/OFBIZ-1659 > Project: OFBiz > Issue Type: New Feature > Components: humanres >Reporter: Anil K Patel >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: CreateEmployee.patch, HREmployee.patch, > HREmployee.patch, Improvements.patch, Improvements.patch, Improvements.patch, > Improvements.patch, Improvements.patch, improvements.patch, > Improvements.patch, Improvements.patch, Improvements.patch > > > Following things can be done to improve usability of Employment screen. > Rename the Employment app menu to Employees > 1) Add Find/List form to find employees in system. > 2) [Create New Employee] This should give a form where we user can input > Person and Contact details and few fields from Employment table. > 3) Employment is a Party Relationship between Party Roles FROM EMPLOYEE TO > INTERNAL ORGANIZATION. To make it easy, values of these two fields should be > Defaulted to these values and I don't see need to show these fields on form. > 4) The Employment.FromPartyId field should have a Party look up that shows > only the Person. > 5) The Employment.ToPartyId field should be a drop down of Parties in > Internal Organization role. > 6) Do not show Termination type and reason fields on Create Employment forms. > 7) Add Terminate Employment button on Update Employment form. On click of > button show a Sub Form that has fields Termination type, Reason and comments > fields. > 8) The Edit form should have FromPartyId read only. > 9) Edit employee screens should have, Summary tab, Employee tab, Employment > and other tabs defined in other jira issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1659) Improve usability of Employment Screen
[ https://issues.apache.org/jira/browse/OFBIZ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Vijaywargiya updated OFBIZ-1659: --- Attachment: Improvements.patch Patch from Harsha Chadhar to improve the usability in PartySkills and Employement Application tab in HR. -- Ashish > Improve usability of Employment Screen > -- > > Key: OFBIZ-1659 > URL: https://issues.apache.org/jira/browse/OFBIZ-1659 > Project: OFBiz > Issue Type: New Feature > Components: humanres >Reporter: Anil K Patel >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: CreateEmployee.patch, HREmployee.patch, > HREmployee.patch, Improvements.patch, Improvements.patch, Improvements.patch, > Improvements.patch, Improvements.patch, improvements.patch, > Improvements.patch, Improvements.patch, Improvements.patch > > > Following things can be done to improve usability of Employment screen. > Rename the Employment app menu to Employees > 1) Add Find/List form to find employees in system. > 2) [Create New Employee] This should give a form where we user can input > Person and Contact details and few fields from Employment table. > 3) Employment is a Party Relationship between Party Roles FROM EMPLOYEE TO > INTERNAL ORGANIZATION. To make it easy, values of these two fields should be > Defaulted to these values and I don't see need to show these fields on form. > 4) The Employment.FromPartyId field should have a Party look up that shows > only the Person. > 5) The Employment.ToPartyId field should be a drop down of Parties in > Internal Organization role. > 6) Do not show Termination type and reason fields on Create Employment forms. > 7) Add Terminate Employment button on Update Employment form. On click of > button show a Sub Form that has fields Termination type, Reason and comments > fields. > 8) The Edit form should have FromPartyId read only. > 9) Edit employee screens should have, Summary tab, Employee tab, Employment > and other tabs defined in other jira issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r658251 - in /ofbiz/trunk/applications/humanres/entitydef: entitygroup.xml entitymodel.xml
Thanks Vikas for taking care of this and thanks to you Scott for reporting it. -- Ashish On Tue, May 20, 2008 at 10:04 AM, <[EMAIL PROTECTED]> wrote: > Author: mor > Date: Tue May 20 07:04:23 2008 > New Revision: 658251 > > URL: http://svn.apache.org/viewvc?rev=658251&view=rev > Log: > Removing RateType entity as it is already defined in workeffort component. > Thanks Scott for reporting > > Modified: >ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml >ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml > > Modified: ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml > URL: > http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml?rev=658251&r1=658250&r2=658251&view=diff > > == > --- ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml (original) > +++ ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml Tue May 20 > 07:04:23 2008 > @@ -69,7 +69,6 @@ > > > > - > > > > > Modified: ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml > URL: > http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml?rev=658251&r1=658250&r2=658251&view=diff > > == > --- ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml (original) > +++ ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml Tue May 20 > 07:04:23 2008 > @@ -702,12 +702,4 @@ > > > > - -package-name="org.ofbiz.humanres.position" > -title="Rate Type Entity"> > - > - > - > - > - > - > + > \ No newline at end of file > > >
What for is used Product.facilityId field?
I can't see this field used anywhere, but I'd like to know what is the purpose of this field? Is it deprecated? Bilgin
Re: Question about OrderItem.itemDescription and Product names
Yes, sounds quite logical Jacques From: "Tim Ruppert" <[EMAIL PROTECTED]> +1 - we have people who like to use the description (not the long description), so that could be an interesting fall back if you don't find either :) - although most people with populate that productName. Cheers, Tim -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6595 On May 20, 2008, at 7:44 AM, Jacopo Cappellato wrote: Hi all, I've noticed that the OrderItem.itemDescription is only set if the product's productName is available; I would like to add code so that, if the productName is not set, then the internalName is used. I need this because the OrderItem.itemDescription seems to be required by some screens and some of the return procedures (I got errors trying to return orders with null itemDescriptions). Is it ok? Jacopo
Re: External id for purchase order shipments
+1 Jacques From: "Jacopo Cappellato" <[EMAIL PROTECTED]> Hi all, what about adding the field: Shipment.externalId that could be used to enter the supplier's external shipment id? It could be useful information to keep track and a record of incoming shipments. Jacopo
Re: Question about OrderItem.itemDescription and Product names
> we could use one of the following fields (in this order): > productName > description > internalName + 1 Bilgin
Re: svn commit: r657085 - in /ofbiz/trunk/applications/humanres: data/HumanResTypeData.xml entitydef/entitygroup.xml entitydef/entitymodel.xml
Thanks Scott, Fixed in rev. 658251. Vikas On Tue, May 20, 2008 at 5:02 PM, Scott Gray <[EMAIL PROTECTED]> wrote: > Hi Ashish > > The RateType entity is already defined in the workeffort app, so warnings > are being thrown when ofbiz starts. > > Regards > Scott > > 2008/5/17 <[EMAIL PROTECTED]>: > > > Author: ashish > > Date: Fri May 16 07:40:22 2008 > > New Revision: 657085 > > > > URL: http://svn.apache.org/viewvc?rev=657085&view=rev > > Log: > > Applied patch from JIRA issue :- > > https://issues.apache.org/jira/browse/OFBIZ-1659. > > > > Following things are covered in this patch :- > > 1) Created Entities PositionTypeRate and RateType. > > (Details of entities are taken from Data Model Resource Book 1) > > 2) Added the sample data for the BenefitType entity. > > > > > > Thanks Parimal Gain for your patch. > > > > Modified: > >ofbiz/trunk/applications/humanres/data/HumanResTypeData.xml > >ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml > >ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml > > > > Modified: ofbiz/trunk/applications/humanres/data/HumanResTypeData.xml > > URL: > > > http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/data/HumanResTypeData.xml?rev=657085&r1=657084&r2=657085&view=diff > > > > > == > > --- ofbiz/trunk/applications/humanres/data/HumanResTypeData.xml > (original) > > +++ ofbiz/trunk/applications/humanres/data/HumanResTypeData.xml Fri May > 16 > > 07:40:22 2008 > > @@ -51,4 +51,8 @@ > > > parentTypeId="" statusTypeId="RES_MGMT"/> > > > parentTypeId="" statusTypeId="PROD_MGMT"/> > > > parentTypeId="" statusTypeId="SALES_MGMT"/> > > + > > + > benefitTypeId="HEALTH"/> > > + > benefitTypeId="VACATION"/> > > + > benefitTypeId="SICK_LEAVE"/> > > > > > > Modified: ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml > > URL: > > > http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml?rev=657085&r1=657084&r2=657085&view=diff > > > > > == > > --- ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml > (original) > > +++ ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml Fri May > 16 > > 07:40:22 2008 > > @@ -68,6 +68,8 @@ > > > > > > > > + > > + > > > > > > > > > > Modified: ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml > > URL: > > > http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml?rev=657085&r1=657084&r2=657085&view=diff > > > > > == > > --- ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml > (original) > > +++ ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml Fri May > 16 > > 07:40:22 2008 > > @@ -687,5 +687,38 @@ > > > > > > > > + > +package-name="org.ofbiz.humanres.position" > > +title="EmplPosition Type Rate Entity"> > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > rel-entity-name="EmplPositionType"> > > + > > + > > + > rel-entity-name="PeriodType"> > > + > > + > > + > rel-entity-name="SalaryStep"> > > + > > + > > + > > + > rel-entity-name="RateType"> > > + > > + > > + > > + > +package-name="org.ofbiz.humanres.position" > > +title="Rate Type Entity"> > > + > > + > > + > > + > > > > > > > > > > >
Re: Question about OrderItem.itemDescription and Product names
Tim, thanks for your comment; we could use one of the following fields (in this order): productName description internalName What do you think? Jacopo On May 20, 2008, at 3:51 PM, Tim Ruppert wrote: +1 - we have people who like to use the description (not the long description), so that could be an interesting fall back if you don't find either :) - although most people with populate that productName. Cheers, Tim -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6595 On May 20, 2008, at 7:44 AM, Jacopo Cappellato wrote: Hi all, I've noticed that the OrderItem.itemDescription is only set if the product's productName is available; I would like to add code so that, if the productName is not set, then the internalName is used. I need this because the OrderItem.itemDescription seems to be required by some screens and some of the return procedures (I got errors trying to return orders with null itemDescriptions). Is it ok? Jacopo
Re: Is OFBiz for Redhat too??
Please use rather user ML for such questions : http://docs.ofbiz.org/display/OFBADMIN/Mailing+Lists#MailingLists-DeveloperList:dev@ofbiz.apache.org Thanks Jacques From: "Ajay @ Pal InfoCom" <[EMAIL PROTECTED]> Hello developers, I have a query, can we use OFBiz on RedHat Linux too? Because we want to use RedHat platform and are not sure on this, whether it will work or not. Any response will be appreciated. Thanks and regards, Ajay Sodhi
Re: Question about OrderItem.itemDescription and Product names
+1 - we have people who like to use the description (not the long description), so that could be an interesting fall back if you don't find either :) - although most people with populate that productName. Cheers, Tim -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6595 On May 20, 2008, at 7:44 AM, Jacopo Cappellato wrote: Hi all, I've noticed that the OrderItem.itemDescription is only set if the product's productName is available; I would like to add code so that, if the productName is not set, then the internalName is used. I need this because the OrderItem.itemDescription seems to be required by some screens and some of the return procedures (I got errors trying to return orders with null itemDescriptions). Is it ok? Jacopo smime.p7s Description: S/MIME cryptographic signature
External id for purchase order shipments
Hi all, what about adding the field: Shipment.externalId that could be used to enter the supplier's external shipment id? It could be useful information to keep track and a record of incoming shipments. Jacopo
Question about OrderItem.itemDescription and Product names
Hi all, I've noticed that the OrderItem.itemDescription is only set if the product's productName is available; I would like to add code so that, if the productName is not set, then the internalName is used. I need this because the OrderItem.itemDescription seems to be required by some screens and some of the return procedures (I got errors trying to return orders with null itemDescriptions). Is it ok? Jacopo
[jira] Updated: (OFBIZ-1649) Create a Contact from vCard
[ https://issues.apache.org/jira/browse/OFBIZ-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Mayur updated OFBIZ-1649: --- Attachment: jpim-0.1.jar > Create a Contact from vCard > --- > > Key: OFBIZ-1649 > URL: https://issues.apache.org/jira/browse/OFBIZ-1649 > Project: OFBiz > Issue Type: New Feature >Reporter: Anil K Patel >Assignee: Vikas Mayur >Priority: Minor > Attachments: jpim-0.1.jar, license.patch, vCard.patch, vCard_gui.patch > > > Implement support for creating Contact from vCard. JPIM project has a lib > under BSD style license that can be used. > http://jpim.sourceforge.net/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1649) Create a Contact from vCard
[ https://issues.apache.org/jira/browse/OFBIZ-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Mayur updated OFBIZ-1649: --- Attachment: license.patch > Create a Contact from vCard > --- > > Key: OFBIZ-1649 > URL: https://issues.apache.org/jira/browse/OFBIZ-1649 > Project: OFBiz > Issue Type: New Feature >Reporter: Anil K Patel >Assignee: Vikas Mayur >Priority: Minor > Attachments: license.patch, vCard.patch, vCard_gui.patch > > > Implement support for creating Contact from vCard. JPIM project has a lib > under BSD style license that can be used. > http://jpim.sourceforge.net/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1649) Create a Contact from vCard
[ https://issues.apache.org/jira/browse/OFBIZ-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598277#action_12598277 ] Vikas Mayur commented on OFBIZ-1649: vCard.patch, This patch is about adding import / export vCard functionality in SFA. This can also be extended to party component view profile screen. > Create a Contact from vCard > --- > > Key: OFBIZ-1649 > URL: https://issues.apache.org/jira/browse/OFBIZ-1649 > Project: OFBiz > Issue Type: New Feature >Reporter: Anil K Patel >Assignee: Vikas Mayur >Priority: Minor > Attachments: vCard.patch, vCard_gui.patch > > > Implement support for creating Contact from vCard. JPIM project has a lib > under BSD style license that can be used. > http://jpim.sourceforge.net/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Discussion: move from Beanshell to Groovy
Yeah - great stuff! Ean, what are your thoughts on GSP? Any other ideas on the templating side that seem like a big win? Cheers, Tim -- Tim Ruppert HotWax Media http://www.hotwaxmedia.com o:801.649.6594 f:801.649.6595 On May 19, 2008, at 10:58 AM, Ean Schuessler wrote: - "Jacques Le Roux" <[EMAIL PROTECTED]> wrote: I know at least one OFBiz project which is already using groovy, this will please these folks ! I know we're happy to hear about it! Adam and I have been talking for a while about stuff like: ofbiz.services.createPerson([firstName: 'John', lastName: 'Doe']) -- Ean Schuessler, CTO Brainfood.com [EMAIL PROTECTED] - http://www.brainfood.com - 214-720-0700 x 315 smime.p7s Description: S/MIME cryptographic signature
[jira] Updated: (OFBIZ-1649) Create a Contact from vCard
[ https://issues.apache.org/jira/browse/OFBIZ-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vikas Mayur updated OFBIZ-1649: --- Attachment: vCard.patch > Create a Contact from vCard > --- > > Key: OFBIZ-1649 > URL: https://issues.apache.org/jira/browse/OFBIZ-1649 > Project: OFBiz > Issue Type: New Feature >Reporter: Anil K Patel >Assignee: Vikas Mayur >Priority: Minor > Attachments: vCard.patch, vCard_gui.patch > > > Implement support for creating Contact from vCard. JPIM project has a lib > under BSD style license that can be used. > http://jpim.sourceforge.net/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Is OFBiz for Redhat too??
Hello Ajay, ofBIZ is very flexible and compatible with Linux (any distribution). here, we are working with Cent OS 5 and Ubuntu 7.10 (both rpm and debian).so that, there is not any problem with RedHat becoz logically RedHat and Cent OS are same.you can do it with RedHat. if any problem persist ask here. Thanks Kapil Singh Kushwah, Linux System Administrator HotWax Media Inc. Indore
Re: Is OFBiz for Redhat too??
Yes, you can use Redhat Linux to deploy Ofbiz. Theoretically, you can deploy OFBiz only any platform which run Java 5.0 as OFBiz is a 100% Java application. Raj Ajay @ Pal InfoCom wrote: Hello developers, I have a query, can we use OFBiz on RedHat Linux too? Because we want to use RedHat platform and are not sure on this, whether it will work or not. Any response will be appreciated. Thanks and regards, Ajay Sodhi
Re: svn commit: r657085 - in /ofbiz/trunk/applications/humanres: data/HumanResTypeData.xml entitydef/entitygroup.xml entitydef/entitymodel.xml
Hi Ashish The RateType entity is already defined in the workeffort app, so warnings are being thrown when ofbiz starts. Regards Scott 2008/5/17 <[EMAIL PROTECTED]>: > Author: ashish > Date: Fri May 16 07:40:22 2008 > New Revision: 657085 > > URL: http://svn.apache.org/viewvc?rev=657085&view=rev > Log: > Applied patch from JIRA issue :- > https://issues.apache.org/jira/browse/OFBIZ-1659. > > Following things are covered in this patch :- > 1) Created Entities PositionTypeRate and RateType. > (Details of entities are taken from Data Model Resource Book 1) > 2) Added the sample data for the BenefitType entity. > > > Thanks Parimal Gain for your patch. > > Modified: >ofbiz/trunk/applications/humanres/data/HumanResTypeData.xml >ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml >ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml > > Modified: ofbiz/trunk/applications/humanres/data/HumanResTypeData.xml > URL: > http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/data/HumanResTypeData.xml?rev=657085&r1=657084&r2=657085&view=diff > > == > --- ofbiz/trunk/applications/humanres/data/HumanResTypeData.xml (original) > +++ ofbiz/trunk/applications/humanres/data/HumanResTypeData.xml Fri May 16 > 07:40:22 2008 > @@ -51,4 +51,8 @@ > parentTypeId="" statusTypeId="RES_MGMT"/> > parentTypeId="" statusTypeId="PROD_MGMT"/> > parentTypeId="" statusTypeId="SALES_MGMT"/> > + > + benefitTypeId="HEALTH"/> > + benefitTypeId="VACATION"/> > + benefitTypeId="SICK_LEAVE"/> > > > Modified: ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml > URL: > http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml?rev=657085&r1=657084&r2=657085&view=diff > > == > --- ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml (original) > +++ ofbiz/trunk/applications/humanres/entitydef/entitygroup.xml Fri May 16 > 07:40:22 2008 > @@ -68,6 +68,8 @@ > > > > + > + > > > > > Modified: ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml > URL: > http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml?rev=657085&r1=657084&r2=657085&view=diff > > == > --- ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml (original) > +++ ofbiz/trunk/applications/humanres/entitydef/entitymodel.xml Fri May 16 > 07:40:22 2008 > @@ -687,5 +687,38 @@ > > > > + +package-name="org.ofbiz.humanres.position" > +title="EmplPosition Type Rate Entity"> > + > + > + > + > + > + > + > + > + > + rel-entity-name="EmplPositionType"> > + > + > + rel-entity-name="PeriodType"> > + > + > + rel-entity-name="SalaryStep"> > + > + > + > + rel-entity-name="RateType"> > + > + > + > + +package-name="org.ofbiz.humanres.position" > +title="Rate Type Entity"> > + > + > + > + > > > > >
Is OFBiz for Redhat too??
Hello developers, I have a query, can we use OFBiz on RedHat Linux too? Because we want to use RedHat platform and are not sure on this, whether it will work or not. Any response will be appreciated. Thanks and regards, Ajay Sodhi
Re: POS
Please Opentaps forums for Opentaps questions Jacques From: "dileepdd" <[EMAIL PROTECTED]> Hi all, I am new to the erp product. Actually i am not able to view the point of sale module it is disabled in the open taps i configure the applications/accounting/config/payment.properties file as mentioned in the opentaps manual. payment.authorizedotnet.login=6zz6m5N4Et payment.authorizedotnet.trankey=9V9wUv6Yd92t27t5 payment.authorizedotnet.test=FALSE But i am not able to view the point of sale module. So please tell the total steps to enable the module so please do the need full this is my mail id : [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/POS-tp15305335p17336208.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
[jira] Commented: (OFBIZ-1659) Improve usability of Employment Screen
[ https://issues.apache.org/jira/browse/OFBIZ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598243#action_12598243 ] Ashish Vijaywargiya commented on OFBIZ-1659: Thanks Parimal Gain for your patch. Your patch is in rev # 658193. -- Ashish Vijaywargiya > Improve usability of Employment Screen > -- > > Key: OFBIZ-1659 > URL: https://issues.apache.org/jira/browse/OFBIZ-1659 > Project: OFBiz > Issue Type: New Feature > Components: humanres >Reporter: Anil K Patel >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: CreateEmployee.patch, HREmployee.patch, > HREmployee.patch, Improvements.patch, Improvements.patch, Improvements.patch, > Improvements.patch, improvements.patch, Improvements.patch, > Improvements.patch, Improvements.patch > > > Following things can be done to improve usability of Employment screen. > Rename the Employment app menu to Employees > 1) Add Find/List form to find employees in system. > 2) [Create New Employee] This should give a form where we user can input > Person and Contact details and few fields from Employment table. > 3) Employment is a Party Relationship between Party Roles FROM EMPLOYEE TO > INTERNAL ORGANIZATION. To make it easy, values of these two fields should be > Defaulted to these values and I don't see need to show these fields on form. > 4) The Employment.FromPartyId field should have a Party look up that shows > only the Person. > 5) The Employment.ToPartyId field should be a drop down of Parties in > Internal Organization role. > 6) Do not show Termination type and reason fields on Create Employment forms. > 7) Add Terminate Employment button on Update Employment form. On click of > button show a Sub Form that has fields Termination type, Reason and comments > fields. > 8) The Edit form should have FromPartyId read only. > 9) Edit employee screens should have, Summary tab, Employee tab, Employment > and other tabs defined in other jira issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1659) Improve usability of Employment Screen
[ https://issues.apache.org/jira/browse/OFBIZ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] parimal gain updated OFBIZ-1659: Attachment: Improvements.patch This patch contains task related to Resume , Qualification , for HR Thanks & Ragards Parimal Gain > Improve usability of Employment Screen > -- > > Key: OFBIZ-1659 > URL: https://issues.apache.org/jira/browse/OFBIZ-1659 > Project: OFBiz > Issue Type: New Feature > Components: humanres >Reporter: Anil K Patel >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: CreateEmployee.patch, HREmployee.patch, > HREmployee.patch, Improvements.patch, Improvements.patch, Improvements.patch, > Improvements.patch, improvements.patch, Improvements.patch, > Improvements.patch, Improvements.patch > > > Following things can be done to improve usability of Employment screen. > Rename the Employment app menu to Employees > 1) Add Find/List form to find employees in system. > 2) [Create New Employee] This should give a form where we user can input > Person and Contact details and few fields from Employment table. > 3) Employment is a Party Relationship between Party Roles FROM EMPLOYEE TO > INTERNAL ORGANIZATION. To make it easy, values of these two fields should be > Defaulted to these values and I don't see need to show these fields on form. > 4) The Employment.FromPartyId field should have a Party look up that shows > only the Person. > 5) The Employment.ToPartyId field should be a drop down of Parties in > Internal Organization role. > 6) Do not show Termination type and reason fields on Create Employment forms. > 7) Add Terminate Employment button on Update Employment form. On click of > button show a Sub Form that has fields Termination type, Reason and comments > fields. > 8) The Edit form should have FromPartyId read only. > 9) Edit employee screens should have, Summary tab, Employee tab, Employment > and other tabs defined in other jira issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: POS
Hi all, I am new to the erp product. Actually i am not able to view the point of sale module it is disabled in the open taps i configure the applications/accounting/config/payment.properties file as mentioned in the opentaps manual. payment.authorizedotnet.login=6zz6m5N4Et payment.authorizedotnet.trankey=9V9wUv6Yd92t27t5 payment.authorizedotnet.test=FALSE But i am not able to view the point of sale module. So please tell the total steps to enable the module so please do the need full this is my mail id : [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/POS-tp15305335p17336208.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
[jira] Updated: (OFBIZ-1782) Junit Test case for purchase order receipts...
[ https://issues.apache.org/jira/browse/OFBIZ-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Pandit updated OFBIZ-1782: Attachment: TestCaseForPOReceipts.patch Here is the patch for the test case. Kindly have a look on it. > Junit Test case for purchase order receipts... > -- > > Key: OFBIZ-1782 > URL: https://issues.apache.org/jira/browse/OFBIZ-1782 > Project: OFBiz > Issue Type: Sub-task >Reporter: Sumit Pandit > Attachments: TestCaseForPOReceipts.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1659) Improve usability of Employment Screen
[ https://issues.apache.org/jira/browse/OFBIZ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598206#action_12598206 ] Ashish Vijaywargiya commented on OFBIZ-1659: Thanks Awdesh Parihar for your patch. Your patch is in Rev # 658129. -- Ashish Vijaywargiya > Improve usability of Employment Screen > -- > > Key: OFBIZ-1659 > URL: https://issues.apache.org/jira/browse/OFBIZ-1659 > Project: OFBiz > Issue Type: New Feature > Components: humanres >Reporter: Anil K Patel >Assignee: Ashish Vijaywargiya >Priority: Minor > Attachments: CreateEmployee.patch, HREmployee.patch, > HREmployee.patch, Improvements.patch, Improvements.patch, Improvements.patch, > improvements.patch, Improvements.patch, Improvements.patch, Improvements.patch > > > Following things can be done to improve usability of Employment screen. > Rename the Employment app menu to Employees > 1) Add Find/List form to find employees in system. > 2) [Create New Employee] This should give a form where we user can input > Person and Contact details and few fields from Employment table. > 3) Employment is a Party Relationship between Party Roles FROM EMPLOYEE TO > INTERNAL ORGANIZATION. To make it easy, values of these two fields should be > Defaulted to these values and I don't see need to show these fields on form. > 4) The Employment.FromPartyId field should have a Party look up that shows > only the Person. > 5) The Employment.ToPartyId field should be a drop down of Parties in > Internal Organization role. > 6) Do not show Termination type and reason fields on Create Employment forms. > 7) Add Terminate Employment button on Update Employment form. On click of > button show a Sub Form that has fields Termination type, Reason and comments > fields. > 8) The Edit form should have FromPartyId read only. > 9) Edit employee screens should have, Summary tab, Employee tab, Employment > and other tabs defined in other jira issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
