Provisioning for alumni for the community (giving our alumni a means for logging in) is yet to be finalized. Recent conversations indicate that the ideal direction and solution could take a significant amount of time and will require funding. This means the community, which is complete/built, could be dark for some time. We've discussed contingency plans and interim work-arounds and will continue to review these options. Proposals from our campus Identity Management (IDM) teams will be presented on Sept 3.

Access and use of data (AKA "security") is another hot topic as of late. The eCRM overarching philosophy of an open CRM conflicts with eComm business requirements that ask for "fenced off" data based on where a user/CU communicator works and their role. The CoE has proposed a work-around that is based on a folder structure with embedded reports that are specific to users, their units and constituents. Teams are still discussing this potential work around, but it has not been tested to confirm it will meet client conditions of satisfaction.

Data loads from the three source systems (CU SIS, HRMS, Advance and MDM) to the Stage environment in Salesforce are about three weeks behind. This is due in large part to the sheer volume of data. With 1.2 million records and hundreds of data points, it simply takes a long time. This is great to work through this now so we can plan for the migration to production, which will also take a significant amount of time. While Kyle's notes indicate launching the eComm team at the same time as the super user/UAT group to Production, I am still pushing for access to production for our eComm team before mid-September. We are working through the viability of this proposed solution.

The eComm team (MECs) had an all-day working session on Thursday. Aug 13. Here's a picture of the group working feverishly on phase 2 user stories with Kyle Kirves facilitating the session.