"protecting" departments

Yahoo Archive
1
With the help of Epicor tech support, we cobbled together a solution to this. Posting here for the collective.

Quote searching is limited by the BPM Quote.GetListCustom, Pre-Processing
The ability to open a quote is limited by the BPM Quote.CheckQuoteSecurity, Pre-Processing

If anyone wants the 4GL code behind these two, please let me know.

Thanks,
Kunal




________________________________
From: Kunal Ganguly <kunal_vantage@...>
To: Vantage Yahoo Group <vantage@yahoogroups.com>
Sent: Mon, January 4, 2010 12:44:03 PM
Subject: [Vantage] "protecting" departments


Hello,

Just wanted to see if anyone had any suggestions or ideas on how to do this, per perhaps has already done it.

We want to "protect" quotes created by one department from another department within the same company without using the multi-company feature. We cannot separate by geographic territory either since each department can operate anywhere in the world and also.

I am thinking that when a quote is created, a value is written to a UD field which contains the names of the departments that the user is authorized to and, when the same record is opened later, the "ON LOAD" event checks against a pre-existing database to see who is authorized for what department and this decides whether the record can be loaded or not.

Thanks,
Kunal

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]
2
Hello,

Just wanted to see if anyone had any suggestions or ideas on how to do this, per perhaps has already done it.

We want to "protect" quotes created by one department from another department within the same company without using the multi-company feature. We cannot separate by geographic territory either since each department can operate anywhere in the world and also.

I am thinking that when a quote is created, a value is written to a UD field which contains the names of the departments that the user is authorized to and, when the same record is opened later, the "ON LOAD" event checks against a pre-existing database to see who is authorized for what department and this decides whether the record can be loaded or not.

Thanks,
Kunal





[Non-text portions of this message have been removed]