11/22/2024 1:56:33 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss designing applications to work with SalesLogix. View the code of conduct for posting guidelines.
|
|
|
|
Sorbanes Oxley and keeping track of LOTS of SLX Changes. 7.20
Posted: 30 Aug 07 9:31 AM
|
Any ideas on how to keep track of most of the changes (adds, edits, deletions) for 135 users.....100 of them remotes, 15 of them LAN, 20 Remote Office on 1 remote office.....and concievably 135 of them could be coming in on the Web (although our projected 'load' is 30-50 at any one time).
RecordChanges and History type 262156 is not an option.
we're thinking lock down most of the major 'trackable' items like Account and Address information, Quotes, Contracts as Transactions...and save the entire record of the transaction in a table in another database....based on a trigger or capture of the transaction as it's being invoked (inserted or whatever).
We've thought about having a table with EntityID and the Table name and a Memo Field in it. The EntityId would store the AddressId, AccountID, etc. and the Table Name would be AccountProducts or what have you.....the MEMO field would be an XML like text document of the field names and values......
(we used to (back in the OLD days) store stuff like:
ACCOUNT: The Account Name
ACCOUNTID: A2EK00014RT
Any thoughts?
|
|
|
| |
|
Re: Sorbanes Oxley and keeping track of LOTS of SLX Changes. 7.20
Posted: 30 Aug 07 2:10 PM
|
We' re going to record the entire record for the Update and Insert triggers.....store this with a transaction GUID, etc. on another database in a LOG_ACCOUNT, LOG_ADDRESS clone of all tables you want to go after.
Use MyGeneration to create the Triggers, and Create Tables......
There is no BEFORE DELETE trigger.....
any ideas on how to capture anything about a Delete? SLX OLE DB Provider doesn't update the MODIFYUSER for example......
Maybe we add something to the SLX OLE DB Provider to capture which records are being deleted???
THANKS! |
|
|
|
Re: Sorbanes Oxley and keeping track of LOTS of SLX Changes. 7.20
Posted: 30 Aug 07 2:30 PM
|
Aren't you bypassing the SLX provider if you are using a database TRIGGER? The ON DELETE trigger should happen before the actual delete is done - which means the record would be copied to your LOG_ table(s)
As a suggestion, you might want to add a field in the LOG_ tables that indicates the record was an update, insert or delete.
John G. |
|
|
|
Re: Sorbanes Oxley and keeping track of LOTS of SLX Changes. 7.20
Posted: 30 Aug 07 3:28 PM
|
Absolutely, you have to bypass the Provider for Updates and Inserts in case an outside application, SQL statement, etc. changes the database......
I don't know if SLX actually changes ModifyDate, ModifyUser for a Delete statement......so these values aren't captureable off of a Remote database passed through Sync from a trigger on the main database.
so even if you use On Delete the value of ModifyUser won't be correct.... |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|