Calyx Software Message Board / Calyx Point / Suggestions & Requests / Transaction Log / Latest Posts

RE: Transaction Log

Bryan Telford — Thu, 18 Dec 2008 22:20:48 GMT

It was a priority in our 7.0 release due out in March, but we had to get other big priorities done as well, such as field level rules and document storage/attachment. However, this type of functionality for the audit trail is going to be in v7.1.

RE: Transaction Log

jack5083 — Thu, 18 Dec 2008 06:18:29 GMT

This feature alone would make me upgrade. Seems Our company is not alone with the problems that persist when fields are changed only to get a clear to close and numbers no longer match up. I think this feature needs to be made a priority in the next version.

RE: Transaction Log

Bryan Telford — Mon, 13 Oct 2008 14:14:43 GMT

We had looked at doing this for the next release, but had to triage the priorities so other items could make it in. Look for this in the late summer 09 release.

RE: Transaction Log

go123 — Mon, 13 Oct 2008 11:59:04 GMT

I agree as well. I've used DataTrac before and it has a great log feature. I also use QuickBooks Online edition which has a similar feature. Who did it, which field, what time, old data, new data. Simple to do, the log for Point would be at the file level and would probably not end up too big. Once the first user has created the file (or imported from a web app) and saved it, only subsequent changes would be tracked. 200 or 300 changes? 100 or 150 bytes per log entry? Looks like between 20 and 45kb to me, per new file. That's overhead very well spent. :w00t:

RE: Transaction Log

ChrisSauerwein — Wed, 21 May 2008 07:27:40 GMT

I'd like to go on record as saying that I'd love a transaction log as well.

A basic collection of all data field changes each time the file is saved would be a lifesaver in many instances. The tracking of who made the changes could/would be tied to party who initiates the save.

RE: Transaction Log

Hula — Tue, 20 May 2008 14:39:54 GMT

I am sorry, what do you mean by the term "version"? How would you find the previous version of a file? Would that entail several copies of each loan?

We would like to see a log of the changes to all fields in a loan. We would like each change to be dated and identifed by user.

RE: Transaction Log

BetaFisch — Mon, 22 Oct 2007 22:36:07 GMT

what about remembering each version of the file and who saved this version. This way you could compare any version to the current or previous?

RE: Transaction Log

Hula — Mon, 22 Oct 2007 09:07:29 GMT

I would think a transaction log per File. We are interested in who did what when on a per file basis. I believe you are thinking globally. We want to be able to track on each file basis.

We have an "Open" system all the way through to closing. Repeatedly, we are just moments away from closing, only to find changes have been made. Or rather, everyone is claiming changes have been made. Then the finger-pointing begins.

We feel that a detailed transaction log of each file, would cure these issues. As well as a terrific troubleshooting tool.

We have an system, DataTrac, used for our "Banking" transactions, which has a transaction log for each file. Their transaction log has revealed countless PROCESS errors, which we addressed.

RE: Transaction Log

BetaFisch — Mon, 01 Oct 2007 11:27:51 GMT

That's going to be a very large log file. But are you looking to log PDS supported fields or all the fields in the Point file?

Transaction Log

Hula — Mon, 01 Oct 2007 11:09:11 GMT

We need to know who changed what field when. Since, we are now on PDS, each of us has a individual login a transaction log could be made available to us. When try to troubleshoot, balance, or audit, Point has no transaction log.

That is my million dollar suggestion, add a tranaction log to see who did what when.