Project Creation
Log into the Fusion Instance and click on navigator. Under configuration section select visual studio option.
Once the visual builder studio page loaded click the create button to create the project as shown in below figure.
Choose the template as Empty Project in the template section and click on next as shown below.
In the properties section you can select the desired wiki markup from the drop down and click on next as shown below.
In the team section you can add your team members and assign the roles to them for this project and click on next as shown below.
Now wait for a few minutes until the visual builder studio creates your project with all the necessary components.
Once the project is created, we need to create the environment. Click on the Environment button.
Provide the environment name and description of your choice and click on create.
Once the environment is created click on create instance.
Select instance type as ‘Oracle Cloud Applications’ and authentication method as ‘Application Credentials’, Provide the base URL, Username and Password of your fusion instance as shown below and click on add.
If the provided instance details and credentials are correct, then only the visual builder studio shows the status and response time for the instance as shown below.
Please save the below extension zip file into your local system from this document. To import the extension into the visual builder studio.
Now click on the workspaces option in the left panel to create the workspace.
Click on Import Option
Click on the Drag and Drop button to select the file from your local system as shown below.
Now select the previously saved extension file.
workspace name and select the repository (you can create the repository of your own from here if you want), as shown below and click on Import.
Once you clicked on the import the visual builder studio will import all the content from the zip file and you can see the components in the left panel as shown below.
After importing the extension, we need to connect the data sources of the fusion. To do that we need to unarchive the below catalogs and must connect the reports with their respective data models. Please follow the procedure below.
Report Uploading
Please find the attached catalogs which consist of data model and the report. unarchive the catalogs in the fusion instance and connect the reports with their respective data models.
DOCUMENET TYPE DOCUMNET DETAIL
Note: Please unarchive the reports in a location where every employee should access to these reports like (custom/Human Capital Management/……)
Correcting the paths in variables
Once the reports are unarchived. We need to change the folder paths in the extension in a few places. Please follow the below procedure to do the corrections.
Navigate to the ‘main-start default’ page and select ‘variable’ tab as shown below.
Select the ‘DocumentTypeBody’ variable and click on properties panel to see the property values.
Open the Default value property in ‘Expression Editor’ Mode.
Now change the Absolute Path in the ‘reportAbsolutePath’ tag with the Document Type Report Absolute path as shown below(if there are any ’[‘ at the beginning and ending of the expression please delete those) and click on save.
Now do the same procedure for the ‘DORDETAILSBODY’ variable and change the default value Expression Absolute path to the Document Details Report Absolute path and save as shown below.
Recreating Connections
In order to fetch the data from the back end we need to create the connections. Click on connections as shown below.
Please delete the existing connections because the extension is created on demo instance so while creation, we used demo instance connections. You can easily delete those by right clicking on the connection name and click on delete button as shown below.
Click on the Service connection button as shown below.
Select Define by End Point
Select Method as Post,
URL: https://fa-etaq-dev5-saasfademo1.ds-fa.oraclepdemos.com/xmlpserver/services/v2/ReportService
in the above URL please replace your instance URL like
https://<your instance URL>/xmlpserver/services/v2/ReportService
Action Hint as Get Many and click on Next.
Provide the Service Name as ‘DocumentType’.
Select the Request tab, select body subtab, and provide the sample text (Please find the attached sample text file below and place your Document Type report path, fusion instance credentials wherever it is mentioned. At run time application use the logged in user credentials.) in the text box as shown below and click on the save example button.
Please provide the ‘DocumentType’ report path username and password wherever it is mentioned in the below sample xml file. This will only be for creation purpose at run time it will not use your creds.
Click on the Test tab and click on the ‘send Request’ button.
Now the visual builder studio evaluates the connection and shows the status. If the status is ‘200 Ok’ then only we must click on the create button to create the connection. If it shows any other status, please check the values and options once again and retry.
The same procedure is to be followed to create other connections the sample text may change according to the data we are fetching. Please find the sample xml file for the ‘DocumentDetails’ connection Creation.
Please provide the ‘Document Details’ report path username and password and a sample document type and person number wherever it is mentioned in the below sample xml file. This will only be for creation purpose at run time it will not use your creds.
Action Chain Corrections
Navigate to Action chains tab and select the ‘ButtonActionChain’ as shown below.
Select the First action call rest and click on select button.
Now select the newly created endpoint ‘DocumentDetails’ and click on select.
Once you select the newly created ‘DocumentDetails’ endpoint we need to provide the mappings. Click on the Not Mapped button of body parameter.
Now map the ‘DORDETAILSBODY’ variable to the Target Parameters body and click on save as shown below.
Now go back to the action chains list by clicking on Action Chains link.
Select the RunningReport Action Chain.
Select the first action and click on the select end point option as shown below.
Now select the newly created ‘DocumentDetails’ endpoint and click on select as shown below.
Now click the Body parameter Not Mapped Button.
Now Map the ‘DORDETAILSBODY’ variable with the parameters body and click on save as shown below.
Now click on the Action chain link and come back to the action chains list.
Select the ‘CredentialsClose’ action chain.
Select the second action and click on select.
Now select the ‘DocumentType’ end point and click on select.
Now click on the Not Mapped button of Body Parameter.
Map the ‘DocumentTypeBody’ Variable to the Body parameter and click on save.
Now click on the preview button and check the report. If the browser asks for any permissions to download multiple files or to allow open other tabs. Please allow the browser by providing permissions.
Credits:
Bindu Bhargav Kollipara
bhargav.kollipara@mpccloudconsulting.com
MPC Cloud Consulting Private Limited
