Blog

ILLWCM Day#4


Tags :


Well the 4 day training class on the Java version is over.  The last day covered security, some talks on staging and covering what was missing.

Missing
  • No view was there for just users or just groups.  They were all placed in one index.
  • The actual documentation for the class suggests putting "(  )" around the names to help sort groups to the top.  Not a good way to do things.  I should have a user, group and all view available from the index.
  • Two people could edit the same group at the same time. There was no locking and the last person to save got an error warning of a conflict.  Confusing at best
  • A cache problem with the browser, across numerous machines.  You would find that after using the interface a long time during the day, no amount of refresh would update the index you needed to access.  Preventing you from grabbing some component, group or area you just added.  A restart and logging back in the browser was necessary..

Found
  • You can lock a document when pushing it back though the approval process.  However, only one copy at a time may be back in draft status for the same part of the published site.
  • As I mentioned before, everything you do needs a refresh as you go along.  So to have good practice, just refresh everytime you have added items and wish to leave an index in the navigation.
  • Security can be added to any part of a site, workflow, stage or design can be done.  In order to get to see a portion of content, a person or group needs access to all the components that make the page.

Staging was particularly interesting as you could have multiple development areas in one installation or totally separate servers.  Partial content may be places on staging servers allowing only certain users access.  The help files did not accurately give instructions on configuring this architecture, but synchronization and syndication seemed to be a large part.


To summarize, I like the product and can't wait to see the enhancements that will and can be done.