Salesforce > Conga Composer (w Query Builder!)
Budget: $25 – $50 USD
This project will be paid on an hourly basis, as some of the documents involved are far more complex than others.
I'm looking for an extra set of hands to help me on a Salesforce project, leveraging Conga Composer.
This Salesforce instance is for an organization that is in the home healthcare space. The Salesforce org tracks patients (Contacts), along with multiple custom objects to track other relevant information related to the patient, such as their related contacts (friends, family members, emergency contacts), medications, diagnoses, dietary restrictions, hearing issues, services, etc.
The organization has approximately 30+ MS Word documents that are government issued forms. Depending on the use case, Salesforce users will need to be able to initiate Conga Composer (example: from the Contact screen for the patient), select the appropriate form to be filled out, and the relevant information for the Contact (patient) should get populated, as needed, into the appropriate sections of the form.
This will involve leveraging Conga Queries to pull the related records (either via lookup, or pull all relevant child records as a table) into the selected form.
Most of the time, these MS Word documents don't even need to get converted to PDFs, as the users will typically need the output files as MS Word documents.
Generally speaking, there is tremendous overlap between these 30 template documents. Nearly all of them ask for basic information about the patient, their home address, phone #, insurance details, emergency contacts, etc. However, there are definitely varied nuances among the various forms that need to be specifically addressed within each form.
About 80% of the data that needs to get merged into these MS Word documents already exist as objects/fields in Salesforce. As I am reviewing each document with the appropriate subject matter experts, we are identifying the source for each value to be inserted into the templates, and where the data doesn't exist in Salesforce, we are making the determination as to whether or not we will ignore it or if we need to update the underlying Salesforce configuration to create the appropriate objects and fields to store this information before inserting it into the Conga Composer templates.
I'm looking for an extra set of hands to help me on a Salesforce project, leveraging Conga Composer.
This Salesforce instance is for an organization that is in the home healthcare space. The Salesforce org tracks patients (Contacts), along with multiple custom objects to track other relevant information related to the patient, such as their related contacts (friends, family members, emergency contacts), medications, diagnoses, dietary restrictions, hearing issues, services, etc.
The organization has approximately 30+ MS Word documents that are government issued forms. Depending on the use case, Salesforce users will need to be able to initiate Conga Composer (example: from the Contact screen for the patient), select the appropriate form to be filled out, and the relevant information for the Contact (patient) should get populated, as needed, into the appropriate sections of the form.
This will involve leveraging Conga Queries to pull the related records (either via lookup, or pull all relevant child records as a table) into the selected form.
Most of the time, these MS Word documents don't even need to get converted to PDFs, as the users will typically need the output files as MS Word documents.
Generally speaking, there is tremendous overlap between these 30 template documents. Nearly all of them ask for basic information about the patient, their home address, phone #, insurance details, emergency contacts, etc. However, there are definitely varied nuances among the various forms that need to be specifically addressed within each form.
About 80% of the data that needs to get merged into these MS Word documents already exist as objects/fields in Salesforce. As I am reviewing each document with the appropriate subject matter experts, we are identifying the source for each value to be inserted into the templates, and where the data doesn't exist in Salesforce, we are making the determination as to whether or not we will ignore it or if we need to update the underlying Salesforce configuration to create the appropriate objects and fields to store this information before inserting it into the Conga Composer templates.