Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
Lawson Landmark
Landmark / Test Environment W/OUT E-mailing Real Suppliers?
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Hitman
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5208
People Online:
Visitors:
371
Members:
0
Total:
371
Online Now:
New Topics
Lawson S3 HR/Payroll/Benefits
Post Tax Benefit Plan Table
11/14/2024 9:16 PM
Hi, totally new to Laswon. I have a repor
Lawson S3 Procurement
ED501 Error: Map 850 not supported by /law/c15vda/lawson/test10/edi/bin/laws_out_91
11/12/2024 3:47 PM
Tried runnning ED501 and getting the atathced erro
Lawson S3 HR/Payroll/Benefits
Error
11/6/2024 9:54 PM
When I try to enroll a retiree in 72.1 health plan
Infor ERP (Syteline)
Syteline: New Data Maintenance Wizard (Error) Need help
11/1/2024 4:24 PM
Hi, I need help with an error on syteline while us
Dealing with Lawson / Infor
Implementing Lawson v10 with Cerner Surginet, Case Cart Picking, and Quick Adds for the OR
10/29/2024 4:20 PM
Hi Everyone, I am wondering if there is any org
Lawson S3 HR/Payroll/Benefits
Canada Tax Calculation (Federal and Provincial) Issue
10/23/2024 5:00 AM
Initially, we had problem with CPP2 calculation is
Lawson S3 HR/Payroll/Benefits
CA Section 125 401k Plan
10/22/2024 10:13 PM
Does anyone have any recommendations on how to fac
S3 Systems Administration
Running AC120 deleted records from ACMASTER table
10/22/2024 3:40 PM
We recently ran the AC120 as normal and somehow it
Lawson S3 Procurement
RQ13 Approval Info
10/17/2024 2:12 PM
When a Requisition is approved on RQ13, what table
S3 Customization/Development
Read and Write CSV file COBOL
10/9/2024 2:53 PM
Does anyone have a quik example of a program that
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3291
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1372
Roger French
1315
mark.cook
1244
Forums
Filtered Topics
Unanswered
Unresolved
Announcements
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Infor / Lawson Platforms
Lawson Landmark
Landmark / Test Environment W/OUT E-mailing Real Suppliers?
Please
login
to post a reply.
1 Replies
0
Subscribed to this topic
32 Subscribed to this forum
Sort:
Oldest First
Most Recent First
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.
Please
login
to post a reply.