WebGate Anywhere 3.x
 How is the system technically protected against access from others?
WebGate Anywhere manages all content in a database system. All access to the database is controlled by the WebGate Anywhere pulisher so that direct access by a Web user is impossible. Are there pre-defined groups within a role concept?
WebGate Anywhere bings four pre-defined user roles for author, designer and admin jobs.
Individual roles can be added and can be used with workflow, access control to templates etc. Can the groups within a role concept be freely defined?
Any user or group can be assorted to any user role. Which kinds of notification to individual employees does the system know?
Approvers are notified by mail when a new document is submitted for approval.
Authors are notified by mail when a document has been published ba an approver or when approval has been denied. Is there an authorisation cycle which is defined or can be freely organised for publications on the website?
WebGate Anywhere contains an integrated workflow component. Workflows can be defined any way and can be attached to any document type (template). Workflows can have different tiers. Within any tier the number of approvals needed to access the next tier can be defined (4-eyes-principle). Is there a protection against inadvertent simultaneous access of several people to one document?
A working copy has to be generated to edit a document. This working copy can only be edited by the author that generated it (as long as no co-authors have been defined).
When a document is submitted for approval, the authoring rights are withdrawn so that the document can no longer be subject to alteration. Which kinds of system-internal task lists and status information are there?
Documents in WebGate Anywhere have one of four stati: "draft", "review", "published" or "archived".
Each change in the status of a document is registered so that the information is kept who is responsible for which change of status. Are authorisation procedures supported?
WebGate Anywhere contains an integrated workflow component. Workflows can be defined any way and can be attached to any document type (template). Workflows can have different tiers. Within any tier the number of approvals needed to access the next tier can be defined (4-eyes-principle). When the last tier has been passed the document is published. [Basic information] [Asset managament] [Availabilty] [Content syndication] [Expandable] [Import] [Performance] [Personalisation] [Workflow] [XML] | 
Update this entry
Downloads
