![]() |
![]() |
![]() |
|
![]() |
|||
![]() |
|||
![]() |
GoLive 6 Dynamic Content Samples | ||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
||||||
Main View | Administration View | How it Works | ||||||
![]() |
||||||||
![]() |
|
There are three tables in the Stories database: one for the stories, one for the editors, and one for the list of possible workflow statuses. The relationships connecting the tables indicate that an editor might be responsible for many different stories, and that many stories can have the same status. StoriesThe Stories table keeps track of two different kinds of information about a story: its content, and its workflow status. The content is stored in the Title, Author, Summary, StoryText, StoryImage, and Editor fields; the workflow status is stored in WorkflowStatus, ShouldPublish, and Priority. There is also an ID field, which provides a unique number that identifies each story. GoLive automatically adds references to the ID field whenever a page uses Show Details of Current Record. EditorsThe Editors table contains information about story editors. In this example it only keeps track of the editor names. The Edit Story page uses this information to dynamically construct a pulldown menu with all of the editors. StatusesThe Statuses table contains all of the possible workflow statuses. The Edit Story page uses this information to dynamically construct a list of radio buttons to change a story's status. |