Best Practices for document types x product types in Opportunity
Dear community,
My client has a requirement to specify a list of required documents (per document type) according to which products were entered in an opportunity.
They required a checklist for those documents that needs to be added to the opportunity. And the checklist must be visible for the sales rep.
Can anyone tell me what would be the best practice to implement this?
thanks
Like
Hello Danilo,
You can create a detail (with an editable list) for the Opportunity edit page and business process that will add the data in the detail object once the new product is added into opportunity.
For example, you can create a new detail "Required documents" on the [Products] tab of the Opportunity edit page. Your detail object will contain the following fields:
- the column for establishing connection with the [Opportunity] object,
- the column for establishing connection with the [Document] object,
- some boolean field for document status (ready/not ready)
You can find more information how to create a detail with the editable list following this link - https://academy.bpmonline.com/documents/technic-sdk/7-12/adding-detail-…
Then, you will need to create a business process which will be triggered on the [Record added] event for the [OpportunityProductInterest] object and will insert the data into your detail.
Please, see the related articles:
- https://academy.bpmonline.com/documents/technic-bpms/7-12/signal-start-…
- https://academy.bpmonline.com/documents/technic-bpms/7-12/add-data-proc…
As a result, your detail will be updated once you add the product in the opportunity.
Hi Tetiana, thanks for the suggestion, it worked. However, it is generating duplicate entries (same required document for different selected products). Any suggestion on how to avoid this?
Hello Danilo,
You can create a script-task element (https://academy.bpmonline.com/documents/technic-bpms/7-12/script-task-p…) in your business-process. In such script task you will be able to get the list of existing records in the detail object via ESQ,
check whether the document already exists in the detail and add it if it is needed. You can learn more how to use ESQ on our Academy web-site -
https://academy.bpmonline.com/documents/technic-sdk/7-12/crud-operation…