Introduction EXTRACT JSON files Since end of 2018 SaaS Cloud provides a new feature to track the status of a data extraction run in BI Cloud Connector (BICC)....
Introduction EXTRACT JSON files Since end of 2018 SaaS Cloud provides a new feature to track the status of a data extraction run in BI Cloud Connector (BICC). Every single run to extract data or keys will produce a JSON file with log information that can be used for monitoring purposes. The naming style per file looks like shown below: EXTRACT_STATUS_DATA_SCHEDULE_<Schedule ID>_REQUEST_<Request ID>.JSON BICC Extract log file for VO data if been chosen in run definition...
Introduction EXTRACT JSON files Since end of 2018 SaaS Cloud provides a new feature to track the status of a data extraction run in BI Cloud Connector (BICC). Every single run to extract data or keys...
Problem Statement Implement data security in Engagement Cloud for users who do not exist in Engagement Cloud Introduction Consider a use case where you want...
Problem Statement Implement data security in Engagement Cloud for users who do not exist in Engagement Cloud Introduction Consider a use case where you want to create a VBCS portal for end users to submit loan applications or service requests which are stored in Engagement Cloud. You need to ensure data security such that the end users can create, update or view only their own data. Engagement Cloud offers strict data security at the user level. But you can potentially...
Problem Statement Implement data security in Engagement Cloud for users who do not exist in Engagement Cloud Introduction Consider a use case where you want to create a VBCS portal for end users to...
Section 3 – Configuring Commerce Cloud This blog is the third and final entry in a series of step-by-step screenshot guides to set up an integration between...
Section 3 – Configuring Commerce Cloud This blog is the third and final entry in a series of step-by-step screenshot guides to set up an integration between Oracle Engagement Cloud and Oracle Commerce Cloud using Oracle Integration Cloud which is detailed in guide here https://docs.oracle.com/cd/E97801_03/Cloud.19A/UsingCCCloudComm/html/index.html. For a full introduction and guidance on how to use this guide please see Section 0 of this series. *The numbering in this...
Section 3 – Configuring Commerce Cloud This blog is the third and final entry in a series of step-by-step screenshot guides to set up an integration between Oracle Engagement Cloud and Oracle...
Introduction In various blog posts we discussed the usage of BI Cloud Connector (BICC) in Oracle SaaS. In our cloud applications for ERP, HCM, EX etc exist...
Introduction In various blog posts we discussed the usage of BI Cloud Connector (BICC) in Oracle SaaS. In our cloud applications for ERP, HCM, EX etc exist various options to store flexible data as we know. One option follows the concept of flexible fields as known as Flexfields. Those are either Key Flexfields (KFF), Descriptive Flexfields (DFF) or Extensible Flexfields (EFF). These data are stored in database tables where the structures are fixed (columns named SEGMENT,...
Introduction In various blog posts we discussed the usage of BI Cloud Connector (BICC) in Oracle SaaS. In our cloud applications for ERP, HCM, EX etc exist various options to store flexible data as we...
Introduction Oracle's Fusion SaaS applications cloud is built on a single data model that connects end-to-end business processes across Human Capital Management...
Introduction Oracle's Fusion SaaS applications cloud is built on a single data model that connects end-to-end business processes across Human Capital Management (HCM), Enterprise Resource Planning (ERP), Customer Experience (CX) and Supply Chain Management (SCM) functionalities. While Oracle is providing a common extension and configuration framework across all Fusion SaaS applications, every pillar has also provided additional purpose-built tools and utilities that supports...
Introduction Oracle's Fusion SaaS applications cloud is built on a single data model that connects end-to-end business processes across Human Capital Management (HCM), Enterprise Resource...
Introduction Engagement Cloud 19A introduces the ability to call IDCS oauth protected REST services. This article explains the setup required in IDCS and...
Introduction Engagement Cloud 19A introduces the ability to call IDCS oauth protected REST services. This article explains the setup required in IDCS and Engagement Cloud, using Oracle Blockchain as the service provider. Note - details on how to call and parse REST services from Engagement Cloud groovy are covered here: Calling REST services from Oracle Engagement Cloud The following components have been used: Engagement Cloud Release 19A IDCS 18.4.2 Oracle Blockchain...
Introduction Engagement Cloud 19A introduces the ability to call IDCS oauth protected REST services. This article explains the setup required in IDCS and Engagement Cloud, using Oracle Blockchain...
Introduction Three major entities of every business/enterprise in most industries, are Customers, Suppliers and Products. In reality, customer, supplier and...
Introduction Three major entities of every business/enterprise in most industries, are Customers, Suppliers and Products. In reality, customer, supplier and product data is required to be stored in all applications and each application might have different data model and data structure requirements. If customer data and product data are not consistently stored in all applications across enterprise, this will result in supply chain inefficiencies, misguided campaigns, and...
Introduction Three major entities of every business/enterprise in most industries, are Customers, Suppliers and Products. In reality, customer, supplier and product data is required to be stored in...
Introduction Here is a typical process for document signing: The document is downloaded and sent via an email. The recipient then prints, signs, scans and...
Introduction Here is a typical process for document signing: The document is downloaded and sent via an email. The recipient then prints, signs, scans and emails the document back. The document is uploaded back to the system of records. This process is slow and tedious, but still works for a single recipient. What if there are multiple recipients who need to sign a single document? Or if there is a hierarchy of signatures required? There can be other complex requirements...
Introduction Here is a typical process for document signing: The document is downloaded and sent via an email. The recipient then prints, signs, scans and emails the document back. The document is...
Introduction This article gives a brief introduction to calling REST services from Oracle Engagement Cloud. It assumes a basic understanding of Groovy,...
Introduction This article gives a brief introduction to calling REST services from Oracle Engagement Cloud. It assumes a basic understanding of Groovy, Application Composer, and the requirements of the REST services that you intend to call. It sets out the basic steps required to setup and make a REST call and describes a couple of code patterns that that can be re-used. The REST services used in the examples come from Oracle Engagement Cloud, so there are no dependencies on...
Introduction This article gives a brief introduction to calling REST services from Oracle Engagement Cloud. It assumes a basic understanding of Groovy, Application Composer, and the requirements of...
