Zheng Tech Blog

Article originally published here . Concur is one of the industry’s most widely used travel and expense management solutions, used by more than 32,000 organizations globally. For companies that are implementing or have implemented Concur, one critical step necessary to fully unleash the power of the platform is the integration process. After implementing Concur, companies often spend a large amount of time on tedious manual work, such as adding new users on new hire events, user off-boarding, manager changes, department changes, etc. These "maintenance" tasks seem trivial at first, but they actually require a major time commitment from Concur administrators, who could be focusing on other critical tasks. Besides, managing Concur’s interaction with other systems, such as HR or financial ledger platforms, introduces more challenges, as these tasks are not straightforward and solutions are not directly provided by any of the applications involved in the integration. Do...

The Informatica Cloud Integration platform is the industry's complete cloud integration platform as a service (iPaaS). Informatica has been continuously playing as the leader role in this space for the 4th consecutive year ( Gartner's margic quadrant for enterprise integration platform ). It's definitely your top choice for data integration management. With the emerging SaaS application on the market, it's essential for integration platform to provide a flexible and efficient connector to integrate various cloud applications in a generic manner. Indeed there are many specific connectors built for individual applications by Informatica (Tier 1 and Tier 2 connectors) or vendors themselves (OEM connectors). But let's face it: most cloud applications evolves quickly on new features and their APIs get updated quicker than you realize. How quickly the connectors can turn around with the most recent API updates? The answer is definitely the connector update lags behind,...

For easy reference, here is a list of version contrast between patchset, WebCenter Portal, Jdeveloper with corresponding WebCenter extensions. (the info is extracted from Oracle doc  1627574.1) Patchset + Bundle Patch WebCenter Portal JDeveloper WebCenter Extension 12c 12.2.1.0.0 12.2.1.0.0 Framework: 12.2.1.0.0.151013.2001 Core: 12.2.1.0.0.151005.0601 dot9 + BP3 11.1.1.9.160119 11.1.1.9.0 11.1.1.9.0.160107.0701 dot9 + BP2 11.1.1.9.8 11.1.1.9.0 11.1.1.9.0.151005.2311 dot9 + BP1 11.1.1.9.2 11.1.1.9.0 11.1.1.9.0.150701.0100 dot9 11.1.1.9.0 11.1.1.9.0* 11.1.1.9.0.150521.2301* dot8 + BP8 11.1.1.8.8 11.1.1.7.0 11.1.1.8.0.150618.0701 dot8 + BP7 11.1.1.8.7 11.1.1.7.0 11.1.1.8.0.150331.0703 dot8 + BP6 11.1.1.8.6 11.1.1.7.0 11.1.1.8.0.141219.1406 dot8 + BP5 11.1.1.8.5 11.1.1.7.0 11.1.1.8.0.141001.1208 dot8 + BP4 11.1.1.8.4 11.1.1.7.0 11.1.1.8.0.140627.1403 dot8 + BP3 11.1.1.8.3 11.1.1.7.0 11.1.1.8.0.140404.0207 dot8 + BP2 11.1.1.8.2 11.1.1.7.0...

In this post, I will go over the basics of two features in WebCenter Content (WCC) - Profile and Folder - and then talk about their own design considerations and usages, and finally discuss their differences. In WCC, the Profile (a.k.a metadata profile or content profile, to differentiate from user profile) is an approach of metadata modeling. The profile is a powerful tool that can be used to manage the metadata fields to achieve efficient processing of content items, such as check-in, update, search, etc. Essentially, content profiles consist of set of rules that manage the display of the metadata fields of content items. Through content profiles, you can control what metadata fields should be displayed/hidden, required or not, read-only/editable, initialized with default value or not, and grouped based on the action to the content – whether you are viewing the content information, checking in, updating or searching. Profile provides the capability to customize the user ...