Hi Peter, That's an interesting question. I was under the impression that no workflow 'copied' over during the audit form creation. So I guess I wasn't expecting any workflow to set anything since how would it know to. I haven't created any workflow.
Thanks, Susan On 10/25/07, Peter Romain <[EMAIL PROTECTED]> wrote: > > Hi Susan, > > Is there any set fields workflow acting on the fields that are being > copied? > > We had an issue where a field was triggering an audit record when I didn't > think it should. > > It turned out that there was a filter setting the field to upper case. > > Even if the field was already in upper case (ie it didn't change) the > audit was still triggered. > > Cheers > > Peter > > > Hi Everyone, > > > > I was glad to see that the Audit process feature was very straight > forward > > and fairly easy to implement. I've tried it on one form on development > > and > > have an issue. I chose to use the Form type of Audit so we can run > > reports > > from the data. > > > > I chose Audit on numerous fields of interest. > > > > I notice that when I change only one field on a ticket, i.e. Assigned > To, > > it > > also writes several other fields to the corresponding audit form entry. > > > > At first I thought it was 'required' fields but that is not exactly the > > case. It is somewhat confusing when you're looking at the details of > the > > audit records. > > > > For instance, Priority shows on each audit record whether it changes or > > not. So say you change the Priority from Low to High and there are > > subsequently several changes to other fields at various times. On the > > records where Priority did NOT change, the audit record shows the > > 'original' > > priority value (Low). So you can see Low, Low, Low, High, Low, Low > ..... > > which leads you to believe it went back down from High to Low when it > > didn't. > > > > But then to make things more confusing, it did not act the same way on > the > > Summary field. Although it does show it on each audit record whether it > > changed or not, at least it keeps its current value. > > > > Are you seeing that behavior also? How are you dealing with that if you > > are > > utilizing the data for reporting? > > > > Thanks for your input, > > > > Susan Palmer > > ShopperTrak > > > > ARS 7.0.1P2 > > Oracle 10g > > Windows Server 2003 > > User/Admin: 7.0.1P3 > > > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where > > the Answers Are" > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where > the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
