Resources Vs Status Filters...

Notes on our latest calendar for FileMaker 13,: DayBack
Posts: 142
Joined: Thu Nov 01, 2012 2:36 pm
PostPosted: Mon Feb 02, 2015 10:23 am
Hi,
I thought I had the DayBack terms worked out but I'm still getting confused.

Here's my thinking for a company roster calendar:
    1) Sample Contacts = Employee names (Joe, Fred, Steve)
    2) Resources = Shifts (Days, Nights, Evenings)
    3) Status = ?
I'm wondering whether Resources should in fact be employees rather than the shifts that they are covering?
Do I need the status filter, they currently help to colour code the shifts but that looks like it's duplicating the resources.

Any thoughts?

Thanks
Brian.
SeedCode Staff
SeedCode Staff
Posts: 475
Joined: Wed Jan 02, 2013 11:47 am
PostPosted: Mon Feb 02, 2015 10:41 am
Typically, Resources would be employees, rooms, trucks, etc. I'm not sure how you might handle shifts. Wouldn't that just be the start and end time of the entry? The Status field is optional, as is color coding. HTH -Jeff
Posts: 142
Joined: Thu Nov 01, 2012 2:36 pm
PostPosted: Mon Feb 02, 2015 10:50 am
Hi Jeff,
I initially used Shifts as a resource, as they were a 'thing' that needed to be filled (like a hotel room I suppose). Each shift has to be filled by an employee between the start and end time, it's compulsory.

We have several shifts that run concurrently (office Days, ops Days, client Days etc), so it's helpful to have them displayed differently.

Can events be colour coded without using the Status value list?

Thanks
Brian.
SeedCode Staff
SeedCode Staff
Posts: 475
Joined: Wed Jan 02, 2013 11:47 am
PostPosted: Mon Feb 02, 2015 11:09 am
That sounds like a reasonable use of resources.

We have some guidance for how to work with color-coding here:
http://www.seedcode.com/pmwiki/index.ph ... ventColors

Let me know if there's anything else I can help you with.

Return to DayBack Calendar for FileMaker

Who is online

Users browsing this forum: No registered users and 1 guest

cron
(855) SEEDCODE
support@seedcode.com
Follow us: