← Post-Live Processes

Post-Live Cases (Banno OLB Conversion Case)

New process for Banno OLB Conversion Case cases - Revised August 2022

CWA Cases must contain the following minimum information:

  • OLB Code
  • Date/Time of the Cut Over/Conversion
  • Will there be a Takedown first? If so, we will need the following:
  • Date/Time
  • Location of Takedown (in modal or other?)
  • Message for Takedown - Standard (below) will be used if alternative is not provided.
  • Standard Takedown Message:
    <div class="temp-olb-msg">Online Banking is temporarily unavailable and will return DAYOFWEEK, MONTH DAY# at 0:00 am TIMEZONE.</div>
  • Are there Smartbanners? Do we have the links? Devs will NOT be adding smart banners when they did not previously exist unless explicitly asked for in the case.
  • Are there App Store Icons on the site (in the footer/etc.)? Do we have the links? CWA will mention any they know about and Devs will search for any throughout the site as well.

We need clarification on all of the above before starting the OLB case.

Developer Process

Part 1 - Takedown (if applicable)

If the FI has chosen this route, we’ll:

  1. Pull down repo and create a branch called case#####-takedown.
  2. Edit the files on the repo necessary for the takedown. See below for a standard takedown message.
  3. Upload the files to UAT temporarily.
  4. Take a screenshot of the placement/text to add to the case.
  5. Revert back to previous UAT zip.
  6. Finally, this branch will never be merged. This will just be created in case someone needs to pull this branch down. Once the takedown is approved, the zip file will be manually uploaded to the live CMS until the designated cut over.

Notes:

  • There isn’t a need to do a takedown microsite. We will only edit the microsite with the new OLB code, when approved.
  • If you need to publish another dev’s takedown, you would need to pull the repo, checkout the takedown branch (case#####-takedown), test the zip file on UAT first and then upload the zip to the live CMS at the designated time.

Standard Takedown Message:

<div class="temp-olb-msg">Online Banking is temporarily unavailable and will return DAYOFWEEK, MONTH DAY# at 0:00 am TIMEZONE.</div>

Part 2 - Proceed with OLB edits:

  1. Checkout master.
  2. Create a new branch for regular OLB work. Ex: git checkout -b case#####
  3. Begin to work the case for the OLB edits - edit the mustache/js/etc. files.
  4. Upload the zip to UAT.
  5. Create merge request.
  6. Add the Takedown (if applicable) & Cut Over times to the calendar so that it is scheduled. Note: You can also add a reminder to check on the status of the request a couple of days before launch if you haven’t heard back on the approval(s).
  7. Submit completed case to CWA with detailed publishing notes. Note: See below for an example of detailed publishing notes.
  8. Once the OLB edits are approved, make the OLB edits to the microsite (Create a branch in microsites repo, etc. and add to the publishing notes of the case). NOTE: Microsite commit needs to read - “case##### workdone URL”

Publishing Notes

  • Merge Request: LINK
  • Agent Smith Deploy Command:
    push-cms-zip casenum deployname.zip www.site.com git-repo-address-here.git
  • OLB Edits? Yes
  • Smartbanner/App Icons? No/Yes
  • Takedown? No/Yes. If Yes, date/text/location? (Make sure takedown screenshot is attached to case.)
  • Scheduled Go Live Date/Time: Date/Time
  • Microsite changes needed? YES
  • Microsite PR: LINK TO PR
  • Microsite URL: https://www.bank.com/temporarilyunavailable