Hi,
would anyone have a suggestion with the following.
CONTEXT:
For most remote employees, visibility and easy communication can be a
challenge. Showing status on work items, requests and work load
(items queued up) is essential (someone had referred to this as
"optics"). SInce this is my case, and I would like to enable folks to
follow progress on projects I manage. So I thought of slowly putting
something together (will probably end up as collection of mini apps).
DESCRIPTION:
So, the first item i am tackling is a request form. But, I would like
to make sure that the tables I use are re-usable in different request.
To do this, was thinking:
1 default table (contains data common to all requests) then another
table, specific to a given request. Example:
default table called 'rm_request' has:
rm_request.ticket
rm_request.title
rm_request.category
rm_request.requested_by
rm_request.email
rm_request.description
rm_request.priority
rm_request.created_on
etc...
The "rm_request.category" field would offer a dropdown. Selecting an
item in that dropdown, should return a sub-form on the same page. TAs
an example, if a user selects "build", then a sub-form should be
loaded (on the same page) where the user would fill out "build"
specific data.
db.define_table('build_request',
Field('ticket',requires=IS_IN_DB(db,rm_request.ticket)),
Field('buildType',requires=IS_IN_DB(db,build_type.name)),
etc...
QUESTION:
So, with all that... would anybody have a sample or something (or
advice/suggestion) on combining 1 default table + (1 drop-down =
another table = subform) where the subform s loaded on the same page
as the default? In my mind, this looks a little like Massimo's
cookbook app but with the criteria described above)
And here's a silly question, if the value of the drop-down's selected
item refer's to a table name, how/where do I retrive that data?
Thanks in advance for your help,
Mart :)
