Event applications
Applications to hold an event — a seminar in a conference hall, a club's concert, a talk elsewhere — made on the site in four steps and decided in the panel, with the halls kept on one calendar with the bookings.
Everything below is declared by Event applications itself, so it describes this deployment rather than a manual — and it is rewritten whenever the program changes.
What it is
- Its key is EventApplications, which is also the prefix of every component it owns.
- It is bought: a site has it only when the registry records that this customer bought it.
What it may be allowed to do
These are the permissions it declares. A person sees one of its screens only where his role carries the matching permission.
- eventapps.documents
- eventapps.manage
- eventapps.setup
- eventapps.view
What it puts on a page
2 components, each of which can be dropped onto a page in the composer.
Event application
The form a signed-in visitor applies for an event with: who applies, the event and its hall, then sends it.
Placed as EventApplications.Apply.
It takes no settings — it draws one way and has nothing to be told.
My event applications
A signed-in visitor's own event applications: their state, and editing or withdrawing them.
Placed as EventApplications.Mine.
It takes no settings — it draws one way and has nothing to be told.
Comments
Nobody has written yet. Be the first.
This article is not taking comments.