Closed collinpreston closed 4 months ago
@pdpinch When a new course run or program is created, the command ./manage.py configure_hubspot_properties
must be run from the web
application in order to add that course run or program as an option in the Hubspot certificate property. How should this process be handled/communicated/documented?
When a new course run or program is created, the command ./manage.py configure_hubspot_properties must be run from the web application in order to add that course run or program as an option in the Hubspot certificate property.
We discussed this over Slack and it seems like creating the property when a certificate (course or program) is created is preferable to adding another management command that needs to be run manually.
How should this process be handled/communicated/documented?
I think we've outgrown this discussion post -- https://github.com/mitodl/hq/discussions/306 -- and should establish something more permant, like the google doc you started. In any case, we should loop in @cachob who will be a key consumer of this kind of documentation.
What are the relevant tickets?
https://github.com/mitodl/hq/issues/3783
Description
How can this be tested?
MITOL_HUBSPOT_API_PRIVATE_TOKEN
,MITOL_HUBSPOT_API_ID_PREFIX
,HUBSPOT_PIPELINE_ID
).docker-compose run web ./manage.py configure_hubspot_properties
in order to update the Hubspot course_run_certificates and program_certificates properties with the string representation of your course runs and programs.The Hubspot Contact will have properties displayed like the screenshot below:
You can also test the course and program certificate creation, and subsequent triggering of syncing the user's data with the Hubspot contact, by enrolling the user in a course, defining a grade for the user in edx, running the periodic edx sync command that checks for course run completion and grades from MITx Online, which will then create a course and possibly a program certificate.