Employee further training is nowadays one of the key challenges various industries (education, energy, medicine & health, manufacturing, etc.) are facing. As opposed to the past, when all training took place on paper, today learning can and should take advantage of computer-based, interactive technologies – to put it simply: digital learning.
Every year billions of dollars are wasted due to inefficient meetings. Especially now, in the COVID-19 crisis, we all need to pay attention to effective and efficient meetings. It’s about analyzing our environment at breakneck speed, reducing costs, conserving liquidity, developing new markets and identifying the right support programs, to name just a few of the challenges.
I spend over 25% of my “normal” business life in meetings. I have led good and bad meetings and attended good and bad ones. In this post, I have taken the opportunity to briefly summarize the most important success factors for effective (doing the right things) and efficient (doing things right) meetings from my own perspective.
Last Wednesday the OpenText Enterprise World took place – the purely digital version. The “real” version, which was supposed to happen last week in Prague, was transformed in light of the COVID19 situation.
I “attended” the show and the official part is just over. Let me give you a short overview of the most important topics, as well as the news around OpenText Documentum.
Mark Barrenechea’s (CIO and CTO of OpenText) key note revolved around two catchwords. One was “Resilient Enterprise”, which covers several aspects. OpenText have acquired several companies that deal with IT security products and have integrated their products into their portfolio. In addition, “resilient” also refers to the ability of companies to continue to function in today’s world with Remote Work – with the help of OpenText products.
Many thanks for the great feedback we received on our recent blog post > Best Practices Checklist for Large-scale Relocation of Work From the Office to Working From Home.
As a brief follow-up, we want to share some useful links to content focusing on the behavior while working from home. My colleagues from fme AG compiled the link collection to adjust to the changed working conditions.
This guide aims to assist companies in the large-scale relocation of work from the office to working from home for reasons such as a pandemic. It does not query the establishment of workstations from home in general. For this approach the list might not be complete and is legally not secured. Nevertheless, the given tips can be used for this purpose. We provide the guide free of charge and will publish in multiple chapters or blog posts. Some chapters cover topics such as managing employees and teams who are working from home or the usage of specific tools such as EMDS, Teamware, etc.
This chapter covers some basic ideas of IT support in terms of equipment and tools for working from home.
What OpenText announced at Enterprise World 2019 in Toronto for the InfoArchive Roadmap has already been realized by fme: Setting up a container-based infrastructure for OpenText InfoArchive.
Microservice architectures are often a graph of components distributed across a network. This architecture gives rise to a new problem. How can we trace and bind together all services involved in one operation request? When a client calls an operation, it can be spread across different services over the network, each service has its own context.
Building a search form in older versions of InfoArchive was very painful specially when building searches for linked tables (Table-based archiving). Finally, InfoArchive 16EP4 release and higher added many search composition enhancements such as:
- Ability to see column properties like Data Type, Encrypted Field, Export Enablement, Filter Enablement, Sorting and Hidden column during composition.
- Simplified nested search mapping and multiple set support
- Repeating attribute support
- Operator support and nested search visibility
- Derive from list-multi select control as a target.
- New data types support FLOAT, BIGDECIMAL, and BIGINTEGER.
Docker containers (https://www.docker.com/resources/what-container) have become an industry standard for cloud-native applications due to their smaller size and resource need compared to the VM-based solutions. Since Docker 17, it is possible to use multistage builds (https://docs.docker.com/develop/develop-images/multistage-build/) to create small scratch-based containers.
Obvious advantages of this approach are the size of the resulting container as well as a reduced surface for potential attacks due to a very limited number of components. But does using scratch also have some unexpected “side-effects”? Let’s look into this using a small Golang-based Program.
It is the 08th of July 2019 at 7:30 o’clock. At fme AG’s office in Brunswick, everything looks like it is going to be a normal Monday morning. The first employees are making themselves comfortable at their workplaces and trying to dispel their tiredness with a hot cup of coffee. Some people wonder about the whereabouts of the dishes and cutlery before going back to their desks to turn on the computer. But the supposed calm is deceptive. Because this week shouldn’t be an ordinary one.