I have an application where guests are allowed to create new records, and browse existing records in the table.

What I would like is to allow guests to capture their email addresses when creating a new record, but not allow guests to see the email address in the table or form view. Administrators should of course be able to view/edit/create the email address field

I don't think this is currently possible.

I think you would need to add Create, Edit,View permissions for each fabrik element and allow for each of those actions to set one of the ACL roles. The for Create you would set that to everyone, and View/Edit you would set to Administrator, in order to achieve the above scenario.
__________________

I'm thinking to something like this: I have more tables coming from the same or different database, even databases from different connections; I want to get a web page displaing data from an advanced search like system where I may select any field from any table belonging to any databases as above to produce data to display in a webpage.

With the ability to edit a record open to a wide audience, it would be nice to be able to recover from either a malicious edit, or simply an incorrect edit, by reverting to a prior version of the table row.

If you think about the way a Wiki works, the past versions of the definition are available so that changes can be rolled back to any prior version of the record.

This may need to be a privileged function as well - available only to a specific user level.

One feature I would REALLY like to have in Fabrik is:

On database join elements, if the target table is 'known' to Fabrik, have an option to "show other data".

Then, when displaying the form with the join element, Fabrik would render the joined tables data as a read-only (detail) view inline with the current form.

So ... instead of like we currently have ...
Code:

Order Number: _______
Customer: [dropdown to customer table]
Cost: ______
Blah: ______

... it would look like:
Code:

Order Number: _______
Customer: [dropdown to customer table]
Name
Address
Phone
Email
URL
Cost: ______
Blah: ______

Ideally, this would be AJAX loaded when editing a form, so the included data changes when you change the dropdown selection.

I think this would a) just be flat out useful, and b) go a long way to solving a lot of the muddles people get in with table joining vs join elements.

ok so I've created a table that link to another child table (related data link) now let say I then create/edit a couple of records on this child table, then how can I get back to the parent table listing(beside making like 20 clicks on the back button)?

It will be very interesting to be able to add a link to the parent table of a related data table.

I love the date and time input fields, but there's one thing missing that I think could be very useful.

The field's options allow us to have only the date or both the date and the time, but there's no option (that I could find) to have only the time. I don't this would be a big effort and it'd be pretty useful.

If you guys need any help just let me know and I'll do my best.

http://fabrikar.com/forums/showthread.php?t=8774

As talked about in this thread: http://fabrikar.com/forums/showthread.php?t=10644 (but with incorrect terminology at first), I think it would be great to have one more ACL for elements.

Right now, there is a choice of setting the Access level for a read-only version of the element in edit mode. My request is to add another option for completely hiding it in edit-mode (based on user level) as a separate option then hiding it completely from both edit and detail views. This way it would be possible to display in detail view, but be completely hidden in edit view for users without permission.

This is useful for creating a reports system where the user starts a form, the admin extends it, then sends it back to the user's account as a list of completed reports. The fields that the admin is going to extend shouldn't display in the the initial form.