I keep exploring OIC features and find them quite powerful and flexible. In this blog, I would like to share a scenario to automate document records upload into Oracle HCM Cloud I came up with. It might be useful to load a batch of scans of personal documents in bulk for many employees and my scenario meets this requirement. I accommodated the On-Premises Connectivity Agent functionality to create a local shared stage area where user can put scans in the PDF format with the certain name convention like: <PersonNumber>_<DocumentType>_decription.pdf
Check this blog for details on how to install and configure a connectivity agent.
My OIC integration polls this shared area and parses a filename and loads the documents for employees into Oracle HCM Cloud.
For demonstration purposes, the integration handles only two document types but can be easily extended to the required number of document types.
Below is a short video that demonstrates a scenario in action:
I hope you find it useful. Feel free to reach to me and we will help you in building any complicated integration in Cloud.
I have been noticing an increasing demand for the Oracle Integration Cloud Service (OIC) for the last couple of years. It is getting extremely strong and keep expanding on new markets. OIC provides a zero-coding (I would say low code) approach for building, deploying, and managing enterprise integration services. I decided to expand my integration knowledge with this service (inspired by Alex MacDonald GitHub) and build some useful scenarios. In this blog, I would like to share my experience working with OIC. You might have read my article – Oracle HCM Cloud: Mass Load Internal Mobility Employee Transactions with a Worker REST API. It shows how to load internal mobility transactions with a Python code. I decided to replicate the same process with the OIC service. OIC is supplied with a large set of predefined adapters. So I used the Oracle HCM Cloud adapter to invoke HCM rest APIs. It took me two days to build up a simple integration process. It is just for demonstration purposes and, of course, it should be expanded with error/file handlings, etc.
This is the integration orchestration flow:
Below are the orchestrion flow steps:
Read file from SFTP
For each person number in the input file
Get an employee self link
Get work relationships by provided link
Pass a WR link to the changeLegalEmployer operation
Concludes the post a brief video that demonstrates the described integration scenario in action: