Tagged SaaS

Oracle SaaS Stories: Creating a Custom App Extension with Visual Builder | Part One: Connect Visual Builder to Fusion SaaS API Service Catalog

Visual Builder Cloud Service (aka VBCS), one of the 3 legs of Oracle Integration Cloud (aka OIC), is a low code development environment that is one of the main mechanisms for extending Oracle Fusion SaaS Apps.

In this episode we are connecting VBCS to a SaaS instance, so we can get the different endpoints provided and then use it in the application.

What you need is:

  • a user with access to OIC instance
  • same user with access to SaaS instance

Step 1: Create a new VBCS app

OIC -> Visual Builder
Click [New] on the top right
Select SaaS Template
Provide values and click [Finish]

Step 2: Configure

Go to hamburger menu on top right and select [Settings]
Click on [Services] tab and provide the info

The url to provide has the following format: https://instancefqdm/helpPortalApi/otherResources/latest/interfaceCatalogs

where instancefqdm is your SaaS instance such as https://<id>-<env&gt;.fa.<datacenter>.oraclecloud.com

Click on [Test] button

Step 3: Import the catalog

Click on [Service Connections] icon on the left
Click on [+ Service Connection]
Click on [Select from Catalog]
Click on [FA Services]
Click on one depending on the functional area you want to work with
Wait for the endpoints to appear, expand and select endpoints desired
When you are done click on [Create] on right down corner
Click on [Endpoints] tab and find your endpoints in there

Step 4: Use an endpoint for listing Contacts in a table

Click on [Web Applications] icon on the left, expand flows, expand main, select main-start, locate Table in the Components panel and drag and drop onto the view or onto the Page Structure panel. Click on [Add Data] on the right
Select Contacts and click [Next]
Select or drag&drop fields in the Columns panel. Select the Primary Key and click [Next]
Leave things as it is for now and click [Finish]
Click the “play” button up right
And here it is, you have your contacts page created

And that’s all folks for now, hope it helps! 🙂

Oracle Loyalty Cloud | REST API | Get Service Requests of a Member + Update SR

Photo by Lukáš Kováčik on Pexels.com

The method for geting this info is under the Engagement REST API here.

The call includes a parameter which is filtering by the Member Name as follows:

curl -X GET -k -H 'Authorization: Basic whatever' -i 'https://serverdomain/crmRestApi/resources/"menbernamehere"&onlyData=true'


curl -X GET -k -H 'Authorization: Basic am9ob........DM3Mzg=' -i 'https://xxxx-xxxx-xx-ext.oracledemos.com/crmRestApi/resources/"ad pepelu"&onlyData=true'

   "items" : [ {
     "SrId" : 300000183643204,
     "SrNumber" : "SR105156",
     "Title" : "bbbbb",
     "ProblemDescription" : null,
     "SeverityCdMeaning" : "High",
     "SeverityCd" : "ORA_SVC_SEV1",
     "AssigneeResourceId" : 300000129858698,
     "PrimaryContactPartyId" : 300000183643142,
     "PrimaryContactPartyUniqueName" : "ad pepelu",
     "PrimaryContactPartyName" : "ad pepelu",
     "ExtnsrMgmtFuseCreateLayout_InstallBase_1554923756871Expr" : "false"
   } ],
   "count" : 1,
   "hasMore" : false,
   "limit" : 25,
   "offset" : 0,
     "name" : "serviceRequests",
     "kind" : "collection"
   } ]

Following same API, here an example of how to update an existing SR:

curl -X PATCH -k -H 'Content-Type: application/vnd.oracle.adf.resourceitem+json' -H 'Authorization: Basic am9ob...3Mzg=' -i 'https://serverdomain/crmRestApi/resources/' --data '{
"ProblemDescription" : "Me duele la cara de ser tan feo"}'
   "SrId" : 300000183643204,
   "SrNumber" : "SR105156",
   "Title" : "bbbbb",
   "ProblemDescription" : "Me duele la cara de ser tan feo",
   "links" : [ {
     "rel" : "self",
     "name" : "resourceMembers",
     "kind" : "collection"
   } ]

Hope it helps! 🙂

The Increasingly Important Role of API Management in the Adoption of Integrated SaaS Solutions Together with the Onprem and Third-party Systems

As the adoption of the cloud by companies progresses, we see how an ecosystem of cloud providers is being formed that must be integrated with each other and with the legacy systems of our customers. That is, it confirms what was already intuited, the cloud will be hybrid and multi-provider.

In this order of things it is necessary to incorporate mechanisms that help to govern the entire ecosystem.

This is not new, in the previous decade paradigms emerged to solve the integrations between the different systems that the companies were developing / implementing  mostly onprem. One of the failures that such practices unleashed was not adequately implement mechanisms for the government of the integrations between the different systems.

Nowadays, with the new paradigms of microservices, the concept of API management appears as a new attempt to bring order to the potential chaos that may end up happening if things are not done with common sense.

And it is certainly observed that it is more necessary than ever to adopt mechanisms that allow governing the wide range of APIs that are currently available for any purpose.

The management of APIs must cover the entire life cycle of the same, from its design to its withdrawal, through publication, securization and monitoring.

Oracle API Platform is Oracle’s offer to manage the life cycle of all APIs that a company publishes and consumes.

Oracle also provides a complete set of integration technologies and tools (data integration and ETLs, IoT, SOA, BPM, low code development…)

Enjoy 😉

Oracle PaaS on the rebirth of integration buses in the cloud era: iPaaS | Oracle PaaS en el renacimiento de los buses de integración en la era cloud : Los iPaaS


Whatever the reason for migrating existing environments to the cloud, many born in the post-mainframe era, it is fair to recognize that, just as integration busses helped coexist in the migration of environments when the model of commercial ERPs and CRMs in the last decade, the same happens now in the move to the cloud.

It is a little frustrating to observe that there are companies that recognize that they have customized their ERP or CRM up to 80%, which shows that the good practices that were deduced from the commercial arguments used by the ERP vendors in the 90’s, something like a “do not let IT control your business” has largely failed, either with failed implementations, or environments that have become complex monsters difficult to maintain and evolve in a world where speed is crucial to compete.

Well, it turns out that a common pattern that is observed in any initiative of migration from the ERP’s / CRM’s to the cloud requires an integration platform in PaaS mode (iPaaS) to allow the progressive:

  • connection of new cloud services (SaaS)
  • disconnection of legacy systemsipaas

In addition, the PaaS platform should provide mechanisms to:

  • the extension of functionalities
  • unique user experience
  • DevOps
  • tools for citizen developers
  • Identity and permissions management
  • etc

Oracle Cloud Platform provides these and other functionalities that allow a smooth and progressive transition to the cloud.

For more information on enterprise cloud software consult Oracle SaaS / DaaS


Sea cual sea la razón para migrar los actuales entornos al cloud, muchos de ellos nacidos en la era post-mainframe, es justo reconocer que, del mismo modo que los buses de integración ayudaron a la coexistencia en la migración de los entornos cuando triunfó el modelo de los ERP’s y CRM’s comerciales en la década pasada, lo mismo ocurre ahora en el paso al cloud.

No deja de ser un tanto frustrante observar que hay empresas que reconocen que han personalizado su ERP o CRM hasta en un 80%, lo que demuestra que las buenas prácticas que se deducían de los argumentos comerciales que utilizaban los vendedores de ERP’s en los 90’s, algo así como un “no dejes que IT controle tu negocio” ha fracasado en gran parte, bien con implantaciones fallidas, bien con entornos que se han convertido en complejos monstruos difíciles de mantener y evolucionar en un mundo donde la velocidad es crucial para competir.

Pues bien, resulta que un patrón común que se observa en cualquier iniciativa de migración de los ERP’s/CRM’s al cloud requiere de una plataforma de integración en modo PaaS (iPaaS) para permitir la progresiva:

  • conexión de los nuevos servicios cloud (SaaS)
  • desconexión de los sistemas legacy

Adicionalmente la plataforma PaaS deberá proporcionar mecanismos para:

  • la extensión de funcionalidades
  • experiencia de usuario única
  • DevOps
  • herramientas para citizen developers
  • Gestión de identidades y permisos
  • etc

Oracle Cloud Platform proporciona estas y otras funcionalidades que permiten una transición suave y progresiva hacia el cloud.

Para más información sobre software empresarial en cloud consultar Oracle SaaS/DaaS

Enjoy 😉