AdoptOS

Assistance with Open Source adoption

Open Source News

How Does Digital Transformation Counteract Slowdown in the Insurance Industry

Liferay - Mon, 05/21/2018 - 11:14

The insurance industry worldwide is in the midst of digital transformation, with insurance providers attempting to apply new technology and modern ways of doing business to an industry that is both heavily regulated by governments and often reluctant to change ways of doing business that have been in place for years. As such, many institutions within the industry may experience slowdown in their adoption and application of new technologies.

The result is a need for technology that helps support and empower insurance companies to be as fast as possible in how they can adopt new solutions and meet the everyday needs of customers. In addition, this technology must be dependable and highly secure to protect the vital data used within everyday business. However, in order to embrace change, insurance providers must better understand both what is slowing down the digital transformation process in their industry and what modern technology can do to quickly and efficiently embrace change.

Why Does the Insurance Industry Need Digital Transformation?

As discussed by McKinsey, the insurance industry is one of the last to undergo large-scale digital transformation as its companies have been largely insulated against potential disruption. This is due to government regulation, the complexity of the services offered, large capital requirements for being a major member of the industry, complex business networks and a wide array of policies that need to be reviewed during every procedure. Together, these elements have long prevented upstart companies from entering the industry and from fast adoption of new technology suddenly changing the way business is commonly done.

However, the continuing advancements made via digital transformation in other industries have now come to the insurance industry. As companies around the world create modern digital experiences and allow customers to shape online services around their individual needs, customers within the insurance industry begin to expect a similar level of service that they experience elsewhere.

The biggest cause of digital transformation in the industry is that insurance is based on customer self-service, which is supported by highly trained employees. Today, modern customers expect digital services that match the precedent set by companies like Amazon. As such, it is important for the modern insurance provider to give audiences a wide array of effective tools built for many different life circumstances, but also a customer experience that flows along easily and helps empower individuals to care for their unique needs.

Along with satisfied customers, the impact of digital transformation on insurance customer self-service can also be seen in finances. According to Forbes, process automation enabled by insurance digital transformation can result in up to a 65% reduction in costs, which is helping to propel transformation in the industry.

How Modern Technology is Speeding Up Insurance

Today, insurance providers around the world wonder what role insurance technology will play in either helping or hindering their standing in the industry. However, the many new insurtech applications being created are meant to enable, not undermine. But in doing so, they can be seen as a disruptor in the industry.

A well-run company should be able to execute in any industry by acquiring and retaining customers. This means that any company looking to embrace digital transformation will require effective tools and a trained team to perform well no matter the industry. The effects of digital transformation within the insurance industry are not the new cause of giant disruption, just the evolution of and continued growth within technology used throughout the industry. Companies who seek to grow and meet modern customer expectations will use these new tools to empower their workforces and long-term business strategies in ways that were not possible beforehand.

Today, brokers are beginning to gain access to data and tools that big insurance companies have had for much longer thanks to the increased accessibility of such solutions. Brokers are attempting to leverage analytics to determine the best and longest-lasting acquisitions for substantial financial gains. However, the vast amount of data being generated by customers and prospects needs to be managed and utilized through predictive analytics in order to create personalized insurance package services, which both individuals and organizations commonly expect in the modern age of insurance.

As a whole, modern insurance companies have made great strides in analytics and have begun applying omnichannel experiences to their online presence. However, most are very early in applying deep customer insights to the data they have collected to create more effective customer experiences.

These new challenges and opportunities mean that insurance providers of all sizes can innovate in exciting, meaningful ways that empower employees and better reach target audiences. Together, they make digital transformation in the insurance industry not just a priority, but a meaningful next step for companies around the world.

What is the State of Insurance Digital Transformation Today?

To help insurance companies better understand their industry today, Liferay conducted a global survey of providers regarding the state of digital transformation. Learn their answers and more insights into insurance digital transformation in our whitepaper.

Read “Insurance in the Digital Age”   Matthew Draper 2018-05-21T16:14:11Z
Categories: CMS, ECM

Four Major Mistakes in Predictive Marketing and How to Avoid Them

Liferay - Mon, 05/21/2018 - 11:00

From dynamic web content to targeted email campaigns to mobile app push notifications, predictive marketing can take on many forms. However, they are all defined by anticipating future needs and interests based on customer data and history in order to shape online experiences for a higher degree of marketing success.

The following four predictive marketing mistakes can frequently occur and negatively impact the campaigns of companies across all industries, as well as the resulting opinions of potential customers. However, solutions are possible so long as businesses are aware of these mistakes, their causes and the ways in which to both prevent and correct errors.

1. Poorly Structuring a Predictive Model

Pulling a large amount of detailed data can give a business the chance to understand the history and interests of individual customers to predict their future needs. However, accessing massive amounts of vital data is only half of the equation when creating a successful predictive marketing campaign. Without a properly researched and structured predictive model, a company may be unable to provide the level of detail and nuanced experiences needed for success. Without proper planning, models may even provide incorrect experiences and product offers.

Solution: As discussed by Target Marketing Mag, successful predictive models prioritize detailed integration of customer data long before they begin applying these insights to the experiences they create. This includes collecting and comparing data from multiple sources so that a single customer view can be created, which not only creates a robust view of individuals, but eliminates errors, such as misspelled names or incorrect assumptions regarding interests. When combined with a predictive score that determines a customer’s level of interest in both product and the business as a whole, a predictive model can have a much lower chance of making critical errors.

2. Starting with a High Profile Project

Every predictive marketing campaign has to start somewhere and after investing time and resources into the systems that enable these targeted campaigns, it may be tempting to kick things off with a high profile, large audience project. However, the cost of error becomes higher the larger a predictive marketing campaign becomes, and it may take some time to smooth out any shortcomings that may affect a campaign.

As highlighted by Computer World, companies had frequently claimed that their predictive models will “revolutionize” their respective industries and, as such, launch high profile campaigns at launch in an effort to wow their target audiences. However, the projects may lead to well-publicized errors and simply be too large and complex to maintain over time, leading to businesses shutting down the projects that they claimed would propel them to the top of the industry.

Solution: Create small, realistic goals for projects that can make a difference in profits but will not have a major negative impact in the case of mistakes. Once successful, build additional, larger projects informed by past successes and failures.

3. Over-Targeting the Customer

Every predictive marketing campaign must walk a fine line between providing an individualized experience and allowing audiences to feel independent in their customer journeys. When a prospect has been over-targeted, he or she may become numb to your company’s marketing efforts or, even worse, begin to resent your business. This includes a constant stream of emails, continually reflecting their shopping history in all online experiences, addressing them by name everywhere and continually shifting website layouts in an attempt to match their interests.

While these experiences can help a customer feel understood by a company, they can also burn them out if they feel continually tracked while online. As customers become warier regarding how companies use their data, an over-abundance of obviously targeted experiences may cause them to seek out competitors.

Solution: A successful predictive marketing campaign should lay out a friendly path before the targeted customer, providing him or her with the products most likely to align with their interests for ease of access and customer support that quickly meets their needs. Consider less obviously targeted experiences and fewer direct communications so that customers feel more at ease with your company handling their data.

4. Leveraging Inappropriate Data

In the modern age of data gathering, many businesses have access to social media, email, shopping history and much more willingly provided by target audiences. However, the trouble begins when a company decides to leverage as much information as they can without discernment regarding whether or not they should put such information to use.

Often, these issues come down to the generic application of big data without crucial segmentation regarding marketing efforts. The result can be wedding congratulations to unmarried targets and baby product advertisements to prospects who haven’t actually announced their pregnancy yet. As discussed by Umbel, it may be tempting for businesses to collect all the data that they can, but the result is often a messy blend of crucial information and bits of insight that should never be used in marketing material.

Solution: When creating parameters for data collection, create clear objectives. What do you plan on using the data for within your marketing campaigns? In addition, what types of data will never be necessary within your predictive marketing? When combined with a system that segments this data as needed, companies can avoid serious mistakes.

Retaining and Engaging Your Customers

Retaining and engaging existing customers for a strong, loyal audience is a major factor in the long-term success of every business. Read more about how to create a return customer strategy that works for you in our whitepaper.

Read “Engage Existing Customers: Four Key Strategies”   Matthew Draper 2018-05-21T16:00:48Z
Categories: CMS, ECM

What is Your Customer Experience Ecosystem

Liferay - Mon, 05/21/2018 - 10:41

Creating, controlling and providing excellent customer experience is a major factor in most companies’ digital business plans today. By striving to provide a pleasant and easy-to-navigate online customer journey, companies can improve their chances that target audiences will be happy with their purchasing process and become return customers.

However, businesses may be too focused on the very specific ideal path that they have crafted for an audience and unaware of the greater customer experience ecosystem that encompasses them. As discussed by Forrester, this ecosystem includes not only the connected touchpoints that a company has created, but the many different people who work within it, as well as other websites, applications and interactions that a potential customer has experienced in relation to your company’s CX, as well as the back-end systems that businesses use to manage their customer-facing touchpoints.

By better understanding the value of a customer experience ecosystem, companies can be prepared to implement successful CX strategies and avoid major ecosystem disruptions that lose customers. The result is consistent, successful long-term CX plans.

Defining a Customer Experience Ecosystem

Forrester defines a customer experience ecosystem as “the web of relations among all aspects of a company - including its customers, employees, partners and operating environment - that determine the quality of the customer experience.” These various elements impact CX in the following ways:

  • Customers - As discussed by Customer Think, customers should be ranked as the highest priority regarding needs within the CX environment due to being the source of funding that propels the entire ecosystem through their purchases. The expectations of customers should influence the way an ecosystem operates, rather than a company attempting to force customers to adapt to their ecosystem. For example, a business that completely overhauls their website to suit their own preferences rather than the preferences and expectations of customers. In doing so, customers can become frustrated and leave for competitors who are more willing to listen to and shape their CX around the needs they have expressed.
  • Employees - While customers are the funding that propels CX, employees are the people that respond to customer demands. When evaluating the ecosystem, consider how well-educated employees are regarding the tools and information at their disposal and how they use these elements to better serve your target audience. By supporting your workforce in serving customer needs and educating them regarding the many aspects of your company’s unique customer experience ecosystem, they can be prepared for a wide array of customer journeys.
  • Partners - In the CX ecosystem, partners can play a crucial role as they often extend the ecosystem further than the touchpoints created by a business in order to reach more potential customers. While this can broaden your target market, it also means that the audience’s perception of your company is influenced by how it is presented by others. Closer partner relationships, well-crafted marketing efforts and systems that integrate with partner data and experiences can help prevent poor communication and negative impressions from influencing the ecosystem.
  • Operating Environment - The software environment in which your users, including customers, employees and partners, run their applications will invariably impact the CX ecosystem, as this influences not only how your systems run, but how different tools and data interact with one another. Should incompatible technology be operating within the same ecosystem, it may result in inaccessible data and difficult transitions within the customer journey

Whether these elements are deliberately connected by companies or have simply been brought together due to the preferences of customers, they form an ecosystem that encompasses a business’ online presence.

Creating a Seamless CX Ecosystem

After determining the many elements that make up a customer experience ecosystem, a business will need to understand how this uniquely applies to their own online presence and what can be done to make the most of it. Through accurate analytics, companies can be made better aware of how their audiences are moving through customer journeys and what touchpoints, both those created by the company and those from third parties, are affecting audience decisions.

Whether potential customers are coming from social media platforms, speaking with representatives over the phone, visiting physical locations in person or coming from targeted advertisements, a well-designed customer experience will be ready to address the unique journeys that come from each of these points of origin and more. This can be done through proper integration with social media, targeted advertisement that also changes web page layouts to suit individual needs and effective back-end system integration that applies customer data in meaningful, targeted methods to customer experience.

The easier that potential customers can move between the elements that make up an ecosystem, the more likely they are to not abandon their journey for another business.

Connect with Your Customers

Today’s businesses need to effectively connect with customers and meet their needs efficiently, but where do you start? Read our whitepaper to learn more effective strategies.

Read “Engage Existing Customers: Four Key Strategies”   Matthew Draper 2018-05-21T15:41:25Z
Categories: CMS, ECM

Liferay Mobile Strategy - ALL the details you need!

Liferay - Sat, 05/19/2018 - 09:28

You want to know more about Liferay Mobile strategies? Check my new video series about Liferay Mobile. Let me know if you have any question.

Video 1 https://youtu.be/R48gQ6bnQpo

Video 2 https://youtu.be/lAT_XjEx8Do

Video 3 - Part 1 https://youtu.be/NOLtn4Y3W9E

Video 3 - Part 2 https://youtu.be/UsDTSF2aMPw

Video 4 https://youtu.be/H0ObNpXRAHU

Video 5 https://youtu.be/VIeyeAz2CXQ

Video 6 https://youtu.be/7bOlD4Xj2E8

 

For the script of the demos in those videos, you can download it from here: https://drive.google.com/drive/folders/12WsD0at0qPXdNFcnNudy6oIdGWwBnMu3

 

Fady Hakim 2018-05-19T14:28:24Z
Categories: CMS, ECM

Liferay Mobile Strategy - ALL the details you need!

Liferay - Sat, 05/19/2018 - 09:25

You want to know more about Liferay Mobile strategies? Check my new video series about Liferay Mobile. Let me know if you have any question.

Video 1 https://youtu.be/R48gQ6bnQpo

Video 2 https://youtu.be/lAT_XjEx8Do

Video 3 - Part 1 https://youtu.be/NOLtn4Y3W9E

Video 3 - Part 2 https://youtu.be/UsDTSF2aMPw

Video 4 https://youtu.be/H0ObNpXRAHU

Video 5 https://youtu.be/VIeyeAz2CXQ

Video 6 https://youtu.be/7bOlD4Xj2E8

 

For the script of the demos in those videos, you can download it from here: https://drive.google.com/drive/folders/12WsD0at0qPXdNFcnNudy6oIdGWwBnMu3

 

Fady Hakim 2018-05-19T14:25:00Z
Categories: CMS, ECM

Liferay Portal 7.1 Beta 1 Release

Liferay - Fri, 05/18/2018 - 16:21
I'm pleased to announce the immediate availability of: Liferay Portal 7.1 Beta 1
 
  Download Now: New in Beta 1 Modern Site Building - Display Pages: Users can now map Basic Web Content articles to editable fields in fragments by creating a Display Page. Users can then select this display page when creating web content articles. Hitting the friendlyURL of the article will render the article on a page using the selected display page.   Fixed in Beta 1

New Features Summary

Modern Site Building: Liferay 7.1 introduces a new way of adding content.  Fragments allows a content author to create content in small reusable pieces.  Fragments can be edited in real time or can be exported and managed with the tooling of your choice.  Use page templates from within a site and have complete control over the layout of your content pages.  Navigation menus now give you complete control over site navigation.  Create site navigation in new and interesting ways and have full control over the navigations visual presentation.        Forms Experience: Liferay 7.1 includes a completely revamped forms experience.  Forms can now have complex grid layouts, numeric fields and file uploads. They now include new personalization rules that let you customize the default behavior of the form.  Using the new Element Sets, form creators can now create groups of reusable components.  Forms fields can now be translated into any language using any Liferay locale and can also be easily duplicated. 
    Redesigned System Settings: System Settings has received a complete overhaul.  Configurations have been logically grouped together making it easier than every before to find what's configurable.  Several options that were located on Server Administration have also been moved to System Settings.     User Administration: User account from has been completely redesigned.  Each form section can now be saved independently of each other minimizing the chance of losing changes.  The new ScreensNavigationEntry let's developers add any form they want to user administration.     Improvements to Blogs and Forums:  Blog readers a can now un-subscribe to notifications via email. Friendly URLs used to be generated based on the entries title. Authors now have complete control over the friendly URL of the entry.   Estimated reading time can be enabled in System Settings and will be calculated based on time taken to write an entry.     Blogs also have a new cards ADT that can be selected from the application configuration.  Videos can now be added inline while writing a new entry from popular services such as: Youtube, Vimeo, Facebook Video, and Twitch.  Message boards users can now attach as many files as they want by dragging and dropping them in a post.  Message boards also has had many visual updates.     Workflow Improvements: Workflow has received a complete UI overhaul.  All workflow configuration is now consolidated under one area in the Control Panel.  Workflow definitions are now versioned and previous versions can now be restored.  Workflow definitions can now be saved in draft form and published live when they are ready.     Infrastructure: Many improvements have been incorporated at the core platform level, including ElasticSearch 6.0 and the inclusion of Tomcat 9.0.  At the time of this release  JDK 8 is still the only supported JDK.  
Documentation Documentation for Liferay 7.1 is well underway.  Many sections have already been completed in the Deployment and Development Sections.  For information on upgrading to 7.1 see the Upgrade Guide. Jamie Sammons 2018-05-18T21:21:31Z
Categories: CMS, ECM

Liferay Portal 7.1 Beta 1 Release

Liferay - Fri, 05/18/2018 - 16:19
I'm pleased to announce the immediate availability of: Liferay Portal 7.1 Beta 1
 
  Download Now: New in Beta 1 Modern Site Building - Display Pages: Users can now map Basic Web Content articles to editable fields in fragments by creating a Display Page. Users can then select this display page when creating web content articles. Hitting the friendlyURL of the article will render the article on a page using the selected display page.   Fixed in Beta 1

New Features Summary

Modern Site Building: Liferay 7.1 introduces a new way of adding content.  Fragments allows a content author to create content in small reusable pieces.  Fragments can be edited in real time or can be exported and managed with the tooling of your choice.  Use page templates from within a site and have complete control over the layout of your content pages.  Navigation menus now give you complete control over site navigation.  Create site navigation in new and interesting ways and have full control over the navigations visual presentation.        Forms Experience: Liferay 7.1 includes a completely revamped forms experience.  Forms can now have complex grid layouts, numeric fields and file uploads. They now include new personalization rules that let you customize the default behavior of the form.  Using the new Element Sets, form creators can now create groups of reusable components.  Forms fields can now be translated into any language using any Liferay locale and can also be easily duplicated. 
    Redesigned System Settings: System Settings has received a complete overhaul.  Configurations have been logically grouped together making it easier than every before to find what's configurable.  Several options that were located on Server Administration have also been moved to System Settings.     User Administration: User account from has been completely redesigned.  Each form section can now be saved independently of each other minimizing the chance of losing changes.  The new ScreensNavigationEntry let's developers add any form they want to user administration.     Improvements to Blogs and Forums:  Blog readers a can now un-subscribe to notifications via email. Friendly URLs used to be generated based on the entries title. Authors now have complete control over the friendly URL of the entry.   Estimated reading time can be enabled in System Settings and will be calculated based on time taken to write an entry.     Blogs also have a new cards ADT that can be selected from the application configuration.  Videos can now be added inline while writing a new entry from popular services such as: Youtube, Vimeo, Facebook Video, and Twitch.  Message boards users can now attach as many files as they want by dragging and dropping them in a post.  Message boards also has had many visual updates.     Workflow Improvements: Workflow has received a complete UI overhaul.  All workflow configuration is now consolidated under one area in the Control Panel.  Workflow definitions are now versioned and previous versions can now be restored.  Workflow definitions can now be saved in draft form and published live when they are ready.     Infrastructure: Many improvements have been incorporated at the core platform level, including ElasticSearch 6.0 and the inclusion of Tomcat 9.0.  At the time of this release  JDK 8 is still the only supported JDK.  
Documentation Documentation for Liferay 7.1 is well underway.  Many sections have already been completed in the Deployment and Development Sections.  For information on upgrading to 7.1 see the Upgrade Guide. Jamie Sammons 2018-05-18T21:19:00Z
Categories: CMS, ECM

Can the agile method apply to digital integration?

SnapLogic - Thu, 05/17/2018 - 12:28

By Mukesh Gehlot Agile is about being able to move quickly and easily – can the agile method be applied to heterogeneous and complex integration projects? Let’s explore. Compared to business applications development that generally focuses on one functional area (e.g., CRM, finance, billing), digital integration cuts across many functional areas. The blueprint behind creating data or process[...] Read the full article here.

The post Can the agile method apply to digital integration? appeared first on SnapLogic.

Categories: ETL

Best Practices and Optimizations for your Product Page

PrestaShop - Wed, 05/16/2018 - 10:11
Your product page is where potential customers make the ultimate decision: to buy or not to buy.
Categories: E-commerce

SnapLogic May 2018 Release: Connecting the digital ecosystem

SnapLogic - Wed, 05/16/2018 - 07:45

We’re pleased to announce the general availability of SnapLogic Enterprise Integration Cloud May 2018 Release. Enterprises need to respond to digital insights faster and we continue to expand and update our cloud integration platform on a quarterly basis to help our customers integrate business critical elements of their digital ecosystem. The May 2018 release includes[...] Read the full article here.

The post SnapLogic May 2018 Release: Connecting the digital ecosystem appeared first on SnapLogic.

Categories: ETL

Fundamentals of Contact Management online training May 17th

CiviCRM - Tue, 05/15/2018 - 17:47

Join Cividesk this Thursday, May 17th for the Fundamentals of Contact Management online training session (12 - 2 pm PT | 1 - 3 pm MT | 3 - 5 pm ET). 

This class is an excellent introduction to managing contacts in CiviCRM and highly recommended for all new users. Click here for more information and to register. Please contact Cividesk Training Manager Susan Engeman, susan@cividesk.com, if you have any questions.

Categories: CRM

Re-envisioning API management – A better approach by Apigee and SnapLogic

SnapLogic - Tue, 05/15/2018 - 16:14

By combining enterprise iPaaS API creation from SnapLogic and a robust API management platform from Apigee, developers can now deliver digital business initiatives faster with less overhead. We just announced our direct integration from SnapLogic Enterprise Integration Cloud to Apigee Edge, also available on Google Cloud, to provide full lifecycle API management. The value of[...] Read the full article here.

The post Re-envisioning API management – A better approach by Apigee and SnapLogic appeared first on SnapLogic.

Categories: ETL

web-portal-design

Liferay - Tue, 05/15/2018 - 15:04
O Design de Portais Web Está Evoluindo

O design de portais web já percorreu um longo caminho desde os tempos de gateways estáticos (como AOL ou Yahoo). A experiência front-end de portais pode ser customizada e refinada, mas o que realmente destaca os portais é sua infraestrutura. Um portal moderno e bem projetado pode conectar centenas de sistemas legados diferentes e transformá-los em uma única solução de negócios simplificada que se adapta à sua empresa.

Esses cinco elementos fundamentais de design de portais web abordam algumas das principais razões pelas quais as empresas decidem criar portais, como permitir uma colaboração mais unificada ou a integração de sistemas. Ao incorporar estes principais componentes, você pode encontrar ganhos imediatos em seu projeto de portal e garantir que você esteja usando a tecnologia da melhor maneira possível.

#1 SSO para Múltiplos Sites

Durante a transição do físico para o digital, diversas soluções de apenas um ponto de contado surgiram nas empresas. Varejistas online, por exemplo, ainda fazem você entrar em um site para ver seus pedidos e outro para revisar seus pontos de recompensa. Ou uma  empresa pode solicitar que seus funcionários realizem login em um site para registrar seu quadro de horários e outro para solicitar reembolsos.

Portais podem conectar múltiplos sites com Single Sign On, removendo a inconveniência de logar em diferentes sites várias vezes. Portais modernos também devem ser configurados com OAuth nativo, que permite aos usuários realizarem login em seu portal através de Facebook, Google ou outra plataforma social.

Utilização na prática:

-     A Hawlett Packard tem um portal global para parceiros que atende mais de 650.000 usuários em 174 países. Cada país costumava ter seu próprio site, mas ao aproveitar a funcionalidade de SSO de uma plataforma de portal, eles conseguiram ter uma URL única e global para enviar para seus parceiros, que precisavam realizar apenas 1 login para acessar tudo que precisavam. O tempo economizado ao manter apenas um site deve ser mais do que suficiente para mostrar a utilidade deste elemento, especialmente para empresas que contam com um histórico de múltiplos sites.

#2 Localização e Distribuição da Comunicação

With the increasing amount of global offices and customer bases, companies need to have a way to manage the translation, localization and distribution of their content. The best portals have sufficient WCM capabilities to create multiple localizations of the same page, allowing administrators to focus on crafting and publishing their communications.

Com a crescente quantidade de escritórios globais e da base de clientes, as empresas precisam ter uma maneira de gerenciar a tradução, personalização e distribuição do seu conteúdo. Os melhores portais contem com funcionalidades WCM suficientes para criar múltiplas localizações da mesma página, permitindo que os administradores de página foquem na elaboração e publicação das suas comunicações.

Utilização na prática:

-     A Domino’s tem uma intranet com sites de suas lojas, franquias e escritórios. O time de comunicação interna envia alertas diferentes e novidades para cada audiência, e como todos os três sites estão no mesmo portal, a equipe pode gerenciar tudo em um só lugar. Isto economiza um tempo valioso que iria ser gasto entre os diferentes sites, buscando documentos e recriando conteúdo em diferentes repositórios. No front end, os usuários apenas veem o conteúdo que é relevante e personalizado para eles.

#3 Componentes Reutilizáveis

Portals should be quick to build across web and mobile. This can mean duplicating standard functionality across multiple sites, such as when an organization needs to create department sites for each of its teams. It can also mean reusing web components when building mobile applications. For organizations that manage a suite of mobile apps, ensuring that your portal enables this reusability from the beginning will put you in a position to innovate faster later.

Portais podem ser construídos rapidamente para a web e móvel. Isto pode ser feito através da duplicação de funcionalidades padrão em diversos sites, quando uma empresa precisa criar sites de departamento para cada time, por exemplo. Também pode significar a reutilização de componentes web ao desenvolver aplicativos móveis. Para empresas que gerenciam uma pacote de aplicativos móveis, assegurar que seu portal permita a reutilização desde o começo pode levar a uma maior inovação.

Utilização na prática:

-     Telx contava com uma necessidade muito específica para seus clientes com um aplicativo móvel nativo que pudesse gerenciar o acesso ao seu data center. Como esta funcionalidade já tinha sido desenvolvida em seu portal, a empresa conseguiu implementar em seu aplicativo móvel sem precisar reescrever nenhum código. Esta habilidade de reutilizar componentes chave através de todos os seus pontos de contato digitais é de extremo valor, e mantém sua experiência consistente com pouco esforço adicional.

#4 Gerenciamento de Workflow

Além do gerenciamento de documento baseado na função de cada usuário, portais permitem que usuários finais sem conhecimento técnico transfiram seus workflows usuais para uma plataforma de colaboração. Workflows avançados podem ser configurados de acordo com a função de cada um, de maneira que os usuários possam enviar suas atividades para seu supervisores. Isto se torna especialmente importantes quando funcionários estão lidando com informações confidenciais de seus clientes e precisam ter certeza que elas não serão perdidas.

Utilização na prática:

-     A Advanced Energy tinha vários estágios de comunicações de pedidos de compra para gerenciar. Ao mover este processo para uma plataforma de portal centralizadora, a organização parou de passar informações por fax, email e telefone. Ao invés disso, a utilização de funções e workflows automatizados, permitiu que seu time tivesse a certeza que as informações estão sendo enviadas diretamente para a pessoa correta, sem nenhum risco de perder o registro delas.

#5 Colaboração

Contar com funcionalidades de colaboração promove o engajamento na maioria dos tipos de portais. Isto é especialmente benéfico para portais de gestão do conhecimento. Às vezes, as equipes usam email como forma de comunicação para um projeto, que rapidamente espalha as informações em várias conversas que não podem ser localizadas ou gerenciadas. Quando você move estes tipos de processos para a mesma plataforma que você gerencia sua biblioteca de documentos, você ajuda seus funcionários a trabalharem de maneira mais eficiente em projetos que incluem membros de outras equipes da empresa. Isto também pode ser positivo em portais para parceiros, por exemplo, onde você trabalha com usuários de diferentes regiões que precisam compartilhar informações sobre seus trabalhos.

Utilização na prática:

-     CitiXsys reconstruiu seu portal do conhecimento para facilitar o compartilhamento de informações para seus usuários e parceiros. O novo sistema reúne uma variedade de serviços, desde módulos de vídeos de treinamentos a fóruns de discussões que são uma maneira de ajudar os funcionários. A colaboração que resulta dos fóruns de discussão intensificou o impacto do portal, e a empresa agora conta com funcionários 3 vezes mais engajados.

Um Bom Design Vai Além do Look & Feel

O design visual e a usabilidade são fatores importantes no design de portais web, mas uma interface de usuário (UI) construída com funcionalidades básicas não irá ajudar as empresas a atingirem o ROI que precisam dos seus portais. Soluções de portais são projetados para desenvolver ferramentas de trabalho digitais personalizadas que ajudam os usuários a realizarem suas atividades, sendo um administrador de sistema realizando a manutenção dos papéis de usuários ou um paciente tentando agendar sua próxima consulta.

  Isabella Rocha 2018-05-15T20:04:59Z
Categories: CMS, ECM

Liferay Faces Portal 3.0.2, Bridge Impl 4.1.1, Bridge Ext 5.0.2 Released

Liferay - Tue, 05/15/2018 - 11:00
Liferay Faces Portal 3.0.2, Bridge Impl 4.1.1, Bridge Ext 5.0.2 Released

Liferay Faces Portal 3.0.2, Bridge Impl 4.1.1, and Bridge Ext 5.0.2 have been released with support for PrimeFaces 6.2, PrimeFaces p:fileUpload mode="simple" (thanks to community member Yeray Rodriguez!), URLs with spaces and more!

Liferay Faces Portal 3.0.2 Release Notes Highlights
  • [FACES-3242] - Upgrade to PrimeFaces 6.2
  • [FACES-3243] - portal: components with javascript (captcha, inputRichText, etc) fail to update with Ajax in Liferay 7.0 GA5

Full Release Notes

Liferay Faces Bridge Impl 4.1.1 Release Notes Highlights
  • [FACES-3242] - Upgrade to PrimeFaces 6.2
  • [FACES-3264] - PrimeFaces file upload fails with PrimeFaces 6.2
  • [FACES-3250] - Primefaces file upload mode=simple does not work (thanks to community member @yerayrodriguez for this contribution!)
  • [FACES-2958] - bridge creates invalid URLs when view params contain spaces in liferay
  • [FACES-3261] - The wrong content type of "text/html" is set for execute "@all" Ajax responses

Full Release Notes

Liferay Faces Bridge Ext 5.0.2 Release Notes Highlights
  • [FACES-2958] - bridge creates invalid URLs when view params contain spaces in liferay

Full Release Notes

Archetypes

Along with these updates, all of our archetypes have been updated to the latest appropriate Liferay Faces, PrimeFaces, and Mojarra artifacts.

JSFSPEC #1433

In order to avoid JSFSPEC #1433, we strongly recommend that all JSF projects update to the latest appropriate Liferay Faces and Mojarra artifacts. JSF 1.2 projects should also add the following context-param to each web.xml file (Liferay Faces Util 2.1.0 and 3.1.0 automatically add the context-param for JSF 2.1+ projects via web-fragment.xml):

<context-param> <param-name>javax.faces.ALWAYS_PERFORM_VALIDATION_WHEN_REQUIRED_IS_TRUE</param-name> <param-value>true</param-value> </context-param>

Please report any issues with this new release in JIRA and ask any questions in our forums.

Kyle Joseph Stiemann 2018-05-15T16:00:00Z
Categories: CMS, ECM

Liferay Faces Portal 3.0.2, Bridge Impl 4.1.1, Bridge Ext 5.0.2 Released

Liferay - Tue, 05/15/2018 - 10:01
Liferay Faces Portal 3.0.2, Bridge Impl 4.1.1, Bridge Ext 5.0.2 Released

Liferay Faces Portal 3.0.2, Bridge Impl 4.1.1, and Bridge Ext 5.0.2 have been released with support for PrimeFaces 6.2, PrimeFaces p:fileUpload mode="simple" (thanks to community member Yeray Rodriguez!), URLs with spaces and more!

Liferay Faces Portal 3.0.2 Release Notes Highlights
  • [FACES-3242] - Upgrade to PrimeFaces 6.2
  • [FACES-3243] - portal: components with javascript (captcha, inputRichText, etc) fail to update with Ajax in Liferay 7.0 GA5

Full Release Notes

Liferay Faces Bridge Impl 4.1.1 Release Notes Highlights
  • [FACES-3242] - Upgrade to PrimeFaces 6.2
  • [FACES-3264] - PrimeFaces file upload fails with PrimeFaces 6.2
  • [FACES-3250] - Primefaces file upload mode=simple does not work (thanks to community member @yerayrodriguez for this contribution!)
  • [FACES-2958] - bridge creates invalid URLs when view params contain spaces in liferay
  • [FACES-3261] - The wrong content type of "text/html" is set for execute "@all" Ajax responses

Full Release Notes

Liferay Faces Bridge Ext 5.0.2 Release Notes Highlights
  • [FACES-2958] - bridge creates invalid URLs when view params contain spaces in liferay

Full Release Notes

Archetypes

Along with these updates, all of our archetypes have been updated to the latest appropriate Liferay Faces, PrimeFaces, and Mojarra artifacts.

JSFSPEC #1433

In order to avoid JSFSPEC #1433, we strongly recommend that all JSF projects update to the latest appropriate Liferay Faces and Mojarra artifacts. JSF 1.2 projects should also add the following context-param to each web.xml file (Liferay Faces Util 2.1.0 and 3.1.0 automatically add the context-param for JSF 2.1+ projects via web-fragment.xml):

<context-param> <param-name>javax.faces.ALWAYS_PERFORM_VALIDATION_WHEN_REQUIRED_IS_TRUE</param-name> <param-value>true</param-value> </context-param>

Please report any issues with this new release in JIRA and ask any questions in our forums.

Kyle Joseph Stiemann 2018-05-15T15:01:32Z
Categories: CMS, ECM

Keeping pace with the evolving omnichannel: Data integration

SnapLogic - Mon, 05/14/2018 - 15:45

First published in Internet Retailing. What keeps customers coming back? It’s the question that forever has and forever will be at the heart of a retailer’s business plan. Rather unhelpfully, however, it’s a question with an answer that is forever changing. Once upon a time, being the only game in town was enough. The emergence[...] Read the full article here.

The post Keeping pace with the evolving omnichannel: Data integration appeared first on SnapLogic.

Categories: ETL

Adding Flexibility to Your Themes Through Gulp Hooks

Liferay - Mon, 05/14/2018 - 14:00

I recently took an online course to learn more about TypeScript, a superset of JavaScript that provides optional static typing, classes, interfaces, and much more. Whenever I'm in the process of  learning a new language/framework/etc. I find it helpful to experiment in a setting I'm already familiar with, where I can  add that new thing a little at a time. Since I work with Liferay themes on a daily basis, I thought it would be a fun experiment to use TypeScript for a theme's main.js file.

At first, I had to compile my TypeScript then move the compiled js file over to the src/js folder in my theme. After doing this a few times I found myself wondering, "there's got to be an automated way to do this." And, there is! Using the example of our liferay-theme-es2015-hook I was able to create a hook that would add TypeScript compilation to the build process; you can see the finished hook here. I'll be using my TypeScript hook as an example of how you could further add custom flexibility to your theme building process.

To create the hook, the first thing to do is initialize a new npm project using npm init to generate and add the necessary fields to the package.json. Next, add the depdencies we'll need  for developing our hook, gulp and liferay-theme-tasks:

npm install --save-dev gulp liferay-theme-tasks

Next create an index.js where the custom gulp tasks will reside.

Depending on what extra processes you would like to add to your theme build, the following steps would be slightly different; adjust for your own project as needed.

Here's the index.js file of the liferay-theme-typescript-hook; let's break down what's happening here.

We've added a few more depenedencies to our hook, gulp-typescript, run-sequence, and typescript. Add the dependencies you need using require statements then export the function for use by the liferay-theme-tasks hook using the standard module.exports.

Next, we'll create the gulp.task we'll want to be picked up and ran in our gulp build/deploy process. In the example, I've created a task called 'typescript:compile' that will be called by the hook.

Finally we tell the hook where to insert the task in the process, since this has to do with my main.js/ts in my src folder I've pointed to 'after:build:src' for further examples you can see the gulp.hook() sequences in the es2015 hook.

And that's it! Now, to make this available for either personal or public use we need to do one of the following: for personal use, from the hook's root folder call npm link to make the npm package available on your system. For public usage simply use npm publish to add your package to the npm public registry.

If you'd like to try the TypeScript hook locally, I've put clear instructions with examples on the repository.

Have fun expanding your theme building workflow!

Alexander Valencia 2018-05-14T19:00:00Z
Categories: CMS, ECM

Adding Flexibility to Your Themes Through Gulp Hooks

Liferay - Sat, 05/12/2018 - 11:58

I recently took an online course to learn more about TypeScript, a superset of JavaScript that provides optional static typing, classes, interfaces, and much more. Whenever I'm in the process of  learning a new language/framework/etc. I find it helpful to experiment in a setting I'm already familiar with, where I can  add that new thing a little at a time. Since I work with Liferay themes on a daily basis, I thought it would be a fun experiment to use TypeScript for a theme's main.js file.

At first, I had to compile my TypeScript then move the compiled js file over to the src/js folder in my theme. After doing this a few times I found myself wondering, "there's got to be an automated way to do this." And, there is! Using the example of our liferay-theme-es2015-hook I was able to create a hook that would add TypeScript compilation to the build process; you can see the finished hook here. I'll be using my TypeScript hook as an example of how you could further add custom flexibility to your theme building process.

To create the hook, the first thing to do is initialize a new npm project using npm init to generate and add the necessary fields to the package.json. Next, add the depdencies we'll need  for developing our hook, gulp and liferay-theme-tasks:

npm install --save-dev gulp liferay-theme-tasks

Next create an index.js where the custom gulp tasks will reside.

Depending on what extra processes you would like to add to your theme build, the following steps would be slightly different; adjust for your own project as needed.

Here's the index.js file of the liferay-theme-typescript-hook; let's break down what's happening here.

We've added a few more depenedencies to our hook, gulp-typescript, run-sequence, and typescript. Add the dependencies you need using require statements then export the function for use by the liferay-theme-tasks hook using the standard module.exports.

Next, we'll create the gulp.task we'll want to be picked up and ran in our gulp build/deploy process. In the example, I've created a task called 'typescript:compile' that will be called by the hook.

Finally we tell the hook where to insert the task in the process, since this has to do with my main.js/ts in my src folder I've pointed to 'after:build:src' for further examples you can see the gulp.hook() sequences in the es2015 hook.

And that's it! Now, to make this available for either personal or public use we need to do one of the following: for personal use, from the hook's root folder call npm link to make the npm package available on your system. For public usage simply use npm publish to add your package to the npm public registry.

If you'd like to try the TypeScript hook locally, I've put clear instructions with examples on the repository.

Have fun expanding your theme building workflow!

Alexander Valencia 2018-05-12T16:58:29Z
Categories: CMS, ECM

Hook for Remote Live Publishing History of web content

Liferay - Fri, 05/11/2018 - 06:16
  portal.properties ----------------------- journal.article.form.default.values=content,abstract,categorization,display-page,related-assets,permissions,custom-fields,Publish History journal.article.form.update=content,abstract,categorization,schedule,display-page,related-assets,custom-fields,Publish History     create Publish History.jsp inside html/portlet/journal/article and put below code <%-- /**  * Copyright (c) 2000-2013 Liferay, Inc. All rights reserved.  *  * This library is free software; you can redistribute it and/or modify it under  * the terms of the GNU Lesser General Public License as published by the Free  * Software Foundation; either version 2.1 of the License, or (at your option)  * any later version.  *  * This library is distributed in the hope that it will be useful, but WITHOUT  * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS  * FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more  * details.  */ --%>   <%@ include file="/html/portlet/journal/init.jsp" %>   <%@ page import="com.liferay.portal.model.BackgroundTask" %> <%@ page import="com.liferay.portal.service.BackgroundTaskLocalServiceUtil" %> <%@ page import="com.liferay.portal.kernel.dao.orm.DynamicQuery" %> <%@ page import="com.liferay.portal.kernel.dao.orm.DynamicQueryFactoryUtil" %> <%@ page import="com.liferay.portal.kernel.util.PortalClassLoaderUtil" %> <%@ page import="com.liferay.portal.kernel.dao.orm.RestrictionsFactoryUtil"%> <%@ page import="com.liferay.portal.kernel.dao.orm.Criterion"%> <%@ page import="com.liferay.portal.kernel.dao.orm.OrderFactoryUtil" %> <%@ page import="com.liferay.portal.kernel.backgroundtask.BackgroundTaskConstants" %>   <div><h4>Remote Live Publishing History</h4></div> <% JournalArticle article = (JournalArticle)request.getAttribute(WebKeys.JOURNAL_ARTICLE); String articleId = article.getArticleId(); try{ DynamicQuery dynamicQuery = DynamicQueryFactoryUtil.forClass( BackgroundTask.class, PortalClassLoaderUtil.getClassLoader()); Criterion criterion1=RestrictionsFactoryUtil.like("taskContext","%##########% "+articleId+",%##########%");         Criterion criterion2 =RestrictionsFactoryUtil.eq("completed", true);                  dynamicQuery.add(RestrictionsFactoryUtil.and(criterion1, criterion2));         dynamicQuery.addOrder(OrderFactoryUtil.desc("createDate")); List<Object> list = BackgroundTaskLocalServiceUtil.dynamicQuery(dynamicQuery); if(list!=null && list.size()>0){%> <div style="max-height:400px; overflow-x:auto"> <table class="table table-bordered table-striped"> <thead class="table-columns"> <tr> <th>#</th> <th>Published On</th> <th>Published By</th> <th>Status</th> <!-- <th>BackgroundTaskId</th> --> </tr> </thead> <tbody class="table-data"> <%for(int j=0;j<list.size();j++){%> <tr> <td class="table-cell"><%=j+1%></td> <td class="table-cell"><%=((BackgroundTask)list.get(j)).getCreateDate()%></td> <td class="table-cell"><%=((BackgroundTask)list.get(j)).getUserName()%></td> <td class="table-cell"><%=BackgroundTaskConstants.getStatusLabel(((BackgroundTask)list.get(j)).getStatus())%></td> <%-- <td class="table-cell"><%=((BackgroundTask)list.get(j)).getBackgroundTaskId()%></td> --%> </tr> <% }%> </tbody> </table> </div> <% } else{%> <div>Either this has not been published or no history available</div> <%} } catch(Exception ex){ ex.printStackTrace(); }     %>   Neha Goyal 2018-05-11T11:16:52Z
Categories: CMS, ECM

Hook for Remote Live Publishing History of web content

Liferay - Fri, 05/11/2018 - 06:16
  portal.properties ----------------------- journal.article.form.default.values=content,abstract,categorization,display-page,related-assets,permissions,custom-fields,Publish History journal.article.form.update=content,abstract,categorization,schedule,display-page,related-assets,custom-fields,Publish History     create Publish History.jsp inside html/portlet/journal/article and put below code <%-- /**  * Copyright (c) 2000-2013 Liferay, Inc. All rights reserved.  *  * This library is free software; you can redistribute it and/or modify it under  * the terms of the GNU Lesser General Public License as published by the Free  * Software Foundation; either version 2.1 of the License, or (at your option)  * any later version.  *  * This library is distributed in the hope that it will be useful, but WITHOUT  * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS  * FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more  * details.  */ --%>   <%@ include file="/html/portlet/journal/init.jsp" %>   <%@ page import="com.liferay.portal.model.BackgroundTask" %> <%@ page import="com.liferay.portal.service.BackgroundTaskLocalServiceUtil" %> <%@ page import="com.liferay.portal.kernel.dao.orm.DynamicQuery" %> <%@ page import="com.liferay.portal.kernel.dao.orm.DynamicQueryFactoryUtil" %> <%@ page import="com.liferay.portal.kernel.util.PortalClassLoaderUtil" %> <%@ page import="com.liferay.portal.kernel.dao.orm.RestrictionsFactoryUtil"%> <%@ page import="com.liferay.portal.kernel.dao.orm.Criterion"%> <%@ page import="com.liferay.portal.kernel.dao.orm.OrderFactoryUtil" %> <%@ page import="com.liferay.portal.kernel.backgroundtask.BackgroundTaskConstants" %>   <div><h4>Remote Live Publishing History</h4></div> <% JournalArticle article = (JournalArticle)request.getAttribute(WebKeys.JOURNAL_ARTICLE); String articleId = article.getArticleId(); try{ DynamicQuery dynamicQuery = DynamicQueryFactoryUtil.forClass( BackgroundTask.class, PortalClassLoaderUtil.getClassLoader()); Criterion criterion1=RestrictionsFactoryUtil.like("taskContext","%##########% "+articleId+",%##########%");         Criterion criterion2 =RestrictionsFactoryUtil.eq("completed", true);                  dynamicQuery.add(RestrictionsFactoryUtil.and(criterion1, criterion2));         dynamicQuery.addOrder(OrderFactoryUtil.desc("createDate")); List<Object> list = BackgroundTaskLocalServiceUtil.dynamicQuery(dynamicQuery); if(list!=null && list.size()>0){%> <div style="max-height:400px; overflow-x:auto"> <table class="table table-bordered table-striped"> <thead class="table-columns"> <tr> <th>#</th> <th>Published On</th> <th>Published By</th> <th>Status</th> <!-- <th>BackgroundTaskId</th> --> </tr> </thead> <tbody class="table-data"> <%for(int j=0;j<list.size();j++){%> <tr> <td class="table-cell"><%=j+1%></td> <td class="table-cell"><%=((BackgroundTask)list.get(j)).getCreateDate()%></td> <td class="table-cell"><%=((BackgroundTask)list.get(j)).getUserName()%></td> <td class="table-cell"><%=BackgroundTaskConstants.getStatusLabel(((BackgroundTask)list.get(j)).getStatus())%></td> <%-- <td class="table-cell"><%=((BackgroundTask)list.get(j)).getBackgroundTaskId()%></td> --%> </tr> <% }%> </tbody> </table> </div> <% } else{%> <div>Either this has not been published or no history available</div> <%} } catch(Exception ex){ ex.printStackTrace(); }     %>   Neha Goyal 2018-05-11T11:16:00Z
Categories: CMS, ECM
Syndicate content