Claromentis intranets and digital workplaces continue to grow in scope. In fact, just recently, our teams have worked hard to expand our digital workplace strategy to include three new intranet components.
Here’s a quick summary of these new components, and how they will help aid your own digital transformation:
Our new intranet components for your digital workplace
Anniversary/birthday intranet component
The anniversary/birthday intranet component allows you to display upcoming employee birthdays and work anniversaries.
This will aid your employee engagement strategy by celebrating your employees’ milestones. It will also improve the employee experience with your intranet, turning it into an interactive digital workplace that delivers more than just information management tools.
File review intranet component
The file review component gives you at-a-glance insights into which documents are in need of updating.
The major advantage of this component is how configurable it is; you can show due dates to all staff, or just the owner of the document, to make it really clear when something is overdue for review. This is an effective digital workplace tool that will improve employee productivity and information accuracy.
RSS reader intranet component
The RSS reader intranet component makes reading news or events easy, be it from an external source or using your own internal RSS feed.
This handy digital tool allows two modes of reading: one is a fixed feed experience – designed for when you want a feed readable but not editable; the second makes use of custom metadata, allowing your end user to configure where the news is coming from, so that the intranet component is always personal to them.
This concept of incorporating the review date into metadata makes a lot of sense to me. One thing I would like to know however is the capability of using the review date and name of the user to send a notification to that person?
@robertr This would be entirely possible however would need to be run from the background process, as opposed to through a component – remember a component is only run when people visit a page it is active on, meaning someone could end up getting a notice 3 days after the due date due no-one activating the component.
If you’ve got the flexibility available to run this through a cron, then yes it’d be entirely plausible.
Excellent post, one of the few articles I’ve read today that said something unique! One new subscriber here 🙂
A really well written post, thank you for your hard work, please keep it up
Great post, great blog!
Your blog is really great.
🙂