webag automat
web content management
|
webag automat 7.1 - what is new? |
|||
Detailed authoring privilegesThe old authoring privilege granting "Insert or delete" on automat-objects has been splitted into
Now you can grant the privilege to insert and/or delete pages to authors and revoke the privilege to modify the folder structure.
Read privileges on folders
Read privileges in the webag automat always belong to single documents. Prior to webag automat 7.1 the webmaster could define a "default read privilege" for a complete web. Each new webpage has been created using the default read privilege.
From now the webmaster can define read privilege defaults for every folder sub-tree. You can grant read privileges to users and/or groups. When a folder read privilege has been changed, the webmaster can decide whether the new privileges should also be saved for existing documents and/or sub-folders. Available options are:
Improved user-interfaceThe folder-index within the authoring system displays documents with differnts icons depending on the document status:
The design of the forms in the authoring system has been improved to support all current browsers. It runs without problems on the actual versions of Firefox, Internet Explorer, Chrome, Safari and Opera. From this release we stop the support for Internet Explorer 6. However, webag automat 7.1 is still running on Internet Explorer 6. New event-triggersWith release 6.4 we intruduced "event-triggers". The first trigger-types where: BEFORE_SESSION_START, BEFORE_PUBLISH_PAGE und AFTER_PUBLISH_PAGE. You can write own PL/SQL-functions to add functionality to the automat behaviour. Now we added two new triggers: BEFORE_SHOW_PAGE fires before a webpage is sent to the users browser. AFTER_SHOW_PAGE runs after sending the page to the browser. URLs to images from the content databaseFiles do not change their filename-url when the author replaces the file with a newer versions and published it. This is important for links to download-documents. For image-files (*.gif, *.jpg, *.jpeg, *.png) we change the filename-url from now on, because sometimes we had problems with proxy-servers sending an old image-version to the browser even if the image had been replaced in the content database.
Bugfixes
|
||||
|