OracleCloudnotes

we all know that converting a scheduler integration to REST is quite easy , where as the reverse is not possible and the only way to achieve it is through creating a wrapper scheduler integration and invoking the trigger one as child from there. But there is another way through which we can achieve the direct conversion. For that please refer to below example. Note : Every step mentioned has to be done very carefully Create Scheduler Integration. I’ve created a base one in which it invokes a SOAP service.  I’ve created a small trigger integration which I’m going to change to scheduler without any wrapper. Please follow the below steps to convert rest based to scheduler:     1)    Export the integration.     2) Rename the iar file to zip.     3) Now unzip the file.     4)    Compare the properties files of both scheduler and rest based integration and make the changes to rest based as per the scheduler integration After changes Now open the resources folder: Move the scheduler resour

Introduction In this article I will be explaining about triggering the PCS application from the chatbot. Main article Many of us might have known about triggering the PCS integrations from the OICS or VBCS. Have you ever done it from chatbots? Let’s build a dummy process application in first place which we want to trigger from the chatbot. The main purpose of this would be to notify the user over the mail with the details that he had filled in the form. In this case I have created a message-based process and named it as chatbot. Create a basic form with two fields UserID and IntegrationName. Now create a new message-based process: For the message action at the begin providing the details as below: Select the form in the User Task (Submit) action: Now Follow the below steps to get the integration configured in chatbot environment: 1.        Go to the settings section and select API services. Provide the details as below : Once done go to the authentication section and

  Introduction In this article I will be explaining about triggering the OICS integration from the chatbot. Main article Many of us might have known about triggering the OICS integrations from the VBCS or PCS. Have you ever done it from chatbots? Let’s build a dummy integration in first place which we want to trigger from the chatbot. The main purpose of this would be to notify the user saying that the integration got triggered from the chatbot. Now Follow the below steps to get the integration configured in chatbot environment: 1.        Go to the settings section and select API services Provide the details as below : Once done go to the authentication section and select basic authentication from the drop-down list: Provide your OIC credentials. No in the methods section, provide the input payload for the integration call. Click on test the request and save the response: In this case it would be blank as the integration type is asynchronous (no feedback). Now please refe

  Introduction In this blog I will be explaining on overcoming the limitation of having a stop action in a synchronous Integration. Main Article The main goal of this article is about achieving to stop the synchronous integration wherever its required. In case of Asynchronous Integration by default we get at stop action at the end of the Integration whereas in synchronous integration by default we can’t use it. But when you want to stop the integration abruptly at any point, how to achieve it. There are three ways to do it: 1)       If you want to get rid of the return at the end and convert it to stop, in other words if you want to convert synchronous to asynchronous, uncheck the configure response payload option in the trigger.   2)       Use throw new fault action at point to stop the integration abruptly irrespective of if it is synchronous or asynchronous.   3)       This one may or may not work in some cases…drop a choose action and on the TRUE path dro

   Introduction: Wait is the most common thing we use to slow down the process at any given point of time, but this wait action is by default disabled for synchronous integrations. Main Article: Create a JavaScript ( syncWait  let  ) with the below Code: function syncWait(waitTimeinmillisec) {   const begin = Date.now();   while ((Date.now() - begin) < waitTimeinmillisec){   }   return waitTimeinmillisec; } now call this JavaScript in your synchronous Integration with the seconds you want to halt your integration * 1000. Call this JavaScript in places you need in your synchronous Integration. That's it you had overcome the synchronous Integration Limitation. Example: -Preetham Konjeti.

Introduction: In the XSLT mapper of OICS by default we don't have the while loop to implement, but there can be a situation where we need to implement while , when such situation shows up how to implement it? Main Article: In the above XML, the filename is static....say we need to populate the same field with 5 file names in a single shot in other words to bring dynamism to the Code we have to use loop. Lets do it using While loop. But in XSLT we don't have while loop by default, then how can we achieve this? Just like functions in any other languages we have a thing called 'Template' in XML. Using this we can achieve the while loop. 1) In the above code, match='/'  indicates the default template to be called , In this case the default templated calls the ' customWhile ' template which we had created with parameter 1 as the input. 2) Once the template is called in the very first step as check would be performed to check the input param falls in our desir

  Introduction : In this blog I will be explaining about creating a chatbot and integrating with your VBCS application. Main Article: Chatbots are the coolest things that everyone would love to have in their application. Let’s start by building a basic chatbot which suggests you a place to visit in India based on your food preferences. STEP1 : ·        Go to the skills section of your digital assistant. ·        click on the Add Intent and rename it to ‘suggestPlaces’ and then go to utterances section of and provide your input. ·        Basically, utterances are the initial conversations that would be started by the humans in a chatbot. once you are done with providing your utterances. click on the train with ML at the top of the page and wait till it gets completed.   STEP2 : ·        Go to the entity section and create an entity (type: valuelist), basically this decides the entity/category to which the user input belongs to. ·        Create an entity with name food. ·