on 10-26-2006 5:57 PM
Hi,
I have one master and two slave repositories. Our website is running on the slaves. We have different workflows that are triggered in master repository for record addition or update. Problem is that even when there is a workflow in progress to accept/reject changes on records, slave synchronization process makes those changes available in the slave repositories. I wonder then what is the use of workflow process if we can't control the changes?
What is the recommended approach to control changes and to make sure only the accepted changes are available on the website.
Regards,
-Y
While there can be many approaches to address this issue, one of them could be to associate your main record with a "Status Code" and tie that with Workflow process in which users set "Status Code" to "Approved".
Your website picks up those records which are "Approved".
HTH
--
Venkat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.