× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We have a request from the auditors it goes as follows:



They want to be able to see in the database journal any changes that were related to a "change request" i.e. all database updates performed by people in IT operation and support. The basic idea is that way the can follow up on grounds of "who did what to this record and why?" The who is the userid that already is in the journal entries. The "why" is the problem part.



Our starting point was that we should set the accounting code of the job to the change request- id that we started working on and hopefully that this accounting code would make its way into the journals. A lot of other job information is in there so why not this?



Apparently the accounting code does not get journaled automatically.



Should it? Will the journaling behavior change if we also start the accounting journal? (Not active at the moment).







Med vänlig hälsning / Best regards


Åke H Olsson



Box 433 SE 551 16 Jönköping Sweden visit: Brunnsgatan 11

phone: +46 (0)36 342976 mobile: +46 (0)705 482976 fax: +46 (0)36 34 29 29

ake.olsson@xxxxxx <mailto:ake.olsson@xxxxxx> www.pdb.se





This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.