Skip to content

Separate the contact change workflow from the adding subscription management account

Sokunrotanak Srey (Rotanak) requested to merge doc-contact-change into master

Why is this change being made?

Changing contact sometime means customer would like to completely change the way they manage the subscription like receiving renewal update on the new email. This need to be updated on SFDC and Zuora. We're adding the workflow in this MR.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)

Merge request reports