Hi

I've just upgraded to 2.7.5 mainly because I wanted to have Museremail sorted.  We use this to list contacts on an RFC form and it's much easier to find the ones you want when they are in a predictable sequence.  As an extension to this it would be great if they could be sorted by the last part of their real name - typical user, give him a sweetie and he wants jam on it!

cheers

Steve

I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old?

Thanks in advance,

Chris

I am tring to sort  the attribute, subject, but it sorts with Z on top and A on the bottom. Is there anyway to reverse sort?

Hello All,

The subject is roughly what i'm asking about so here are the details. I have combed through the forums for an answer and didn't come up with anything regarding what i need.

Issue:

Below is what the logbook is setup as. However once there are more than 10 entries on the page, when a user views the logbook, elog automatically puts them to the higher value page # (ie entry number 11 is on page 2).

As I am sorting the entries by status and by Dist or Beat to organize entries for quicker viewing and access, I would prefer that elog always shows on page 1 when a user views the log book. The statuses are setup for sorting properly but when reverse sort is turned on, status "3-Closed" appears at the top instead of status "1-Open" to appear at the top, Status "2-Sent to Next Shift" next, then "3-Closed" after that.

Is there a to just view page 1 without doing the reverse sort?

Theme = default
Page Title = ELOG - $logbook
Entries per page = 10
Attributes = Entered By, Call Type, Date/Time Reported, Customer Name, Customer Phone Number, Location, Dist or Beat, Description, Badge, Updated By, Action Taken, Report Time, Status
List Display = Entered By, Call Type, Date/Time Reported, Customer Name, Location, Dist or Beat, Description, Badge, Updated By, Status
Locked Attributes = Entered By, Updated By
Preset Entered By = $long_name
Preset on edit Updated By = $long_name
Options Status = 1-Open, 2-Sent to Next Shift, 3-Closed
Preset Status = 1-Open
Cell Style Status 1-Open = background-color:red
Cell Style Status 2-Sent to Next Shift = background-color:yellow
Cell Style Status 3-Closed = background-color:green
Type Date/Time Reported = Datetime
Type Customer Phone Number = numeric
Type Report Time = Datetime
Sort Attributes = Status, Dist or Beat
Reverse sort = 0
Use Lock = 0
Summary lines = 0
Self Register = 0

Thanks in advance.

G

We're up to 30 logbooks, 3.2GB data total and Elog damen has now become slow. Performance stats show 100%CPU on startup then reduces. Searches and general UI activity is slow. It runs on a VM with 4GB memory allocated. Up to 15 concurrent users.

Trimming and archiving some data files may help but I gather overall this is underpowered hardware in this instance so what is recommended system requirements for a config like this?

Dear all,

I just wanted to share a small script which I wrote to integrate our ELOG in Slack. This allows us to be notified immediately if there is a new logbook entry directly within the appropriate Slack channels. We're using ELOG V2.9.2-245 but if the log-file format has "Subject, Author, Type" in the header, it should work with any other version. I'm using Pyinotify for the file watch which relies on a Linux Kernel feature (merged in kernel 2.6.13) called inotify, so the script only works on Linux.

Here is the code: https://github.com/tamasgal/elog-slack

Cheers and thanks for ELOG!

Tom

For our application we have a lot of very common events we would like to log.  It would be preferable that for certain events/entries we could setup a single button / quick entry method.  Is there away to accomplish this?