# data[].attributes.body
Every time we needed anything you were the SUPERMAN with a solution. Enjoyed working with you and looking forward to the future.

# data[].attributes.body
For all your hard work and answering the millions questions that I had and will have lol

# data[].attributes.body
The working sessions were great for quick reactions and problem solving. A lot of opportunity for learning new troubleshooting techniques as well!

# data[].attributes.headline
The Connectivity of the Streams in Lower Env (if possible!)

# data[].attributes.subject
The Connectivity of the Streams in Lower Env (if possible!)

# data[].attributes.body
From Salesforce side of things, we need these streams to be running from Env to Env for continuous testing. Even if it is only available Stage to Stage for all of the Streams running will help. We need to make a note to make sure every time we update anything to the streams, we make sure that it is running successfully in Stage.

# data[].attributes.body
Thank you for all the hard work, you are the expert of connecting to SF now!

# data[].attributes.body
The changes in Salesforce or Database, which can effect each other, before we make the change, we need to be better at communicating and test.

# data[].attributes.headline
Loan Stream Deployment - Incorrect Category Ids

# data[].attributes.subject
Loan Stream Deployment - Incorrect Category Ids

# data[].attributes.body
After our go-live, we realized there was a miscellaneous table join that resulted in the incorrect category ids being sent through the stream. We noticed it quickly and Suman tweaked it almost immediately, but it would have been ideal if we had caught this during the PROD --> Stage connection testing.

# data[].attributes.body
Great Job everyone who involved in the project and made it success. It is pleasure working with you all :)

# data[].attributes.body
Thank you for always stepping up to test all aspects of the different streams - from JSON creation and load testing to validating the smallest scenarios on the Salesforce side - you are truly the best. Thank you for everything!

# data[].attributes.body
We worked great as a team. It would be nice if DEA, DPE and Salesforce teams did a show and tell (more like a quick code walkthrough). This would help understand each other's systems better

# data[].attributes.headline
Kudos to Jealene, Barbara, Robert and Calleen

# data[].attributes.subject
Kudos to Jealene, Barbara, Robert and Calleen

# data[].attributes.body
Thank you all for keeping us aligned to the project goals and handling all communications. There were lots of moving pieces. You all did a terrific job keeping everyone informed of the changes

# data[].attributes.body
Loan stream had a lot of complexities and was the first project to use the new pattern. You worked through the issues patiently and showed a lot of composure.

# data[].attributes.body
Thank you Raj for answering all our queries and guiding us during the development process

# data[].attributes.body
Having stepped into the Mulesoft Exit somewhere in the middle I have been very impressed with how highly functioning these teams are and how easy collaboration is. We are making great plans, executing beautifully, and adapting to changes as they happen in the best possible way.

# data[].attributes.body
You wear so many hats and you excel at everything that you do. Your knowledge, organization, intuition, and overall demeanor bring an incredible amount to Team Astro and the Mulesoft Exit project as a whole. Keep making it look easy because you're great at it!

# data[].attributes.body
Barb Doyle is a rockstar. Thanks for keeping everyone informed and up-to-date!

# data[].attributes.body
We spent a lot of time on this functionality -- trying to understand which tables, databases, etc. And then after all of that discovery and hard work, we discovered a fundamental flaw in how the contactMove and upsertContacts calls will come to Salesforce. We ultimately determined the effort to adjust for this was too complicated and not worth it... which was frustrating but relieving at the same time. Thumb pointer moment -- I should have taken more time to understand how the Breakout Account Tool works in the backend before the project kicked off, so I apologize for the large amount of time and effort spent on this functionality.

# data[].attributes.body
I think having the contracts written up to define high-level requirements helped set us up for success as we moved forward. There were always small tweaks along the way, but it ensured that everyone knew the direction of each stream, and could update it along the way together!

# data[].attributes.body
Thank you for always assisting with each initiative we have in this project without question or issue. You have a terrific collaborative mindset and Team Astro is incredibly grateful to have the opportunity to work with you every step of the way :)

# data[].attributes.body
Thank you to my two favorite architects (and PILLAR AWARD WINNERS) for all that you do for the MuleSoft Exit project and for all of our teams. Your knowledge, hard work, and willingness to answer any and all questions that come up are incredibly inspiring and helpful. We couldn't do this without both of you!

# data[].attributes.body
I appreciate all that you have done for this project. From constantly organizing meetings and conversations to keeping documentation organized. This project would not be where it's at without you. It has helped me grow as a developer and think of external teams to consider in the many projects to come in the future.

# data[].attributes.body
We would like things to go perfect and according to plan, but when things didn't work out we were not only able to adapt in our own lanes, but do so in our cross-team environments, coordinating our efforts and experimenting to get to where we need to be.

# data[].attributes.body
When we weren't fully connected end-to-end, we could've had larger volumes of real data for all of our scenarios. We had the few JSON bodies here and there to run through Salesforce, but I feel we could've been more exhaustive with the amount of real JSONs we put through while being in our lower more accessible environments.

# data[].attributes.body
At project kickoff there was a strict timeline that escaped us pretty quickly. There was a lot of trial and error as this was a brand new process with a new tool in the mix. It seemed like we weren't getting any traction with a solution causing other teams to push their timelines. It has made the stress of the project heightened and when it came down to it leadership wanted to see some progress for the months of work we had been conducting. It is never an ideal situation to find yourself in to scramble to get things put together in the last minute. It could have been process that slowed us down or the experimental phase of the project either way I didn't feel we had the support we needed to be successful. This caused it to come down to the wire and put individuals under a lot of stress.

# data[].attributes.body
Thank you for all the insight you've given not only in the work delivered in our recent Stream solutions, but in all the moving pieces that would all be working together

# data[].attributes.body
Not only are you a great QA but you also kept us laughing and having a good time despite all the stress. Thank you!

# data[].attributes.body
Huge huge huge shout out to everyone that has been involved in this project. I continue to be so impressed with the way all teams have collaborated and worked through everything together. The willingness you all have given - and receive feedback from one another is next level. It's been wonderful working together and I hope you are all so proud of the hard work that's gone into these streams.

# data[].attributes.body
Thanks for keeping us on track with the status updates & meeting facilitations!

# data[].attributes.body
Thank you for EVERYTHING that you've done to support this initiative!

# data[].attributes.body
#IYKYK
You quickly learned a new technology with ease!
THANK YOU for all of your hard work!

# data[].attributes.body
Maybe 4pm? Any questions ect after 4 risk not getting answered or looked at till next day

# data[].attributes.body
Adding stream connectivity to lower environments. This will help us do end-to-end testing earlier on and identify potential issues faster. Also allows for more testing in the process

# data[].attributes.body
Demo functionality/code walk-through across teams so we all have better understanding of each other's systems

# data[].attributes.body
Making sure communication among BAs is streamlined to ensure all pieces are moving as expected and any risks/setbacks are communicated as early as possible