Welcome to the Calyx Software Message Boards where you can share ideas and solutions with other Calyx users! Calyx personnel including Tech Support, Development, QA, and Business Planning often visit these message boards unofficially to better understand our customers' needs. To submit your suggestions Click Here.
This discussion forum is a service provided by Calyx Software. Calyx Software does not endorse any particular point of view expressed in this forum or any information provided in it. The use of the information provided by other users in this message board is at your own risk.
Calyx Software Message Board
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      



Transaction LogExpand / Collapse
Author
Message
Posted 10/1/2007 11:09:11 AM


Forum Guru

Forum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum Guru

Group: Forum Members
Last Login: 6/26/2008 6:48:15 AM
Posts: 70, Visits: 237
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.



Thanks for your help,

John Hoopes

Post #5961
Posted 10/1/2007 11:27:51 AM


Sepal

Sepal

Group: Moderators
Last Login: Yesterday @ 4:30:31 PM
Posts: 1,178, Visits: 9,169
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?

Disclaimer:  This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post.
Post #5964
Posted 10/22/2007 9:07:29 AM


Forum Guru

Forum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum Guru

Group: Forum Members
Last Login: 6/26/2008 6:48:15 AM
Posts: 70, Visits: 237
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.

Thanks for your help,

John Hoopes

Post #6077
Posted 10/22/2007 10:36:07 PM


Sepal

Sepal

Group: Moderators
Last Login: Yesterday @ 4:30:31 PM
Posts: 1,178, Visits: 9,169
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?

Disclaimer:  This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post.
Post #6086
Posted 5/20/2008 2:39:54 PM


Forum Guru

Forum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum Guru

Group: Forum Members
Last Login: 6/26/2008 6:48:15 AM
Posts: 70, Visits: 237
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. 

Thanks for your help,

John Hoopes

Post #6657
Posted 5/21/2008 7:27:40 AM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: Yesterday @ 9:30:14 AM
Posts: 109, Visits: 1,165
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.

Post #6663
Posted 10/13/2008 11:59:04 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 11/7/2008 7:09:19 AM
Posts: 3, Visits: 8
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.

-RoVar
Post #7323
Posted 10/13/2008 2:14:43 PM


Supreme Being

Supreme Being

Group: Moderators
Last Login: 11/15/2008 10:00:24 PM
Posts: 835, Visits: 1,899
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.

Bryan
Point Product Manager
Post #7325
« Prev Topic | Next Topic »


Reading This TopicExpand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: Emmanuel Huna, Bryan Telford, Jason Beck, Mike Thompson, BetaFisch

PermissionsExpand / Collapse

All times are GMT -8:00, Time now is 3:21am

Powered by InstantForum.NET v4.1.4 © 2008
Execution: 0.234. 12 queries. Compression Enabled.
© 2005 Calyx Software. All rights reserved.