Lint checker modifications (#59)

* freetier removed

freetier has been removed

* experiential review

experiential review

* Review comments provided by Ravi

Review comments provided by Ravi

* help email

help email

* Title change

Title change

* tile synch with wms

tile synch with wms

* changes to meet standards

changes done to meet standards

* pointed to correct md file

pointed to correct md file

* FBDI Import

FBDI Import

* Review of FBDI Import

Review of FBDI Import

* Title Change as per WMS title

Title Change as per WMS title

* Moved folder structure

Moved folder structure under ERP Cloud

* Bulk Extract and links modified in other labs

Bulk Extract and links modified in other labs

* Bulk extract

Bulk extract

* foldernamestolowercase

folder names to lowercase

* Update create-connections.md

* folder names

folder names

* Feedback by anoosha

Feedback by anoosha and implemented by Subhani

* Indent

Indent in all the workshops

* File2ObjectStorage

File moved to ObjectStorage

* review of core core-competencies

review of core core-competencies workshop as per latest release

* experiential review

experiential review

* updated on Jan 7th

Modified as per the latest version and also file references to the object storage

* Jan 9

Jan 9 as per the new UI

* BIP Report

BIP Report

* opa dp update

* DP Footer summary

* task 12 fixed instructions

* BIP report

BIP report and links in bulk extract

* Delete tracinglevel.png

* Update of objectstorage ref

Update of objectstorage ref

* Update bipreport.md

* Feb 6

Feb 6 update

* Feb 06

Feb 06

* Feb 07

Feb 07

* Atomfeed

Atomfeed

* Atomfeeds

Atomfeeds

* atomfeeds lab

atomfeeds lab

* Atomfeeds

Atomfeeds

* AtomFeed

AtomFeed Feb 16

* Update atomfeeds.md

* Feb 17th update

Feb 17th update

* Feb 17th update

Feb 17th update

* Feb 17th links

Feb 17th : video hub links update

* intro update

intro update

* Intro updated

Intro updated

* Update introduction.md

* File server update

File server update

* object storage link

object storage link updated

* hcm-cloud bulkimport lab

* intro section change

* title change

* intro changes

* title change

* code block changes

* code block fix

* escape characters fix

* escape character fix

* syntax fix

* review by Kishore

review by Kishore

* review

review by Subhani Mar 08

* QA By Kishore

* qa business services ll

* image fix business services ll

* BIP Report setup

BIP Report setup

* Update setup.md

* qa bulk extract

* Updates as suggested by LiveLabs QA

* qa directory sync

* qa get started. fixed oic3 provision path

* qa getstarted fixed file server path

* typo

review

* Minor spell check bulk import

* spell check

spell check

* exp lab prereqs

exp lab prereqs

* ERP extract ll. fixed Configure certificates md reference in manifest

* spell check

* Feedback

Feedback from Bootcamp and Ingrid and Lucy

* LL understand rest adapter-first branch commit

* minor update

* bucket changes

* image fix

* pr corrections

* pr rec changes

* lab fixes post ORDS version changes

* fixed the ords pl/sql code

* folder structure commit for cloud world usecase

* Updated as per the latest release

Updated as per the latest release

* OPA flow

OPA flow

* naming convention

naming convention

* Aug 02

Aug 02 modification, done until creating structured process.

* Aug 02

Aug 02 modification

* Aug 03 modifications

Aug 03 modifications

* Aug 04 modification

Aug 04 modification

* Aug 05

Aug 05

* Aug 05 changes

Aug 05 changes

* Aug 07 noon

Aug 07 noon

* final review

final review

* intro,getstarted,lab1,2,3,4 additions

* subhanis work opa commit

* Vijayas ODA changes

* connector url

connector url

* ODA peer review

ODA peer review

* Aug 09 peer review 8pm

Aug 09 peer review 8pm

* create oda

create oda

* oda and integrations fix

* section added:opa add app roles to users

* opa peer review KK

* peer review changes

peer review changes

* Peer review changes

Peer review changes

* architecture diagram added

* Peer review Aug 11

Peer review Aug 11

* Peer review Aug 11

Peer review Aug 11

* title change

* Integration style modification

Integration style modification

* Peer review

Peer review

* oda changes and image updates -KK

* Aug 12

Aug 12

* remove opa folder

remove opa folder

* Removed OIC Flow

Removed OIC Flow

* added opa and oic flows

added opa and oic flows

* duration

duration

* conclusion sections added to all labs

* link fixed

* fixed copy tags

* table properties updated

* image link and naming convention fixed

* image references fix

* image name ll qa compliance

* oda qa compliance fixes

* copy tag allignment fix

* copy text image allignment fix

* ocw folder addition for getting started oic 3

* ocw folder update and minor instruction fixes

* ocw folder update and instruction fix

* ocw update and additional info added

* minor change of po creation in erp cloud

* fixed xpath filter expression,cloud shell,lab sequence swaps to meet pre conf requirements

* critical changes per product updates

* changed the adw deployment type to serverless

* architecture ocw template

* Oct 03 changes

Oct 03 changes. by Subhani

* HCM Updates done

HCM Updates done

* Common modification

Common modification

* Oct 10

Oct 10 bulk extract, bip report and events

* Oct 11

Oct 11 updates

* Oct 11 changes

Oct 11 changes

* new LL hcm journeys booster opa

* added get started section

* minor edit

* added couple of tasks in get started section

* filename corrections

* PAR resources link

PAR resources link

* oic3 b2b structure commit

* B2B Outbound

B2B Outbound by Subhani

* Update of outbound

Update of outbound

* b2b outbound

b2b outbound

* Inbound started

Inbound started

* Inbound update

Inbound update

* Inbound update

Inbound update

* Updates

Updates of the links

* Feb 16

Feb 16 changes

* Formatting

Formatting

* Format modification

Format modification

* Feb 20 update

Feb 20 update

* Update b2b-trading-partner-manager.md

* get started hc lab

* underscore issues

* from subhani

Outbound and inbound labs

* lab numbering fixed

* title fix

* updates

* added images with rename

* review changes by livelabs team

review changes by livelabs team

* Delete switchAction.png

* b2b file path modification

b2b file path modification

* b2b file path modification

b2b file path modification

* rab ll commit

* lab artifacts par fixed

* added video link in intro

* petty formatting fixes

* peer review changes

* minor updates and typo fixes

* ocw 24 live lab

* updated db invoke changes

* contributor update

* last update change

* removed tbd video link

* fixed lab 6 task 6 indentation

* oic3 provision path fix

* oic provision copied to opa common

* features 2024

* updates on Aug 02

updates on Aug 02

* updates on Aug 03

updates on Aug 03

* architecture diagram

architecture diagram added

* architecture diagram added

architecture diagram added

* Modified in main branch

Modified in main branch

---------

Co-authored-by: kkatta11 <[email protected]>
Co-authored-by: kishore katta <[email protected]>
Co-authored-by: Ravi Chablani <[email protected]>
Co-authored-by: Hope Fisher <[email protected]>
Co-authored-by: Subhani Sahib Italapuram <[email protected]>

oic-gen3/features-2024/events/aboutprojects/projects.md

@@ -20,11 +20,11 @@ This lab assumes you have:
 
 - Completed all the previous labs
 
-## About the projects
+## Task 1: About the projects
 
-You can design, manage, and monitor integrations from a single, self-contained workspace known as a project. This eliminates the need to navigate to other parts of the Oracle Integration user interface (which is required with standalone integrations or integrations in packages).
+1. You can design, manage, and monitor integrations from a single, self-contained workspace known as a project. This eliminates the need to navigate to other parts of the Oracle Integration user interface (which is required with standalone integrations or integrations in packages).
 
-## How project helps you
+## Task 2: How project helps you
 
 With everything at your fingertips, you'll build faster. And, with easy updates to integrations based on accelerators, you'll future-proof your prebuilt integrations. Finally, deploy quickly and with confidence using project deployments. Keep reading to learn more.
 
@@ -52,7 +52,7 @@ With everything at your fingertips, you'll build faster. And, with easy updates
 
     In a project, you can design, manage, and monitor integrations in B2B standalone mode. Use an AS2 Adapter connection as a trigger or an invoke connection, or use an FTP Adapter connection as an invoke connection. Track the processing of B2B messages as integration instances during runtime in the project.
 
-## Restrictions
+## Task 3: Restrictions
 
 - [Restrictions](https://docs.oracle.com/en/cloud/paas/application-integration/integrations-user/manage-project.html#GUID-A26A0ABD-9F80-4E6F-B34D-B7B51E5F43B6__DEF)
 - [Contents of a project](https://docs.oracle.com/en/cloud/paas/application-integration/integrations-user/restrictions-projects.html)

oic-gen3/features-2024/events/introduction/introduction.md

@@ -32,7 +32,7 @@ In this workshop, you will learn how to:
 * An Oracle Free Tier or Paid Cloud Account.
 * A Chrome browser.
 
-## Pub/Sub (Publisher/subscriber) architecture
+## Task 1:  Pub/Sub (Publisher/subscriber) architecture
 
 * Pub/Sub (or Publish/Subscribe) is an architectural design pattern used in distributed systems for asynchronous communication between different components or services. Although Publish/Subscribe is based on earlier design patterns like message queuing and event brokers, it is more flexible and scalable. The key to this is the fact that Pub/Sub enables the movement of messages between different components of the system without the components being aware of each other’s identity (they are decoupled).
 
@@ -42,15 +42,15 @@ In this workshop, you will learn how to:
     ![publisher](../images/publisher.png)
     ![subscriber](../images/subscriber.png)
 
-## Benefits of the Pub/Sub model
+## Task 2:  Benefits of the Pub/Sub model
 
 * The Pub/Sub pattern brings many benefits to the table, including but not limited to:
 * Loose coupling between components, making your system more modular and flexible.
 * High scalability (in theory, Pub/Sub allows any number of  publishers to communicate with any number of subscribers).
 * Language-agnostic and protocol-agnostic, which makes it straightforward and fast to integrate Pub/Sub into your tech stack.
 * Asynchronous, event-driven communication that’s ideal for realtime, low-latency app
 
-## When should you use the Pub/Sub pattern?
+## Task 3: When should you use the Pub/Sub pattern?
 
 * Pub/Sub’s loose coupling, asynchronous nature, and inherent scalability make it an excellent solution for distributed systems with a high and fluctuating number of publishers and subscribers. You can use Pub/Sub for many different purposes, such as:
 * Sending event notifications.
@@ -60,7 +60,7 @@ In this workshop, you will learn how to:
 * Broadcasting updates (one-to-many messaging).
 * Building responsive, low-latency end-user experiences like live chat and multiplayer collaboration functionality.
 
-## Situations where Pub/Sub is a bad choice
+## Task 4: Situations where Pub/Sub is a bad choice
 
 Every design pattern has limitations and trade-offs. There are scenarios where Pub/Sub is the wrong choice:
 
@@ -74,7 +74,7 @@ Every design pattern has limitations and trade-offs. There are scenarios where P
 
 * Synchronous communication: Pub/Sub is designed for asynchronous communication, where the publisher doesn't wait for a response from the subscriber. If you need a synchronous request-response communication pattern, you should consider using something else instead of Pub/Sub.
 
-## Event Design Life Cycle
+## Task 5: Event Design Life Cycle
 
 The publish and subscribe feature enables you to decouple producers and subscribers. This decoupling enables you to define an event and start building your subscriber for the event before the event is published. You can create an event type (can be a producer, subscriber, or someone else). Creating an event type defines a contract, meaning that there's a contract to produce and subscribe.
 
@@ -84,7 +84,7 @@ The event design life cycle consists of three high-level steps. These steps are
 2. Create an event publishing integration
 3. Create an event subscription integration
 
-## Restrictions
+## Task 6: Restrictions
 
 A maximum of 50 integrations can subscribe to events per service instance.