Like other portal engines TNG integrates a versioning system. The basic versioning modes are None versioning for unimportant content, Major Only versioning (1.0, 2.0, etc.) for regular changing important content and Major and Minor versioning (1.0, 1.1, 1.2, ....1.6, 2.0, 2.1, etc) for content that is created by a team.
Besides this Sense/Net introduces the publishing with approval. Whether it concerns content with or without versioning, we can limit publishing by inducting approval. Actually a content element version in the Portal File Structure (PFS) can have several states, which internally are marked: P for last valid (“Published”), L for Locked, D for Draft, A for waiting for Approval and R for Reject.
If approval is required for certain content, after creation or modification the system creates a version waiting for approval. This is only visible for the user who has the permissions to approve it or reject it. When the content is accepted by clicking the Approve button, it gets the next version number with the character P and it is visual for other users.
In a later version we implement a workflow solution which can use those states seamlessly and which takes for the delivery through the system.
When your content is an important part of your business, this solution is an extra guarantee for reliable and error free storage and publishing.
Currently rated 4.0 by 1 people
- Currently 4/5 Stars.
- 1
- 2
- 3
- 4
- 5