Here's a more detailed breakdown of how the Docwriter would fit into the process:
1. Lead to Opportunity (Qualification Stage):
Lead is created when a service request is first submitted.
Opportunity is created once the lead is qualified and the request is deemed legitimate and ready for processing.
At this point, the Opportunity is primarily used to track the qualification of the service request.
The Opportunity tracks high-level details such as the requested service type, expected completion date, assigned team member, and SLA compliance.
The Opportunity may undergo approvals but does not yet involve document creation or detailed execution.
Docwriter (and document generation) does not typically play a role in this phase. The Opportunity is for business validation and high-level tracking.
2. Service Request (Post-Opportunity Conversion):
Once the Opportunity is qualified and approved, you move to the Service Request stage. This is where the Docwriter (or another document generation tool) comes into play.
Service Request Creation:
The Opportunity is converted into a Service Request once the service is deemed ready for execution.
The Service Request entity is used to manage the detailed execution of the request, including:
Document generation (using Docwriter).
Approval workflows.
Task management.
SLA tracking for fulfillment.
Docwriter would be used during this phase to generate the document(s) based on the information collected in the Opportunity. For example:
Document Drafting: When the Service Request is created, a Docwriter button could be available to generate the initial draft of the required document (e.g., policy, report, contract).
Document Editing & Collaboration: Once the document is generated by Docwriter, it’s stored in SharePoint for collaboration with stakeholders. Feedback is gathered, and the document is revised based on comments.
Approval Process: The Service Request could go through a multi-level approval workflow for the document, and the document itself is updated and finalized.
Where Docwriter Fits in the Lifecycle:
Opportunity Creation: Qualifying the request; no document generation yet.
Service Request Creation:
Once the Opportunity is converted to a Service Request, the Docwriter is used for document generation.
Documents are created based on the details provided in the Opportunity (e.g., type of service, service category).
Document Review and Collaboration:
The document is shared with stakeholders through SharePoint.
Stakeholders leave feedback, and the document is revised in Docwriter as needed.
Approval:
The document goes through approval workflows in Dynamics 365.
After final approval, the document is published (e.g., delivered to the requester or uploaded to a marketplace).
Clarification on Timing:
Docwriter comes after the Opportunity is qualified (i.e., after the service request has been validated) but before the Service Request is completed. The Opportunity acts as a qualifying entity, while the Service Request tracks the detailed execution of the service.
The Service Request is the entity where the fulfillment occurs—this includes document creation, feedback, revisions, and final publication.
In Summary:
The Opportunity is focused on qualifying the service request and ensuring that it’s viable for fulfillment.
Docwriter (or document generation) comes into play once the request has been qualified and is moved to the Service Request stage. Here, documents are created, shared, revised, and approved.
The Service Request entity tracks the execution and delivery of the service, including document creation and final approvals, using Docwriter and SharePoint for collaboration.
