Merge branch 'main' into sb-ogg-1

Author: mihai-tudor-oracle

.github/workflows/banned_file_changes_pr.yml

@@ -3,7 +3,7 @@ on:
   # pull_request:
   #   branches: [ "**/*" ]
   pull_request_target:
-  
+
 jobs:
   check_for_banned_file_changes:
     name: Look for unsupported (banned) file modifications on PRs
@@ -31,7 +31,7 @@ jobs:
           echo 'Changes to files in .github are not allowed.'
       - name: Comment if .github changed
         if: contains(steps.files.outputs.all_files_changed, '.github')
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **Banned Files Modified**
@@ -43,15 +43,15 @@ jobs:
           echo 'Changes to license_policy.yml are not allowed.'
       - name: Comment if license_policy.yml changed
         if: contains(steps.files.outputs.all_files_changed, '"license_policy.yml"')
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **Banned Files Modified**
             Changes to `license_policy.yml` are not permitted.  Please revert your changes and re-submit a new PR.  Simply changing the file back to its original state and re-committing won't work (you must revert the changes made to it).
           repo-token: ${{ secrets.GITHUB_TOKEN }}
       - name: Look for changes to repolinter.json
         if: contains(steps.files.outputs.all_files_changed, '"repolinter.json"')
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **Banned Files Modified**
@@ -63,7 +63,7 @@ jobs:
           echo 'Changes to repolinter.json are not allowed.'
       - name: Look for changes to sonar-project.properties
         if: contains(steps.files.outputs.all_files_changed, '"sonar-project.properties"')
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **Banned Files Modified**
@@ -76,4 +76,4 @@ jobs:
       - name: Fail on banned file changes
         if: contains(steps.files.outputs.all_files_changed, '.github') || contains(steps.files.outputs.all_files_changed, '"license_policy.yml"') || contains(steps.files.outputs.all_files_changed, '"repolinter.json"') || contains(steps.files.outputs.all_files_changed, '"sonar-project.properties"')
         run: |
-          exit 1
+          exit 1

.github/workflows/license_audit.yml

@@ -31,7 +31,7 @@ jobs:
         run: echo "${{ steps.analysis.outputs.unapproved_licenses }}"
       - name: Comment if analysis finds unapproved licenses
         if: steps.analysis.outputs.unapproved_licenses == 'true'
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **License Inspection**

.github/workflows/repolinter.yml

@@ -34,7 +34,7 @@ jobs:
           echo "Errored: ${{ steps.analysis.outputs.errored }}"
       - name: Comment if analysis finds missing disclaimer
         if: steps.analysis.outputs.disclaimer_found == 'false'
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **FAILURE: Missing Disclaimer**
@@ -47,34 +47,34 @@ jobs:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
       - name: Comment if analysis finds missing readme
         if: steps.analysis.outputs.readme_file_found == 'false'
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **FAILURE: Missing README**
             The README file seems to be missing.  Please add it.
-            
+
             Details:
             ${{ steps.analysis.outputs.readme_file_details }}
           repo-token: ${{ secrets.GITHUB_TOKEN }}
       - name: Comment if analysis finds missing license
         if: steps.analysis.outputs.license_file_found == 'false'
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **FAILURE: Missing LICENSE**
             The LICENSE file seems to be missing.  Please add it.
-            
+
             Details:
             ${{ steps.analysis.outputs.license_file_details }}
           repo-token: ${{ secrets.GITHUB_TOKEN }}
       - name: Comment if analysis finds copyright notice missing
         if: steps.analysis.outputs.copyright_found == 'false'
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :warning: **WARNING: Missing Copyright Notice(s)**
             It's a good idea to have copyright notices at the top of each file.  It looks like at least one file was missing this (though it might be further down in the file - this might be a false-positive).
-            
+
             Details:
             ${{ steps.analysis.outputs.copyright_details }}
           repo-token: ${{ secrets.GITHUB_TOKEN }}

CONTRIBUTING.md

@@ -0,0 +1,55 @@
+# Contributing to this repository
+
+We welcome your contributions! There are multiple ways to contribute.
+
+## Opening issues
+
+For bugs or enhancement requests, please file a GitHub issue unless it's
+security related. When filing a bug remember that the better written the bug is,
+the more likely it is to be fixed. If you think you've found a security
+vulnerability, do not raise a GitHub issue and follow the instructions in our
+[security policy](./SECURITY.md).
+
+## Contributing code
+
+We welcome your code contributions. Before submitting code via a pull request,
+you will need to have signed the [Oracle Contributor Agreement][OCA] (OCA) and
+your commits need to include the following line using the name and e-mail
+address you used to sign the OCA:
+
+```text
+Signed-off-by: Your Name <[email protected]>
+```
+
+This can be automatically added to pull requests by committing with `--sign-off`
+or `-s`, e.g.
+
+```text
+git commit --signoff
+```
+
+Only pull requests from committers that can be verified as having signed the OCA
+can be accepted.
+
+## Pull request process
+
+1. Ensure there is an issue created to track and discuss the fix or enhancement
+   you intend to submit.
+1. Fork this repository.
+1. Create a branch in your fork to implement the changes. We recommend using
+   the issue number as part of your branch name, e.g. `1234-fixes`.
+1. Ensure that any documentation is updated with the changes that are required
+   by your change.
+1. Ensure that any samples are updated if the base image has been changed.
+1. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
+   what your changes are meant to do and provide simple steps on how to validate.
+   your changes. Ensure that you reference the issue you created as well.
+1. We will assign the pull request to 2-3 people for review before it is merged.
+
+## Code of conduct
+
+Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If you'd
+like more specific guidelines, see the [Contributor Covenant Code of Conduct][COC].
+
+[OCA]: https://oca.opensource.oracle.com
+[COC]: https://www.contributor-covenant.org/version/1/4/code-of-conduct/

SECURITY.md

@@ -0,0 +1,38 @@
+# Reporting security vulnerabilities
+
+Oracle values the independent security research community and believes that
+responsible disclosure of security vulnerabilities helps us ensure the security
+and privacy of all our users.
+
+Please do NOT raise a GitHub Issue to report a security vulnerability. If you
+believe you have found a security vulnerability, please submit a report to
+[[email protected]][1] preferably with a proof of concept. Please review
+some additional information on [how to report security vulnerabilities to Oracle][2].
+We encourage people who contact Oracle Security to use email encryption using
+[our encryption key][3].
+
+We ask that you do not use other channels or contact the project maintainers
+directly.
+
+Non-vulnerability related security issues including ideas for new or improved
+security features are welcome on GitHub Issues.
+
+## Security updates, alerts and bulletins
+
+Security updates will be released on a regular cadence. Many of our projects
+will typically release security fixes in conjunction with the
+Oracle Critical Patch Update program. Additional
+information, including past advisories, is available on our [security alerts][4]
+page.
+
+## Security-related information
+
+We will provide security related information such as a threat model, considerations
+for secure use, or any known security issues in our documentation. Please note
+that labs and sample code are intended to demonstrate a concept and may not be
+sufficiently hardened for production use.
+
+[1]: mailto:[email protected]
+[2]: https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html
+[3]: https://www.oracle.com/security-alerts/encryptionkey.html
+[4]: https://www.oracle.com/security-alerts/

ai-and-app-modernisation/README.md

@@ -3,10 +3,10 @@
 
 On Oracle Cloud Infrastructure (OCI), business users and developers find a comprehensive portfolio of tools and services to create, modernize, and extend enterprise applications.
 
-This area includes Application Integration, AI Services, Content Management, as well as many other exciting low code and no code services.
+This area includes Application Integration, AI Services, as well as many other exciting low-code and no-code services.
 
 For more details, also see [oracle.com](https://www.oracle.com/): 
-[Application Integration](https://www.oracle.com/integration/) | [Artificial Intelligence Services](https://www.oracle.com/artificial-intelligence/) | [Content Management](https://www.oracle.com/content-management/)
+[Application Integration](https://www.oracle.com/integration/) | [Artificial Intelligence Services](https://www.oracle.com/artificial-intelligence/)
 
 # License
 

ai-and-app-modernisation/ai-services/README.md

@@ -2,12 +2,20 @@
 
 Oracle Cloud Infrastructure (OCI) AI Services is a collection of services with prebuilt machine learning models that make it easier for developers to apply AI to applications and business operations. The models can be custom-trained for more accurate business results. Teams within an organization can reuse the models, datasets, and data labels across services. OCI AI Services makes it possible for developers to easily add machine learning to apps without slowing down application development.
 
-Reviewed: 30.01.2024
+Reviewed: 17.10.2024
+
+# Team Publications
+- [Cloud Coaching - Low Code embraces Oracle Cloud Infrastructure AI services](https://www.youtube.com/watch?v=0oHixpA9JDc)
+    - Learn how to create applications that read, modify, and classify documents with a couple of clicks using our low code development platform and some of the OCI AI services offering.
 
 # Table of Contents
 
-  - [Useful Links](#useful-links)
-  - [Reusable Assets](#reusable-assets)
+- [AI Services](#ai-services)
+- [Team Publications](#team-publications)
+- [Table of Contents](#table-of-contents)
+- [Useful Links](#useful-links)
+- [Reusable Assets](#reusable-assets)
+- [License](#license)
 
 # Useful Links
 

ai-and-app-modernisation/ai-services/ai-document-understanding/README.md

@@ -2,16 +2,19 @@
 
 Oracle Cloud Infrastructure (OCI) Document Understanding is an AI service that enables developers to extract text, tables, and other key data from document files through APIs and command-line interface tools. With OCI Document Understanding, you can automate tedious business processing tasks with prebuilt AI models and customize document extraction to fit your industry-specific needs.
 
-Reviewed: 30.01.2024
+Reviewed: 17.10.2024
 
 
 # Table of Contents
 
-  - [Team Publications](#team-publications)
-  - [LiveLabs and Workshops](#livelabs-and-workshops)
+- [Document Understanding](#document-understanding)
+- [Table of Contents](#table-of-contents)
+- [Team Publications](#team-publications)
   - [Reusable Assets Overview](#reusable-assets-overview)
-  - [Useful Links](#useful-links)
+- [Useful Links](#useful-links)
+  - [LiveLabs and Workshops](#livelabs-and-workshops)
   - [Customer Stories](#customer-stories)
+- [License](#license)
 
 # Team Publications
 
@@ -43,6 +46,8 @@ Reviewed: 30.01.2024
 - [Document Understanding (Insurance Document) Key Value extraction demo](https://youtu.be/QsFqaRxtV1s)
 - [Cloud Customer Connect - How to Train Your Oracle AI Cloud Service Model](https://community.oracle.com/customerconnect/events/604740-oci-how-to-train-your-oracle-ai-cloud-service-model)
     - In this session, we demonstrate how you can use OCI AI services, to create custom models using the data labeling, vision, and document understanding service.
+- [Cloud Coaching - Low Code Modular RAG-based Knowledge Search Engine using Oracle GenAI](https://www.youtube.com/watch?v=KkVomurY_0Q)
+    - In this coaching session, you’ll learn how to use low-code integration with Oracle Integration Cloud to integrate and orchestrate social media channels like WhatsApp, Business channels like a Web Application built in Oracle Visual Builder, productivity channels like OCI Object Storage, local large and small language models (LLMs), and vector databases to ingest live data into the RAG-based Knowledge Search Engine store. 
 
 # Useful Links
 

ai-and-app-modernisation/ai-services/generative-ai-service/speech-genai/LICENSE renamed to ai-and-app-modernisation/ai-services/ai-document-understanding/ai-email-invoice/LICENSE

@@ -0,0 +1,22 @@
+# Invoice Document Processing from Gmail into ERP systems using OCI Document Understanding & Oracle Integration Cloud
+
+In this article, we'll explore how we can process invoice documents from Gmail into an ERP System in real-time using OCI Document Understanding and Oracle Integration Cloud (OIC). 
+This solution combines a low-code approach to capture Gmail messages in real-time with Google Cloud Pub/Sub Adapter, extract invoice data with AI Document Understanding and create invoices in ERP systems using Oracle Integration Cloud ERP adapters.
+
+Reviewed: 30.10.2024
+ 
+# When to use this asset?
+ 
+See the README document in the /files folder.
+ 
+# How to use this asset?
+ 
+See the README document in the /files folder.
+ 
+# License
+ 
+Copyright (c) 2024 Oracle and/or its affiliates.
+ 
+Licensed under the Universal Permissive License (UPL), Version 1.0.
+ 
+See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE) for more details.