2Know Magazine: Sharing KM Knowledge
2Know: Sharing KM Knowledge
December 2015 - Magazine No. 195
December 2015 - Magazine No. 195
Edition:

A portal literally means a gate. Therefore, an organizational portal is the gate, the entrance to the organization. According to a common definition, the portal is the entrance gate through and from which we wish the user to access all documents and applications. An organizational portal serves as the entrance gate for organizational workers and one of its main objectives is to manage the corporate knowledge; it enables us to link information, knowledge and data via incorporated windows.

 

Does this definition withstand the test of time?

The cultural changes that have occurred, such as the social networks, which have become a massive time consumer for users of all ages, together with the accelerated digital development pace and an enormous amount of information available at all times have affected our personal content consumption habits as well as raised the expectations from the organizational portal- both in terms of content and technological aspects.

 

What does this mean?

We are accustomed to certain abilities when visiting different websites- searching for information and finding it quickly using Google, performing different activities such as shopping via E-form, paying bills, booking an appointment, keeping in touch with your friends through Facebook, choosing content which interests us on Pinterest, etc. Therefore, expecting similar abilities from the organizational systems at the workplace are merely natural.

 

As a result, one of the substantial trends in this field is changing the organizational conception from "Intranet" to "Digital Workplace". This change of approach is manifested by the following transitions:

  • from an organizational homepage (with similar content for all workers) to a personal homepage
  • from mainly static data to mostly dynamic data
  • from focusing on organizational news to mainly social content
  • from a single content manager/central management to involving multiple content management
  • from using informative language (read) to motivating towards action (do)
  • from a page manager that edits the content to a page manager that is actually a Feed manager
  • from adjusted Desktop design to responsive design
  • from fixed design to design which allows more structural flexibility and dynamic design
  • from flat content to layered content
  • from a focus on navigation and menus to relevant and efficient search functions
  • from searching for knowledge experts to an era of Wisdom of the Crowd in which everybody contributes to the accumulated knowledge.

In conclusion, the digital environment is an inseparable part of our daily conduct and assists us in fulfilling our daily tasks effectively as well as allows substantial saving of resources, including efficient time utilization.

Well, why should our workplace offer a different experience?

 

References:

http://www.kmrom.com/Site/Terms/ViewTerms.aspx?CategoryID=51&Letter=%d7%a4

https://richarddennison.wordpress.com/2015/06/17/10-differences-between-an-intranet-and-digital-workplace-homepage/

 

 

The 2013 version of SharePoint is characterized, among other things, by its Apps architecture- not only are its Web Parts available for use on the website, so are the App Parts which are 'building blocks' structured for setting up the website and as such have their designated uses. Furthermore, the organization can purchase more apps via the Microsoft Application Shop using a model derived from the successful mobile application model.

Nevertheless, there might be a specific organizational need which is not addressed by the existing apps, including those available at the shop. This situation calls for application development.

Application development for SharePoint 2013

Application development for SharePoint 2013 is simple. The various development tools grow more sophisticated with each version and simplify the development process.

In the past, developing code X was applicable exclusively on website X. In order to use the application on another website, one had to conduct some adjustments to the site. These apps, however, are "closed" building blocks, available for use on any website we wish. All you have to do is distribute and utilize. Thus, one app development can serve many organization workers who now do not need to turn to the developer- they can simply search for the relevant app in the organization's app collection. This is Re-Use at its best.

Note: Microsoft has lately decided to change the term SharePoint Apps to the new term SharePoint Add-ins. Click here for a detailed explanation on the Microsoft website.

Hereby are some instruction videos (from YouTube) for getting started with app development in a SharePoint environment:

Introduction to SharePoint 2013 App Model

Developing Apps for SharePoint 2013 with Visual Studio 2013

Developing Apps for SharePoint 2013 with Visual Studio 2012

Of course, there are thousands of other available video manuals of this sort.

Do you want to leverage this option in your organization?

Announce a contest between the organization's development workers involving innovation and entrepreneurship in the field of SharePoint 2013 application development. Provide them with time and incentive and who knows? Maybe one of them will develop the next hot solution for your organization. Your developers will need ideas for what kind of application is needed. Well, announce a contest between all SharePoint users in the organization, in which the users offer innovative ideas for development. These ideas can then be suggested to your application developers!

The 2013 version of SharePoint is characterized, among other things, by its Apps architecture- not only are its Web Parts available for use on the website, so are the App Parts which are 'building blocks' structured for setting up the website and as such have their designated uses. Furthermore, the organization can purchase more apps via the Microsoft Application Shop using a model derived from the successful mobile application model.

Nevertheless, there might be a specific organizational need which is not addressed by the existing apps, including those available at the shop. This situation calls for application development.

Application development for SharePoint 2013

Application development for SharePoint 2013 is simple. The various development tools grow more sophisticated with each version and simplify the development process.

In the past, developing code X was applicable exclusively on website X. In order to use the application on another website, one had to conduct some adjustments to the site. These apps, however, are "closed" building blocks, available for use on any website we wish. All you have to do is distribute and utilize. Thus, one app development can serve many organization workers who now do not need to turn to the developer- they can simply search for the relevant app in the organization's app collection. This is Re-Use at its best.

Note: Microsoft has lately decided to change the term SharePoint Apps to the new term SharePoint Add-ins. Click here for a detailed explanation on the Microsoft website.

Hereby are some instruction videos (from YouTube) for getting started with app development in a SharePoint environment:

Introduction to SharePoint 2013 App Model

Developing Apps for SharePoint 2013 with Visual Studio 2013

Developing Apps for SharePoint 2013 with Visual Studio 2012

Of course, there are thousands of other available video manuals of this sort.

Do you want to leverage this option in your organization?

Announce a contest between the organization's development workers involving innovation and entrepreneurship in the field of SharePoint 2013 application development. Provide them with time and incentive and who knows? Maybe one of them will develop the next hot solution for your organization. Your developers will need ideas for what kind of application is needed. Well, announce a contest between all SharePoint users in the organization, in which the users offer innovative ideas for development. These ideas can then be suggested to your application developers!

 

Written by Rom Knowledgeware
Fax 077-5020772 * Tel 077-5020771/3 * Bar Kochva 23 st., Bnei Brak Postal: 67135