# data[].attributes.body
Announcements: TM ONE Redesign launching tonight (4/19)
Blockers:

Risks:

Goals for the week:
- IGS salesforce metrics release this week
- Permissions AWS focus; after merging in several small branches
- POC: Kick off ONE Login
Needs:

- How to enforce uniqueness across salesforce contact ids

# data[].attributes.body
Goals: Windows 10 update/setup, Permissions release.

Blockers:
Risks:

Mon Apr 17 ★
Last Week: Fixed activity advance search issue. Back up data.
Today: Backup data. Windows 10 update (16.07 or higher). restore backup.

Tues Apr 18
Yesterday: Got updated Windows 10. Docker setup worked as expected.
Today: Merging feature branches to master , prepare and test Build for Thursday release

Wed Apr 19 ★
Yesterday: Prepared Permissions build. Testing on QA env. Re-based permissions-docker branch from master.
Today: Testing permissions on IJASH, Fixing configs for Permissions-docker. getting permissions docker image working locally.

Thurs Apr 20 ★
Yesterday: Worked with Priya to fix Permissions aws config, Local permisssion docker image, Permissions cloud deployment and intdev102 portal setup for Permissions aws.
Today: Verifying Permissions build on ijash, Deployment to production on Monday.

Fri Apr 21:
Yesterday:  testing ijash build and reading angular docs
Today:Continue with Angular documentation

# data[].attributes.body
Goals: Kick off Unified Login Redesign

Blockers:
Risks:

Mon Apr 17 ★
Last Week: TM ONE w/OIDC for Federation POC; Angular 2 review
Today: Retrieve ONE Login UX Specs. from Casey; will decide where to start from there

Tues Apr 18 ★
Yesterday: Retrieved UX specs for Unified Login from Casey
Today: Start on FTUE screens for ^^; figure out how to package an Angular 2 project w/existing ONE login codebase

Wed Apr 19 ★
Yesterday: Wrapped up self-service AWS deployment
Today: Actually start on FTUE screens for ONE Login UX Redesign

Thurs Apr 20 ★
Yesterday: Getting more acquainted with angular CLI w/tutorials/docs before starting on Unified Login
Today: Wrap up Angular2 documentation sifting then start on FTUE screens

Fri Apr 21:
Yesterday: Set up Angular2 project for Unified Login; started on FTUE screens
Today: Continue w/^^: should have email/username FTUE screen on git by EOD

# data[].attributes.body
Goals: Finalize identifier first design

Blockers:
Risks:

Mon Apr 17 ★
Last Week: Completed POC, Came up with 3 approach for identifier first flow, Reviewed Web Caching from Pierre
Today: Completed Sequence Diagram for Identifier First Approach consider OL integrated in PF or outside PF. Open for new tickets.

Tues Apr 18 ★
Yesterday: Came up with Sequence Diagram for Identifier first approach
Today:  Finalize Identifier first design. Work on New one login design work with Josh and Amol.

Wed Apr 19 ★
Yesterday: Finalized identifier first approach, helping Amol for permissions AWS migration
Today: Permissions AWS migration continues, Work with Josh and David on one login new design

Thurs Apr 20 ★
Yesterday: Completed AWS migration on non prod, permissions aws app available on portal intdev102. Gave updated docker file to Amol for local env set up
Today: Get more understanding on one login UI components and work on architecture

Fri Apr 21:
Yesterday: Working on one login UI sequence diagram
Today: Working on one login UI sequence diagram

# data[].attributes.body
Goals: Windows 10 imaging redux, dev and QA testing of web response cache, possible metrics enhancements

Blockers: Windows 10
Risks:

Mon Apr 17 ★
Last Week: implemented web response cache with some web-queriable metrics
Today: Adding annotations in all web services, testing on dev environments

Tues Apr 18 ★
Yesterday: cache deployed to intdev102 for testing. getOrganizationsForHostAndTcodes(), searchTcodes(), getUserAccountsForHostAndOpcodes(), and getUserAccountIdsForHostAndOpcodes() are cached.
Today: windows 10 upgrade, adding more methods to the list of those cached, discuss wan replication of hazelcast with Shweta.

Wed Apr 19 ★
Yesterday: A whole lotta nuthin'. Windows 10 upgrade still wont let Docker install, cache branch wont deploy on jetdev3 or intdev102 (deploys fine on local), and logs are not being written, even after reprovisioning, so no way to see what's wrong. Syseng ticket was created, still no answer
Today: Request a full reimaging of laptop with correct windows 10 version, then reinstall everything

Thurs Apr 20 ★
Yesterday: progress on Docker install. Was using the wrong (32-bit) PowerShell, one of system's scripts is faulty. Should be fixed today. Also progress on jetdev3 and intdev102 deployment, the fault was a change on those boxes that makes them not accept CRLF in conf files anymore. Fixed my end, trying to get them to revert that change, tho
Today: Hopefully finalize Docker install and resolve deployment issues. Also looking into issues with authenticate when using cache.

Fri Apr 21:
Yesterday: Worked on cache issues, all fixed now, code cleaned up.
Today: fixed unit tests, merged master, will roll out to jetdev3 then intdev102. Still no work on updated Docker install script.

# data[].attributes.body
Goals: Fix SalesForce and Mixpanel issues

Blockers:
Risks:

Mon Apr 17
Last Week: php script for user creation in Mixpanel and domain CSS,CSM and segment synch issue
Today: update scheduler to handle updatedomain and mixpanel user create testing

Tues Apr 18 ★
Yesterday: Salesforce scheduler and php debug
Today: salesforce release and verification in prod

Wed Apr 19 ★
Yesterday: salesforce scheduler update release to prod, verified domains, updated with expected data from salesforce
Today: updating metrics publish scheduler, may be mixpanel script?

Thurs Apr 20 ★
Yesterday: code clean up in metrics publish scheduler and with Brian's help fixed php debug and mixpanel api, tested create users in mixpanel scripts for IGS users
Today: get more details on unique salesforceId for users and its implementation

Fri Apr 21:
Yesterday: working on unique salesforceId enforcement
Today: cont. working on unique salesforceId enforcement

adapter-service deployed successfully on aws with intdev102 igs and DB, and working REST APIs, still issue with uws-adapter
http://adapter.ibs.dev1.us-east-1.nonprod-tmaws.io:8080/health/healthcheck