Empower your firm with next-gen data solutions

Our product suite (all .NET based) consists of a small but growing number of related applications with a lot of configuration data stored in app/web.config files with multiple environmental transforms. Much of the configuration is repeated across multiple projects in each environment (e.g. connection strings, email servers, etc.) so centralization of this data would be of great help. Currently, making even simple changes to any of these keys requires sifting through a large number of config files and transforms to make changes which is tedious, error prone, and difficult to test effectively.

How should you go about saying no to your clients in a way that’s respectful, clear, and doesn’t tank the project? What should you do when saying no isn’t a viable option? And what does it have to do with improv? Join us to find out.

Use case modeling timeline and possible future events that could interfere with supply chain. Allows user to see all options for rerouting and the implications of each decision.