s
menu menu

Login  |  Register search:   
Search Blog
Enterprise Forms Blog
Jan29

Written by:EThuongmai Support
1/29/2006 6:50 PM 

With the introduction of a rich text editor for editing HTML fields, Enterprise Forms users now can freely create and edit rich content without requiring any knowledge of HTML.  This article describes how to use Enterprise Forms to create and publish content via a designated approval process.


Enterprise Forms form template designer has an mini approval process whereby designated form creators can create content, whether it is a web form or just an article, the form template goes through a mini approval process before it can be publish for public viewing.  The workflow for publishing form template is a 6 step approval process.Â

  • Once a form template is created by a designated form creator, it is assigned a "Development" state.  This  state is solely for  designing  the form template layout and content.  In addition other meta data information about the form template such as security access controls and roles are defined.  During the "Development" state, the form template can be shared for editing by other form creators.  However in order to have exclusive editing rights to the form template the form template must be locked for editing.
  • Once the form creator is happy with the content and it is properly validated, the form creator then change its state to "Pending Approval".  The "Pending Approval" state is designed to allow users with form template approval role to view the form template to make sure everything is exactly as required before the form approver sends the form template to the next state in the workflow "Pending Publish".  If for example the form template is not up to standards, then it can be send back to "Development" state for further refinement.Â
  • Once a form template is at "Pending Publish" a form template publisher (user with Publish role) can review the publish it to go to "Available" state.Â
  • When a form template reaches the "Available" state, it can be used by the Data Collection Manager for public viewing and use.  If a form template is no longer required after a period of use, it can be "Archived" off by a a form template pubisher.Â

The following details how to use Enterprise Forms form template designer engine to create an publish content

  • Download a sample form template,  "No Workflow Template" from the download page
  • Log in as user with Form Creator access and import the downloaded form template via the Form Template Manager, Import/Export screen
  • Go the Form Details screen of the newly imported form template and Lock the form template for exclusive write access.
  • Modify the form template content via the Form Designer screen.  Once completed, unlock and click on Validate to validate the form template.  If errors generated from Validation, amend the form template accordingly as requested in the error message
  • From this step on wards, you are now ready to approve and publish content
  • Log in as user with Form Creator access and go the Change State screen of the Form Template.  Change the value of "Change State To" field to "Pending Approval..." then click on the Update link button to update changes
  • Log in as user with Form Approval access and go the Change State screen of the Form Template.  Change the value of "Change State To" field to "Pending Publish..." then click on the Update link button to update changes
  • Log in as user with Form Approval access and go the Change State screen of the Form Template.  Change the value of "Change State To" field to "Available..." then click on the Update link button to update changes.  This step will make the form template available for use by the Data Collection Manager.
Once the form template has been publish, add a new instance of "Data Collection Manager - Standalone" module to a page.  Go to its settings and assigned the newly published form template for public viewing.

Tags:

10 comment(s) so far...

Re: Howto use Enterprise Forms as content publisher

In this forum thread: http://www.longnhi.com/Forums/tabid/138/forumid/1/threadid/88/threadpage/1/scope/posts/Default.aspx

... I was exploring the possibility of using EF as a article management system. At the time I decided that EF was not suitable because:
1. Users who are allowed to edit an article are immediately in "edit mode" when they open an article form.
2. Customizing the Report Manager to produce a menu of articles was difficult (Report Manager shows lists as a table, rather than a menu of links).

I am interested by your post about using EF as a content publisher - has anything changed with the module that would make 1 or 2 possible?
FYI, I am still hunting for the 'perfect' content publishing module! I keep coming back to check out EF because it is a very mature product, and the closest to what I need. Other candidate modules are the epContentBuilder, DNN Masters Content Builder, Efficion Articles and the official DNN WIki module, but each has its problems (not actively being developed any more/not yet released/not customizable enough/not yet released)!

By lneville on  2/9/2006 1:41 AM

Re: Howto use Enterprise Forms as content publisher

This article describes the use of the Form Template as an article which goes through an approval process before being published and available for public viewing.

In regards to your point 1:

If a user has Form Creator access in the Form Template Manager module, that user needs to Lock the form template before the user can have exclusive access to editing the form. Thus if a form template (article) is not locked for editing, you will not be able to modify the form template content.

In regards to your point 2:

Because we are only using the Form Template Manager module to design and publish article and not collect content from users we can not use the Report Manager module to display article links. The Report Manager is only used to display collected information from a publish form template. Thus there is a distinction between using Enterprise Forms as a normal web form designer or using it as a content publisher

By ethuongmai on  2/9/2006 2:08 AM

Re: Howto use Enterprise Forms as content publisher

I think I need to explain further about how I see our company using EF as a content publisher. I am sorry my lack of experience with EF may mean these questions have obvious answers!

In my company there will be three roles: 1. People who can create and modify form (article) templates, 2. People who create and modify articles using these templates, and 3. People who can only read articles. People who are in role 1 will also usually be in role 2, but the majority of article writers are only in role 2.

I think I gave you the impression from my question that the users creating the templates are the only ones creating the articles, but that is not the case - the form templates would need to be published.

Given this:
1. I am assuming that a form (article) that someone created could later be edited by the same user or other users in the 'article editor' role (2 above). Is this accurate?
2. If a user is in the 'form template creator' role (1 above) AND in the 'article editor' role (2 above), when they open an existing form (article), will it be presented as read-only i.e. 'flat' content meaning the content fields are not presented in textboxes (but with a button to enable editing).
3. Is it possible to have a role that is just allowed to read articles and nothing more (3 above), who will see articles as 'flat' content meaning the content fields are not presented in textboxes?
4. Given Report Manager could be used to list articles, has anything changed in the presentation options, i.e. I would like to show a menu of links to articles rather than a table with columns? If not, you mentioned coding my own menu module ... just need to confirm the forms data is available in tables as records rather than within an XML document.
Thanks

By lneville on  2/14/2006 3:26 AM

Re: Howto use Enterprise Forms as content publisher

Can you give me any feedback on my latest questions? Should I put them in the forums instead?

By lneville on  2/20/2006 1:42 AM

Re: Howto use Enterprise Forms as content publisher

Appologize for the delayed response.


What we are trying to illustrate in the article is that Enterprise Forms could be used to create content. Content could then go through an approval quality assurance (QA) process. Once the QA is completed it can then be published for public viewing. The Form Template Manager module manages the content creation, approval and publishing. The Data Collection Manager module looks after displaying the published form.


Let us try to map Enterprise Forms Template roles to your company roles

EF Form Creators --> Company Role 1
EF Form Creators/Approvers/Publishers --> Company Role 2
Normal Users --> Company Role 3

In regard to your questions from earlier post:

1. An article here is the Form Template. Thus anyone in Company Role 1 can create the article then later edit the article. However once the articled has been edited, it can not be published again without being approved by users in Company Role 2

2. In Enterprise Forms Template manager module, a form creator can only edit a form template (article) when the Form Template in DEVELOPMENT status. In addition the form creator must have exclusive lock to the form template for editing. If a user does not satisfy the above condition a "read-only" message will appear, and the user can only view content but not edit

3. The Form Template manager should only be granted to users who deal with creating and publishing content. Once the content has been publish, you then use the Data Collection Manager to then display the content in its right format without the grid layout, text boxes, etc. The security of the Data Collection Manager is control via the module's security settings in a normal way. Having said that, it is possible to grant users to only have READ access to the Form Template Manager module.

4. The Report Manager can not be use in this instances because, we are not collection data at all. A new module needs to be created if should be to have some sort of menu system with links to published content.

Hope that helps


By ethuongmai on  2/20/2006 2:25 AM

Re: Howto use Enterprise Forms as content publisher

Ahha I think I see your point now. You are suggesting using form templates as individual articles. In other words, an article about apples would be one template and a second article about oranges would be a second template.
I was imagining creating one template for similar articles (lets say a template for all articles about fruit), and then filling in this form each time I wanted to create an article (i.e. with the Data Collection Manager).
Please confirm if this is what you are saying. If so, my idea might still work ... I will have to test it out on your test site.
One more thing - can you confirm if the forms data (i.e. contents of each field) is available in tables as records rather than within an XML document.

By lneville on  2/22/2006 4:16 AM

Re: Howto use Enterprise Forms as content publisher

That is correct. Our idea of content publishing is using each form template as a separate article. This way it allow more freedom in design layout for the article author.

However, your way of thinking would also work and is infact might be more suited if the articles need to follow the same layout.

The advantage of using a single form template and form intances as articles is that you can use the Report Manager to generate summary view of articles in which you can also have link to full details of the article. In addition, if your form template fields contain mostly Rich Text Editors, then when the form is displayed in Read-only more these fields are displayed as proper labels instead of text boxes as in versions prior to 2.2.

As for data storage, form data are stored in Enterprise Forms tables and not in an XML document. However, you would need to have a knowledge of the XML schema before data cam properly be extracted. One of the ways that you can view captured form data or articles in a table like format is via the Report Manager. When a report template is created, the system generates a database view, which gives you a flat view of all the fields in a table like structure. The advantage of this is that you can use this view in any other SQL

By ethuongmai on  2/22/2006 5:25 AM

Re: Howto use Enterprise Forms as content publisher

Thanks this is all clear now.

By lneville on  2/22/2006 9:59 AM

Re: Howto use Enterprise Forms as content publisher

I have thought in this regard that the term "template" is modestly misleading. We aren't creating form (or content) templates (which could be re-used for various content) ... we're creating forms, or instances of content delivery. Yes, they can be published in more than one place, yet they are tied to the particular content.

In the "Data Collection Manager" which is now really a "Content Publishing Manager" for this particular use ... would anonymous end users be able to select from a dropdownlist various contents which could then be displayed in the same place?

By pmichael on  12/7/2008 7:51 PM

Re: Howto use Enterprise Forms as content publisher

With dabinding and postback are now in place I don't see any reason why you could not have a dropdownlist of content to display via the data collection manager module.

By EThuongmai Support on  12/7/2008 8:24 PM
footer
Update :: March 13, 2010