how to set timeout period of service and what is the default service time out
We found in the doc : http://ofbiz.apache.org/dtds/services.xsd. xs:attribute type=xs:int name=transaction-timeout default=0/ Here it mentioned : default is 0. I found in documentation that default means System default. How to know what is the system default timeout ?. I have run the following use case to figure out how this behaves : I have created a service and open a transaction and just below create one infinite loop. Run with three use cases to 15 minutes: 1. use-transaction=true 2. use-transaction=false 3. default But in all three cases, I did not get any service timeout error. If you have any idea the provide the answer. Please any one can provide information on following : (1) What is default OFBiz service timeout? (2) Where service timeout is configured(in which config file) ? (3) Can we set timeout period for each service separately ? (4) Does ofbiz set default time period for database operation (if response from database takes more time) ? (5) In which are scenarios , ofbiz throws service timeout error ? Thanks in advance. -- View this message in context: http://www.nabble.com/how-to-set-timeout-period-of-service-and-what-is-the-default-service-time-out-tp19526162p19526162.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
[jira] Assigned: (OFBIZ-1950) Replacement of FTL TabBars with menus widgets in catalog application
[ https://issues.apache.org/jira/browse/OFBIZ-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned OFBIZ-1950: Assignee: Bilgin Ibryam Replacement of FTL TabBars with menus widgets in catalog application Key: OFBIZ-1950 URL: https://issues.apache.org/jira/browse/OFBIZ-1950 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: SVN trunk Reporter: Bruno Busco Assignee: Bilgin Ibryam Priority: Minor Attachments: catalog_tabbars.patch, catalog_tabbars.patch, catalog_tabbars.patch Hi, the attached patch replaces all *TabBar.ftl files of the catalog application with menu widgets. Using the menu widget the html is more consistent. for example the selected class is always applied to the li tag and not to the a tag of the menu. Unfortunately I am facing a problem that I have not yet solved: using menu widgets with FF3, and in some case with IE also, the catalog application pages are not displayed correctly. The content of the main area after the TabBar menu is located at the very bottom of the page, after the end of the left column content. I have seen that removing the .clear rule in the .css this is solved but then more problem come with the main menu. Any idea on how to solve this? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1950) Replacement of FTL TabBars with menus widgets in catalog application
[ https://issues.apache.org/jira/browse/OFBIZ-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam updated OFBIZ-1950: - Attachment: product.png Bruno, there is still one issue. You can see from the attached image, that the Product For doesn't appear on a new line. In the ftls, this is solved by adding an extra br/. Not sure how to do it in menu widgets. Replacement of FTL TabBars with menus widgets in catalog application Key: OFBIZ-1950 URL: https://issues.apache.org/jira/browse/OFBIZ-1950 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: SVN trunk Reporter: Bruno Busco Assignee: Bilgin Ibryam Priority: Minor Attachments: catalog_tabbars.patch, catalog_tabbars.patch, catalog_tabbars.patch, product.png Hi, the attached patch replaces all *TabBar.ftl files of the catalog application with menu widgets. Using the menu widget the html is more consistent. for example the selected class is always applied to the li tag and not to the a tag of the menu. Unfortunately I am facing a problem that I have not yet solved: using menu widgets with FF3, and in some case with IE also, the catalog application pages are not displayed correctly. The content of the main area after the TabBar menu is located at the very bottom of the page, after the end of the left column content. I have seen that removing the .clear rule in the .css this is solved but then more problem come with the main menu. Any idea on how to solve this? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Authorized.net implementation
Hi all, We are working with ofbiz and currently in a state of implementing authorize.net payment gateway. we have configured the payment .properties file as payment.authorizedotnet.url=https://certification.authorize.net/gateway/transact.dll payment.authorizedotnet.url=https://test.authorize.net/gateway/transact.dll and other parameters like user id ,password etc are all set to real values. During checkout process when we select payment method authorize.net and submit that order. we get following exception. org.ofbiz.base.util.HttpClientException: IO Error processing request (java.security.cert.CertificateException: No trusted certificate found) Is there any need of purchasing any certificate for test account ? if needed . Please provide me URL link from where to download the certificate. Please guide me how can i resolve this problem. Thanks, Harkomal -- View this message in context: http://www.nabble.com/Authorized.net-implementation-tp19529654p19529654.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Re: Authorized.net implementation
this has been discussed on the [EMAIL PROTECTED] ML where this should be. Look in the archives for July. I have CC the userlist where you can continue this. Pal InfoCom Technologies sent the following on 9/17/2008 4:31 AM: Hi all, We are working with ofbiz and currently in a state of implementing authorize.net payment gateway. we have configured the payment .properties file as payment.authorizedotnet.url=https://certification.authorize.net/gateway/transact.dll payment.authorizedotnet.url=https://test.authorize.net/gateway/transact.dll and other parameters like user id ,password etc are all set to real values. During checkout process when we select payment method authorize.net and submit that order. we get following exception. org.ofbiz.base.util.HttpClientException: IO Error processing request (java.security.cert.CertificateException: No trusted certificate found) Is there any need of purchasing any certificate for test account ? if needed . Please provide me URL link from where to download the certificate. Please guide me how can i resolve this problem. Thanks, Harkomal
[jira] Created: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
Added support for migrating FacilityRole to FacilityParty - Key: OFBIZ-1963 URL: https://issues.apache.org/jira/browse/OFBIZ-1963 Project: OFBiz Issue Type: Improvement Components: product Reporter: surya kusumakar 1) Write a migrate service to upgrade existing data from the FacilityRole entity to the new FacilityParty entity. For these, changes has been made in UI as well. 2) The FacilityRole entity has been deprecated and new entity FacilityParty is created for these changes has been made in UI and entitymodel.xml files. 3) Also add fromDate and thruDate fields to maintain records of FacilityRole entity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
[ https://issues.apache.org/jira/browse/OFBIZ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surya kusumakar updated OFBIZ-1963: --- Attachment: LatestUpdatedFacilityParty.patch This patch contains implementation of the description given above. Added support for migrating FacilityRole to FacilityParty - Key: OFBIZ-1963 URL: https://issues.apache.org/jira/browse/OFBIZ-1963 Project: OFBiz Issue Type: Improvement Components: product Reporter: surya kusumakar Priority: Minor Attachments: LatestUpdatedFacilityParty.patch 1) Write a migrate service to upgrade existing data from the FacilityRole entity to the new FacilityParty entity. For these, changes has been made in UI as well. 2) The FacilityRole entity has been deprecated and new entity FacilityParty is created for these changes has been made in UI and entitymodel.xml files. 3) Also add fromDate and thruDate fields to maintain records of FacilityRole entity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
[ https://issues.apache.org/jira/browse/OFBIZ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] surya kusumakar updated OFBIZ-1963: --- Priority: Minor (was: Major) Added support for migrating FacilityRole to FacilityParty - Key: OFBIZ-1963 URL: https://issues.apache.org/jira/browse/OFBIZ-1963 Project: OFBiz Issue Type: Improvement Components: product Reporter: surya kusumakar Priority: Minor Attachments: LatestUpdatedFacilityParty.patch 1) Write a migrate service to upgrade existing data from the FacilityRole entity to the new FacilityParty entity. For these, changes has been made in UI as well. 2) The FacilityRole entity has been deprecated and new entity FacilityParty is created for these changes has been made in UI and entitymodel.xml files. 3) Also add fromDate and thruDate fields to maintain records of FacilityRole entity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OFBIZ-1963) Added support for migrating FacilityRole to FacilityParty
[ https://issues.apache.org/jira/browse/OFBIZ-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Vijaywargiya reassigned OFBIZ-1963: -- Assignee: Ashish Vijaywargiya Added support for migrating FacilityRole to FacilityParty - Key: OFBIZ-1963 URL: https://issues.apache.org/jira/browse/OFBIZ-1963 Project: OFBiz Issue Type: Improvement Components: product Reporter: surya kusumakar Assignee: Ashish Vijaywargiya Priority: Minor Attachments: LatestUpdatedFacilityParty.patch 1) Write a migrate service to upgrade existing data from the FacilityRole entity to the new FacilityParty entity. For these, changes has been made in UI as well. 2) The FacilityRole entity has been deprecated and new entity FacilityParty is created for these changes has been made in UI and entitymodel.xml files. 3) Also add fromDate and thruDate fields to maintain records of FacilityRole entity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
TimeEntry versus WorkEffort
It seems to me that the TimeEntry entity duplicates the WorkEffort entity. Why can't a time entry be a WorkEffort of type TIME_ENTRY? I also noticed in the TimeSheet entity the fields partyId and clientPartyId. Why isn't that information kept in TimesheetRole? -Adrian
Re: TimeEntry versus WorkEffort
A basic tenet of data modeling (or the variety of it that we're shooting for with OFBiz) is to start with the concepts we want to model and then create literal entities for them and only combine two concepts when they are really similar. In the Jira issue for temporal expressions (along with various old mailing list postings) I explained why we chose to combine tasks and calendar events into a single entity: WorkEffort (which is actually a concept based on The Data Model Resource Book). In a way I think using WorkEffort for a Project is a bit of a stretch, but so far it's been fine... mostly because a Project is more or less just a very high level task. That's what matters most when considering whether to use the same or different entities is the concept behind them, and NOT whether or not they have similar fields, or even the same fields, on them. In fact, there are dozens of cases in OFBiz where entities have VERY similar fields. If you take that concept far enough you end up with a few generic entities that are reused for all sorts of things, and start to compromise and have generic field names like stringInfo1 and other meaningless terms that depend 100% on context to determine what they are and mean. Take that to the extreme and you have just 2-3 tables in your database and have rows for fields of an entity (often called an object in those cases, to further dilute the meaning of the term) instead of columns, and use a global ID plus other meta data to figure out what each row is. A TimeEntry is a very different concept from a WorkEffort, so even if we could put TimeEntry data into the WorkEffort entity we wouldn't want to. On the same note, why not use the same entity for CustRequest, Quote, Order, and Invoice? They're all pretty similar aren't they? Also, why not use the same entity for ProdCatalog, ProductCategory, and even Product... they also all have pretty similar fields While we're at it, let's have just a single EntityRole entity that replaces all *Role and *Party entities that pretty much all have the same fields... It's great to think about this sort of thing, and you can find hundreds of papers, articles, and even books along these lines. It doesn't mean it's a good direction in general for data modeling, and there are also plenty of papers, articles, and books that preach the opposite. A lot of the concepts in this direction are popular in the academic world, which makes sense because in that world people like to throw of real world constraints and practicality to explore new things. So far all they've made is a mess, and people with a more practical perspective generally don't go for it. I suppose it goes back to the seduction of ultimate flexibility... when in reality we want as many constraints as possible because more constraints limit the scope of what we have to deal with and made our jobs easier. Sorry if that's way too much of a generality... it's kind of a basic aspect of practicality IMO. -David On Sep 17, 2008, at 11:27 AM, Adrian Crum wrote: It seems to me that the TimeEntry entity duplicates the WorkEffort entity. Why can't a time entry be a WorkEffort of type TIME_ENTRY? I also noticed in the TimeSheet entity the fields partyId and clientPartyId. Why isn't that information kept in TimesheetRole? -Adrian
[jira] Commented: (OFBIZ-1955) Create a party relationship between a new customer and the product store in the eCommerce application
[ https://issues.apache.org/jira/browse/OFBIZ-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12631865#action_12631865 ] David E. Jones commented on OFBIZ-1955: --- Patrick: that sounds like a requirement that is different from a multi-tenant environment. In a multi-tenant environment they are basically using the same system, but with totally separate data sets. You're talking about divisions of a single organization that want to share data. What you're describing does lead to associating a customer with either a store or the internal organization running the store. To help clear up the design further the answer to another of the questions I asked would help: how will the data be used? In other words, what will be evaluated or when doing evaluations what data and data relationships need to be considered? Create a party relationship between a new customer and the product store in the eCommerce application - Key: OFBIZ-1955 URL: https://issues.apache.org/jira/browse/OFBIZ-1955 Project: OFBiz Issue Type: Improvement Components: ecommerce Affects Versions: SVN trunk, Release Branch 4.0 Reporter: Patrick Antivackis Assignee: Jacques Le Roux Priority: Trivial Fix For: SVN trunk Attachments: OFBIZ-1955.patch When a new user is creating its own account in an eCommerce application, a CUSTOMER profile is created to this new user, but no relationship is made between this new user and the product store. The enclosed patch will create a relationshop of type CUSTOMER_REL between the user (partyIdFrom) with the profile CUSTOMER (roleTypeIdFrom) and the data store (partyIdTo) with profile _NA_ (roleTypeIdTo) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1955) Create a party relationship between a new customer and the product store in the eCommerce application
[ https://issues.apache.org/jira/browse/OFBIZ-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12631879#action_12631879 ] Patrick Antivackis commented on OFBIZ-1955: --- In the requirement, it's important to keep the store/company owning the store (here one company has one store) that bring the customer to create an account because : - marketing campaign will first highlight the product of the initial store/company - a percent of the revenue of all the products sold by other stores/companies will be inputed in the revenue of the initial store So the important data to be evaluated is which is the store/company that bring the customer to create an account. Create a party relationship between a new customer and the product store in the eCommerce application - Key: OFBIZ-1955 URL: https://issues.apache.org/jira/browse/OFBIZ-1955 Project: OFBiz Issue Type: Improvement Components: ecommerce Affects Versions: SVN trunk, Release Branch 4.0 Reporter: Patrick Antivackis Assignee: Jacques Le Roux Priority: Trivial Fix For: SVN trunk Attachments: OFBIZ-1955.patch When a new user is creating its own account in an eCommerce application, a CUSTOMER profile is created to this new user, but no relationship is made between this new user and the product store. The enclosed patch will create a relationshop of type CUSTOMER_REL between the user (partyIdFrom) with the profile CUSTOMER (roleTypeIdFrom) and the data store (partyIdTo) with profile _NA_ (roleTypeIdTo) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: TimeEntry versus WorkEffort
David, Thank you very much for the detailed explanation. I should have re-read the chapter on Work Efforts - I had a misunderstanding of how they are used. -Adrian David E Jones wrote: A basic tenet of data modeling (or the variety of it that we're shooting for with OFBiz) is to start with the concepts we want to model and then create literal entities for them and only combine two concepts when they are really similar. In the Jira issue for temporal expressions (along with various old mailing list postings) I explained why we chose to combine tasks and calendar events into a single entity: WorkEffort (which is actually a concept based on The Data Model Resource Book). In a way I think using WorkEffort for a Project is a bit of a stretch, but so far it's been fine... mostly because a Project is more or less just a very high level task. That's what matters most when considering whether to use the same or different entities is the concept behind them, and NOT whether or not they have similar fields, or even the same fields, on them. In fact, there are dozens of cases in OFBiz where entities have VERY similar fields. If you take that concept far enough you end up with a few generic entities that are reused for all sorts of things, and start to compromise and have generic field names like stringInfo1 and other meaningless terms that depend 100% on context to determine what they are and mean. Take that to the extreme and you have just 2-3 tables in your database and have rows for fields of an entity (often called an object in those cases, to further dilute the meaning of the term) instead of columns, and use a global ID plus other meta data to figure out what each row is. A TimeEntry is a very different concept from a WorkEffort, so even if we could put TimeEntry data into the WorkEffort entity we wouldn't want to. On the same note, why not use the same entity for CustRequest, Quote, Order, and Invoice? They're all pretty similar aren't they? Also, why not use the same entity for ProdCatalog, ProductCategory, and even Product... they also all have pretty similar fields While we're at it, let's have just a single EntityRole entity that replaces all *Role and *Party entities that pretty much all have the same fields... It's great to think about this sort of thing, and you can find hundreds of papers, articles, and even books along these lines. It doesn't mean it's a good direction in general for data modeling, and there are also plenty of papers, articles, and books that preach the opposite. A lot of the concepts in this direction are popular in the academic world, which makes sense because in that world people like to throw of real world constraints and practicality to explore new things. So far all they've made is a mess, and people with a more practical perspective generally don't go for it. I suppose it goes back to the seduction of ultimate flexibility... when in reality we want as many constraints as possible because more constraints limit the scope of what we have to deal with and made our jobs easier. Sorry if that's way too much of a generality... it's kind of a basic aspect of practicality IMO. -David On Sep 17, 2008, at 11:27 AM, Adrian Crum wrote: It seems to me that the TimeEntry entity duplicates the WorkEffort entity. Why can't a time entry be a WorkEffort of type TIME_ENTRY? I also noticed in the TimeSheet entity the fields partyId and clientPartyId. Why isn't that information kept in TimesheetRole? -Adrian
Discussion: Recurring Events
I would like to start working on connecting the temporal expressions code to recurring events. Before I begin, I want to make sure I understand the requirements and where things should land. The WorkEffort entity already has a RecurrenceInfoId field, so adding a temporal expression ID field to that is obvious. What about a personal calendar? Where are those recurring events kept? They aren't related to a work effort or a work schedule. What about an employee work schedule? I want to assign an employee to work in the roof department from 8am to 5pm, Monday through Friday, with a lunch break from 12:00 to 12:30pm. Where would those recurring events go? -Adrian
Re: Discussion: Recurring Events
On Sep 17, 2008, at 2:15 PM, Adrian Crum wrote: I would like to start working on connecting the temporal expressions code to recurring events. Before I begin, I want to make sure I understand the requirements and where things should land. The WorkEffort entity already has a RecurrenceInfoId field, so adding a temporal expression ID field to that is obvious. Yep, sounds good. What about a personal calendar? Where are those recurring events kept? They aren't related to a work effort or a work schedule. Why would a personal calendar be any different from any other calendar event? Calendar events go in the WorkEffort entity. What about an employee work schedule? I want to assign an employee to work in the roof department from 8am to 5pm, Monday through Friday, with a lunch break from 12:00 to 12:30pm. Where would those recurring events go? Here's what I wrote in Jira OFBIZ-1956: To push this further, and to answer Jacques' question: the WorkEffort entity is already designed to handle work schedules using the WorkEffortType Available (ID: AVAILABLE). In addition Jacopo added some demo data that I put together for another project that shows how this would look (pretty much exactly, actually) with the old recurrence records (also in that same issue): !-- Standard Work Schedule Schedules: work availability of 8 hours per day, from Monday to Friday -- RecurrenceRule recurrenceRuleId=SCHED_STD_40HR_WK frequency=DAILY intervalNumber=1 countNumber=-1 byHourList=09,10,11,13,14,15,16,17 byDayList=MO,TU,WE,TH,FR/ RecurrenceInfo recurrenceInfoId=SCHED_STD_40HR_WK startDateTime=2008-01-01 00:00:00.000 recurrenceRuleId=SCHED_STD_40HR_WK recurrenceCount=0/ WorkEffort workEffortId=SCHED_STD_40HR_WK workEffortTypeId=AVAILABLE scopeEnumId=WES_PRIVATE workEffortName=Work Schedule Full Time (40 hrs/wk) recurrenceInfoId=SCHED_STD_40HR_WK/ For the future let's do the same thing except instead of a recurrenceInfoId on the WorkEffort have a temporalExpressionId. Does that make sense, or were you looking for something else? -David
Re: Discussion: Recurring Events
That's great input. I just wanted to make sure I didn't go in a different direction than what was already planned. Thanks! -Adrian David E Jones wrote: On Sep 17, 2008, at 2:15 PM, Adrian Crum wrote: I would like to start working on connecting the temporal expressions code to recurring events. Before I begin, I want to make sure I understand the requirements and where things should land. The WorkEffort entity already has a RecurrenceInfoId field, so adding a temporal expression ID field to that is obvious. Yep, sounds good. What about a personal calendar? Where are those recurring events kept? They aren't related to a work effort or a work schedule. Why would a personal calendar be any different from any other calendar event? Calendar events go in the WorkEffort entity. What about an employee work schedule? I want to assign an employee to work in the roof department from 8am to 5pm, Monday through Friday, with a lunch break from 12:00 to 12:30pm. Where would those recurring events go? Here's what I wrote in Jira OFBIZ-1956: To push this further, and to answer Jacques' question: the WorkEffort entity is already designed to handle work schedules using the WorkEffortType Available (ID: AVAILABLE). In addition Jacopo added some demo data that I put together for another project that shows how this would look (pretty much exactly, actually) with the old recurrence records (also in that same issue): !-- Standard Work Schedule Schedules: work availability of 8 hours per day, from Monday to Friday -- RecurrenceRule recurrenceRuleId=SCHED_STD_40HR_WK frequency=DAILY intervalNumber=1 countNumber=-1 byHourList=09,10,11,13,14,15,16,17 byDayList=MO,TU,WE,TH,FR/ RecurrenceInfo recurrenceInfoId=SCHED_STD_40HR_WK startDateTime=2008-01-01 00:00:00.000 recurrenceRuleId=SCHED_STD_40HR_WK recurrenceCount=0/ WorkEffort workEffortId=SCHED_STD_40HR_WK workEffortTypeId=AVAILABLE scopeEnumId=WES_PRIVATE workEffortName=Work Schedule Full Time (40 hrs/wk) recurrenceInfoId=SCHED_STD_40HR_WK/ For the future let's do the same thing except instead of a recurrenceInfoId on the WorkEffort have a temporalExpressionId. Does that make sense, or were you looking for something else? -David
Re: Discussion: Recurring Events
David E Jones wrote: On Sep 17, 2008, at 2:15 PM, Adrian Crum wrote: What about an employee work schedule? I want to assign an employee to work in the roof department from 8am to 5pm, Monday through Friday, with a lunch break from 12:00 to 12:30pm. Where would those recurring events go? Here's what I wrote in Jira OFBIZ-1956: To push this further, and to answer Jacques' question: the WorkEffort entity is already designed to handle work schedules using the WorkEffortType Available (ID: AVAILABLE). Wouldn't that be confusing? When someone is working they are available? It seems to me someone is available if they are *not* working. -Adrian
Re: Discussion: Recurring Events
On Sep 17, 2008, at 4:02 PM, Adrian Crum wrote: David E Jones wrote: On Sep 17, 2008, at 2:15 PM, Adrian Crum wrote: What about an employee work schedule? I want to assign an employee to work in the roof department from 8am to 5pm, Monday through Friday, with a lunch break from 12:00 to 12:30pm. Where would those recurring events go? Here's what I wrote in Jira OFBIZ-1956: To push this further, and to answer Jacques' question: the WorkEffort entity is already designed to handle work schedules using the WorkEffortType Available (ID: AVAILABLE). Wouldn't that be confusing? When someone is working they are available? It seems to me someone is available if they are *not* working. That's correct, they're not working, they're available for work. In other words those are times when events (or tasks with scheduling) can be assigned, or when looking at all tasks assigned and their estimated times how many days it will take to complete them (and when each will start, etc). -David
Re: Discussion: Recurring Events
David E Jones wrote: On Sep 17, 2008, at 4:02 PM, Adrian Crum wrote: David E Jones wrote: On Sep 17, 2008, at 2:15 PM, Adrian Crum wrote: What about an employee work schedule? I want to assign an employee to work in the roof department from 8am to 5pm, Monday through Friday, with a lunch break from 12:00 to 12:30pm. Where would those recurring events go? Here's what I wrote in Jira OFBIZ-1956: To push this further, and to answer Jacques' question: the WorkEffort entity is already designed to handle work schedules using the WorkEffortType Available (ID: AVAILABLE). Wouldn't that be confusing? When someone is working they are available? It seems to me someone is available if they are *not* working. That's correct, they're not working, they're available for work. In other words those are times when events (or tasks with scheduling) can be assigned, or when looking at all tasks assigned and their estimated times how many days it will take to complete them (and when each will start, etc). Understood. Okay, one more question (for future reference, not having to do with recurring events): In the example I gave above, I need to show that the employee is working during those hours - that they are *not* available. Is there a WorkEffortType for that? I'm coming from the perspective of production employees punching a time clock. They are supposed to be working 8am - 5pm, Monday through Friday. -Adrian
Re: Discussion: Recurring Events
On Sep 17, 2008, at 4:49 PM, Adrian Crum wrote: David E Jones wrote: On Sep 17, 2008, at 4:02 PM, Adrian Crum wrote: David E Jones wrote: On Sep 17, 2008, at 2:15 PM, Adrian Crum wrote: What about an employee work schedule? I want to assign an employee to work in the roof department from 8am to 5pm, Monday through Friday, with a lunch break from 12:00 to 12:30pm. Where would those recurring events go? Here's what I wrote in Jira OFBIZ-1956: To push this further, and to answer Jacques' question: the WorkEffort entity is already designed to handle work schedules using the WorkEffortType Available (ID: AVAILABLE). Wouldn't that be confusing? When someone is working they are available? It seems to me someone is available if they are *not* working. That's correct, they're not working, they're available for work. In other words those are times when events (or tasks with scheduling) can be assigned, or when looking at all tasks assigned and their estimated times how many days it will take to complete them (and when each will start, etc). Understood. Okay, one more question (for future reference, not having to do with recurring events): In the example I gave above, I need to show that the employee is working during those hours - that they are *not* available. Is there a WorkEffortType for that? I'm coming from the perspective of production employees punching a time clock. They are supposed to be working 8am - 5pm, Monday through Friday. What is it that they're not available for? Do you mean when they are working they are not available? In other words, they have a calendar event that makes them unavailable 8-5 M-F? -David
Re: Discussion: Recurring Events
David E Jones wrote: On Sep 17, 2008, at 4:49 PM, Adrian Crum wrote: David E Jones wrote: On Sep 17, 2008, at 4:02 PM, Adrian Crum wrote: David E Jones wrote: On Sep 17, 2008, at 2:15 PM, Adrian Crum wrote: What about an employee work schedule? I want to assign an employee to work in the roof department from 8am to 5pm, Monday through Friday, with a lunch break from 12:00 to 12:30pm. Where would those recurring events go? Here's what I wrote in Jira OFBIZ-1956: To push this further, and to answer Jacques' question: the WorkEffort entity is already designed to handle work schedules using the WorkEffortType Available (ID: AVAILABLE). Wouldn't that be confusing? When someone is working they are available? It seems to me someone is available if they are *not* working. That's correct, they're not working, they're available for work. In other words those are times when events (or tasks with scheduling) can be assigned, or when looking at all tasks assigned and their estimated times how many days it will take to complete them (and when each will start, etc). Understood. Okay, one more question (for future reference, not having to do with recurring events): In the example I gave above, I need to show that the employee is working during those hours - that they are *not* available. Is there a WorkEffortType for that? I'm coming from the perspective of production employees punching a time clock. They are supposed to be working 8am - 5pm, Monday through Friday. What is it that they're not available for? Do you mean when they are working they are not available? In other words, they have a calendar event that makes them unavailable 8-5 M-F? That's exactly what I mean. It could be I'm used to seeing things from a different perspective than what you're describing. I understand the approach you're describing - someone is available for work so their work schedule is flagged as available. The perspective I'm accustomed to is an employee is available for work when they are not already working. They are available for work when they are off. So, I have to look at it differently. An employee is off when they are not available. No big deal. It will take some getting used to. -Adrian
Re: Discussion: Recurring Events
On Sep 17, 2008, at 5:18 PM, Adrian Crum wrote: David E Jones wrote: On Sep 17, 2008, at 4:49 PM, Adrian Crum wrote: David E Jones wrote: On Sep 17, 2008, at 4:02 PM, Adrian Crum wrote: David E Jones wrote: On Sep 17, 2008, at 2:15 PM, Adrian Crum wrote: What about an employee work schedule? I want to assign an employee to work in the roof department from 8am to 5pm, Monday through Friday, with a lunch break from 12:00 to 12:30pm. Where would those recurring events go? Here's what I wrote in Jira OFBIZ-1956: To push this further, and to answer Jacques' question: the WorkEffort entity is already designed to handle work schedules using the WorkEffortType Available (ID: AVAILABLE). Wouldn't that be confusing? When someone is working they are available? It seems to me someone is available if they are *not* working. That's correct, they're not working, they're available for work. In other words those are times when events (or tasks with scheduling) can be assigned, or when looking at all tasks assigned and their estimated times how many days it will take to complete them (and when each will start, etc). Understood. Okay, one more question (for future reference, not having to do with recurring events): In the example I gave above, I need to show that the employee is working during those hours - that they are *not* available. Is there a WorkEffortType for that? I'm coming from the perspective of production employees punching a time clock. They are supposed to be working 8am - 5pm, Monday through Friday. What is it that they're not available for? Do you mean when they are working they are not available? In other words, they have a calendar event that makes them unavailable 8-5 M-F? That's exactly what I mean. It could be I'm used to seeing things from a different perspective than what you're describing. I understand the approach you're describing - someone is available for work so their work schedule is flagged as available. The perspective I'm accustomed to is an employee is available for work when they are not already working. They are available for work when they are off. So, I have to look at it differently. An employee is off when they are not available. No big deal. It will take some getting used to. If someone has nothing scheduled then all it means is we don't know anything about their schedule, and it may be that they are available for an appointment or something. If we look at their calendar and see Available type of events then we know they are available for work unless there is a specific calendar event scheduled on top of the availability which would make them unavailable. Does that help? We could change the description of this WorkEffortType to be Available for Work or something... -David
Re: [jira] Created: (OFBIZ-1962) ecommerce application
Hello Vinayak, What is purpose to create it ? If it is only for testing then please delete it. Or please post something over here. -- Thanks and Regards Sumit Pandit. HotWaxMedia, Inc http://www.hotwaxmedia.com On Sep 17, 2008, at 10:55 AM, Vinayak Yadav (JIRA) wrote: ecommerce application - Key: OFBIZ-1962 URL: https://issues.apache.org/jira/browse/OFBIZ-1962 Project: OFBiz Issue Type: New JIRA Project Components: ecommerce Affects Versions: SVN trunk Reporter: Vinayak Yadav Fix For: SVN trunk -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1962) ecommerce application
[ https://issues.apache.org/jira/browse/OFBIZ-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12632090#action_12632090 ] Ravindra Mandre commented on OFBIZ-1962: Vinayak I really do not getting that why you created this issue . If you are getting any error then post it or you need some improvement in ecommerce then please give description otherwise close it. ecommerce application - Key: OFBIZ-1962 URL: https://issues.apache.org/jira/browse/OFBIZ-1962 Project: OFBiz Issue Type: New JIRA Project Components: ecommerce Affects Versions: SVN trunk Reporter: Vinayak Yadav Fix For: SVN trunk -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
