Thanks I have been disabling workflow in the same way. I have through about adding the two fields. I still may end up doing it if we get a lot of calls about the last modify by fields not showing the correct thing.
Dan Dan Wangler, SAIC; MHS Remedy Support Team Tri-Service Infrastructure Management Program Office (TIMPO) 300 Convent St, Suite 1800; San Antonio, Texas, 78205 Phone: 210-338-3162; Email: dan.wangler....@timpo.osd.mil -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of patchsk Sent: Tuesday, May 18, 2010 12:15 AM To: arslist@ARSLIST.ORG Subject: Re: {Remedy ARS} DSO We have a similar DSO setup for the reporting box. Only difference is other than the forms we do not store any workflows in reporting server also we do not use it as a hotbackup. But may be the following could be helpful for u r questions as there is no out of the box configuration that I know of. 1. We created two custom field 'xLastModifiedBy' and 'xLastModifiedDate', and wrote one set fields filter on Submit/Modify If $USER$ != "Distributed Server" Set $USER$ and $TIMESTAMP$ to above fields. We added all the forms in our system to this filter, so no need to write one filter per form. Just make sure the above field ids are same in all the forms. 2. Probably you could just write one filter and attach all the forms to it. This filter would fire on 0 order and if $USER$ = "Distributed Server" skips to 999 filter. On May 17, 7:50 am, "Wangler, Dan" <dan.wangler....@timpo.osd.mil> wrote: > Dear List > > We are trying to implement a database replication by using DSO. We have > a duplicate, parallel system to our production that is used for > Analytics/reporting. We have setup DSO to push changes, as they occur, > from the production (source) server to the parallel (target) server. > Our thoughts were to use the target server both for reporting and as a > hot backup. We have all workflow and escalations turned on but are > sending transaction to the target server as Data Only. I wanted to > check to see if anyone is doing this, using DSO to push to a reporting, > and to solicit comments about this approach. > > I see one important issue. When a record is created or modified on the > source server, the record always says it was modified last by > "Distributed Server". This is probably because DSO pushes the > transaction to the target server and returns a "Successful" transfer > back to the source server. Is there anyway to retain the "real" last > modified by and last Modified Date? While the information on the target > server is correct, it is confusing to the user on the source server. In > addition, while DSO is updating fields with the successful status, > another user could have open the form and get the message saying the > ticket had already been updated by someone else since the user opened > it. Is there someway to prevent this from happening? > > Another issue we see is that as information is pushed from the source > server to the target server, filters are driven on the target server. > In some cases, modifications on one form causes an update to a different > form and could lead to permissions issues. Is there someway to stop > this without adding to the filter qualification "USER' != "Distributed > Server"? One way, I can think of, is placing the target server in Admin > Only mode. Would the DSO creates and updates take place in Admin Only? > > Any comments or suggestions would be greatly appreciated. > > Regards > > Dan > > Dan Wangler, SAIC; MHS Remedy Support Team > > Tri-Service Infrastructure Management Program Office (TIMPO) > > 300 Convent St, Suite 1800; San Antonio, Texas, 78205 > > Phone: 210-338-3162; Email: dan.wangler....@timpo.osd.mil > > ___________________________________________________________________________ > ____ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > attend wwrug10www.wwrug.comARSlist: "Where the Answers Are" > > -- > You received this message because you are subscribed to the Google Groups > "Remedy ARS" group. > To post to this group, send email to arsl...@googlegroups.com. > To unsubscribe from this group, send email to > arslist+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/arslist?hl=en. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
