Who's On?

	Membership:
	Latest: Julie
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5311

	People Online:
	Visitors: 331
	Members: 0
	Total: 331

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3290
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244

Landmark / Test Environment W/OUT E-mailing Real Suppliers?

1 Replies

0 Subscribed to this topic

32 Subscribed to this forum

Sort:

Author

Messages

Riverboat Sam

New Member

Posts: 3

3/1/2011 3:29 PM

Does anyone have a way to copy Landmark Prod to a Test environment and remove or substitute Supplier E-mail addresses? If we copy Landmark to test, we're afraid that there's nothing to stop e-mails from going out to real vendors from the Test system. We don't want to pull the plug on the entire Test box as regards to e-mailing, because there's aspects of e-mailing in Landmark that we want to test.
Does anyone have a means of deleting or substituting the Supplier e-mail addresses... or some other solution?
Thanks for any help!

Woozy

Veteran Member

Posts: 709

3/2/2011 3:22 PM

We had this issue with EmployeeContact and Actor email addresses.

Are you under a Managed Services contract for Landmark management? In our case, we worked with LMS to create a set of "post data refresh" tasks that they perform after every data refresh that includes a set of SQL updates of email addresses from the "real" addresses to a "fake" addresses in those business classes (which is the same for everyone, and that goes to a secured public folder for testing purposes).

By the way, as part of the post-data refresh tasks, we also have LMS:

truncate several business classes (like Workunit information, pending actions, and scheduled tasks) so they don't continue running and generating notifications
truncate/restore several business classes (like ProcessFlows, ProcessFlow Versions, System Configuration, PFI Tasks, etc) since we typically have different setup in each environment, and development in process that hasn't gone to Production.

This is something we've been building since go-live, and it still changes every refresh cycle as we find new "issues" that we have to address.

I hope this is helpful.