BAM is moving to using BBID, but we have no way of testing to see if our configuration works prior to moving. We should have a test environment to test major system changes such as this prior to putting them into production.

A sandbox or test environment critical for testing functionality, trying new ideas, etc. All systems I have worked in have always had a test/sandbox environment.

We need a test environment, even temporary, so we can test changes to API integration with realistic data without impacting our production environment/data. This is the only vendor I am aware of in our portfolio, that does provide an environment where we can safely test changes.

I agree.

App State would really appreciate a Sandbox enviroment. This would help prevent errors, assist with training, and be able to test APIs without risking real-time errors.

Yes, a sandbox would be awesome!

Having a test environment that can be used to work with reviewers, donors and new students would be very beneficial. This would eliminate the possibility of errors in a live situation and allow new users the safe option for practice purposes. Would also allow us to "see" how any new additions look from the student's perspective. Thank you.

How do you vote ...or is this closed?

Almost every software products as INCLUDED a Fully functional Production and a Test environment...what BB is calling a test environment for setting up SAML is BS.

We need the ability to work on the next General Application while the current one is open. That would be extremely helpful. So if a test environment is not available could this be an option?

Yes to a test environment for the General Scholarship application! Two years worth of errors because we could not see how our edits would appear to the students until it was too late.

I would appreciate the ability to create a mock application where I could capture screenshots of what a student should see at each step. Having to complete a Profile page, a General Scholarship application and then individual opportunities, becomes cumbersome and inviting incomplete applications.

This is something that the University of Alaska would like to see. 

At the University of WI we purchased a second production site.   That one has 1000 applicants and some small number of opportunities (can't recall what). We use it as out test system.   We give it a look and feel (and name) so applicants/users will never confuse it for the real one.

Pros: We have a production system that use as test.

Cons: As a separate site it must be maintained separate (can't just have BB port data over)

Even if infeasible to have a full testing environment, having a sandbox environment where we're able to test APIs and various configurations in a focused way would be invaluable. 

I have always felt a test environment would be very helpful.  Working with live information has always been extremely concerning and I'm extremely grateful that AW/BBAM has been able to restore or at least figure a way to work around issues caused in the live site. but it would be nice if the live site was not affected by testing.

We've found that a full testing site would be technically infeasible and difficult to maintain. However, I'm leaving this request as "open for voting" for a better way to test APIs.

A test environment would be extremely helpful when testing new functionality and its effects without messing with live data. If I could vote multiple times, I would.