[OCA]12567 Location structure needs to reflect hierarchy of Buildings #22
Conversation
[ADD] fieldservice 0.0.1 (#2) [UPD] addons table in README.md [ci skip] [UPD] README.rst [ADD] setup.py REDCOR.md should list redcor enhancements [IMP] README: explain what is FSM [ADD] Vehicle (OCA#23) * [ADD] Vehicle [OCA]12567 Location structure needs to reflect hierarchy of Buildings (OCA#22) * [IMP] Extend fsm.location object [UPD] README.rst [FIX] View [ADD] red_fsm base, team handler Option for enabling the red_fsm teams, new mwnu added under fieldservice settings to use red_fsm teams. Removed incomplete method [ADD] stages and stage sets add website_support module change module structure [removed] remove website_support module, modified labels for fields and menu modifications, cleaned code Advanced stage transitions, option to add stage transitions for the stage sets Tickets base. Support ticket base form, mail notification to employees and customers, etc team: basic skills, person basic skills. Tickets: ticket from website adjusted indentation added plone code as a sample team handler
…OCA#22) * [IMP] Extend fsm.location object
|
We're building a bloated monolithic module here. |
|
That was also my comment on #23 |
|
I can see that with specific workflows, a building hierarchy is not needed. However, I had several customers who needed more details. when I worked with UPS and FedEx and large Utility companies one of the key problem was that the delivery or service point is often not the address point but a different location. The good thing about the model is that all the fields are optional. It would be great to have a configuration setting to turn some detailed location fields on/off. |
|
In my past experience in service management / plant maintenance in SAP this would be done using a hierarchical structure, like the concept of Location in stock. In SAP they call it "Technical Location". And you can define a hierarchical tree that maps to physical places. The location does not necessarily need to be within your company. IMHO adding so many fields as in this PR is never going to solve all the problems, whereas adding the field "Technical Location" would do. |
|
I remember (a little fuzzy) using both functional and technical location for elevator equipment location representation. If I understand your suggestion you would like a generic, flexible hierarchy that allows us to define any "technical location" and tie it to a parent record (either another technical location or a functional location. Max and I are working with a customer right now who needs the details - we can see if this makes sense. I like the suggestion. |
|
A Location hierarchy is important. But that’s not what’s happening here. |
|
Please review #27 |
…OCA#22) * [IMP] Extend fsm.location object
[IMP] Fieldservice : raising a Validation Error if the sale order FSM location is empty and any sale order lines are set to any of the field service tracking options
…OCA#22) * [IMP] Extend fsm.location object
…OCA#22) * [IMP] Extend fsm.location object
…#22) * [IMP] Extend fsm.location object
…#22) * [IMP] Extend fsm.location object
…OCA#22) * [IMP] Extend fsm.location object
…OCA#22) * [IMP] Extend fsm.location object
…OCA#22) * [IMP] Extend fsm.location object
…OCA#22) * [IMP] Extend fsm.location object
…#22) * [IMP] Extend fsm.location object
…#22) * [IMP] Extend fsm.location object
…#22) * [IMP] Extend fsm.location object
Modified module: