Create project / service contract from opportunity about yetiforcecrm HOT 4 CLOSED

This functionality exists from the beginning of YetiForce.
You can generate projects from the opportunity level (the module is associated).
Comment from YetiForce:
You can generate projects from templates (for example you click on “Add project type A” and it generates the project and assigns X number of tasks to it and Y number of milestones, you can configure everything in the panel)
Regarding a “service contract” I think that creating contracts is a part of sales process and this process should not end before creating the contract, that is why in version 0.0.12 we will add this function).

from yetiforcecrm.

Comment from Claude:
That is not what I meant. I would expect a function similar to "Create Invoice" from an "Opportunity" without having to re-enter all the information about the company, contact, etc. again

Comment from YetiForce:
You have in mind such functionality [http://www.vtexperts.com/product/vtiger-field-autofill/], but more extensive?

from yetiforcecrm.

Status: pending
Comment from Claude:
I was actually thinking of a more generic approach along the following line.
Goal: Create a new object in module B based on data in an object in module ABy-product: All commands 'Create Copy From X' and 'Duplicate' could be replaced by this one functionality
Configuration-------------------TABLE X
cmd_id -> unique identified
label -> Label to be displayed as the command source_module -> name of module A target_module -> name of module B (may be identical to modul A, thus allowing to use the same mechanism for duplicating objects) source_to_target_relationship -> type of relationship between A and B (dependence, related, none)
target_to_source_relationship -> type of relationship between B and A (dependence, related, none) source_related_to_field -> field in object A containing the reference to the newly created object B (if dependence is relationship type) target_related_to_field -> field in object B containing the reference to the object A (if dependence is relationship type)TABLE Y
cmd_id -> copy command id source_field -> Name of field in A to be copied to B target_field -> Name of field in B receiving copy from A
FUNCTION----------------1. Create a new object of type B2. Copy the data from object of type A to newly created object of type B using the data in table Y3. If source_to_target_relationship = related, created entry in table vtiger_crmentityrel from A to B4. If target_to_source_relationship = related, created entry in table vtiger_crmentityrel from B to A5. If source_to_target_relationship = dependence, set field defined by source_related_to_field to the identified of the newly created object of type B6. If source_to_target_relationship = dependence, set field defined by target_related_to_field to the identified of the newly created object of type A7. Optionally, execute a specific hook function to allow customizing the data copied (by filling specific fields with specific values, e.g., setting a given date field to today's date)
8. Display new created object of type B for editing
I think that implementing this functionality would not be that expensive in time and would allow to simplify the source code significantly as many separated functions currently in place could be removed. Unfortunately I don't (yet) have sufficient knowledge of the Yetifocre/Vtiger internaals to do the implementation myself, otherwise I would.
Regards
From: YetiForce [email protected]
To: [yetiforce:tickets] [email protected]
Sent: Wednesday, November 26, 2014 1:11 AM
Subject: [yetiforce:tickets] #34 Create project / service contract from opportunity
status: open --> pending
[tickets:#34] Create project / service contract from opportunityStatus: pending
Milestone: future
Created: Thu Oct 23, 2014 06:24 PM UTC by YetiForce
Last Updated: Wed Nov 26, 2014 12:11 AM UTC
Owner: nobodyIn order to implement YetiForce for end-to-end client management, it would be great if there would be a function that transforms an opportunity into either a project or a service contract, the two objects that could result from a successful opportunity.Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/yetiforce/tickets/34/To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

from yetiforcecrm.

I understand that you try to create a universal mechanism aimed to create relations and copy data between them. Your idea is good in general, but it has no business justification. Every process is different; various relations exist and show various data depending on a situation. Some of the things are configured rigidly (e.g. mysql foreign key so search can work faster). It is impossible to eliminate a developer from a CRM project and it seems as if you are trying to achieve that.

This Issue should be closed in my opinion. You’re describing some kind of idea, but not a logically proven requirement / business functionality.

from yetiforcecrm.