Before continuing, we should clarify what is meant by an Oracle Live Experience application. In the context of Live Experience, an application isn't an standalone installable, runnable application in the sense of an Android or iOS app, or Microsoft Excel; instead, it's a set of base configuration parameters identified by a client ID.
When you create a client app (an Android, iOS or web app, applications in the traditional sense), you'll use that client ID to register your client app with the Live Experience application. The Live Experience application then governs basic behaviors of your client application, such as:
What digital streams should be recorded (audio, video, or screen share) when your app is participating in a customer engagement.
Whether your app only be available during certain hours.
Whether and at what frequency your app queries customers for call quality feedback.
The Application section has two modes. Initially, it requires you to register and set up your application. Until you register your first application, the application drop-down menu at the top of the screen defaults to Add New. Post registration, it defaults to the latest registered application.
You can easily register your new application with these steps:
Enter the name of the web or native application that you want to integrate with Live Experience.
Click Register New Application.
The Client Secret dialog asks you to note the Client ID and Client Secret that Live Experience generates. Be sure to make a note of these to provide to the authentication server.
Enter a meeting URI, if a meeting will be associated with this application.
A meeting URI is another way to create audio, video, and screen-share engagements but with the added capabilities for the associate to: 1) pre-schedule the engagement and 2) initiate the engagement rather than having the end-user initiate it.
You must submit a custom base-URI scheme that is specific to the meeting-enabled mobile application, and one to which the mobile application is coded to respond. You can't use an http URI because the browser would respond to it. The steps that a tenant must follow are:
Choose and get approval for the unique URI scheme. For example, abcd://.
Code your mobile application to launch in response to it.
Configure the application's URL to fit. For example, abcd://mycompany.app.com/meeting
The URI you enter here is associated with the application and becomes the base URL that an associate uses in the Associate Desktop to set up a meeting. See Configure and Use Meetings to Engage Your Customers for additional information.
After you've made a note of the Client ID and Client Secret, click Ok. I've made a note.
After you have registered your application, clicking Application presents the Application Details screen for the application you select in the drop-down menu at the top of the screen. The Application Details screen displays details about the selected application and gives you options to update or delete the application.
To add an additional application:
In the Details tab, click Add New in the drop-down menu at the top of the screen.
Enter the application name in the Application Name text box.
Click Register New Application.
In the Client Secret dialog, note the values of the generated Client ID and Client Secret.
Enter a Meeting URI if you want to associate a customer meeting with this application.
Click Ok. I've made a note to acknowledge that you've copied the Client ID and Client Secret.
When you delete an application, the client ID, client secret, and customer recording settings associated with the application are also deleted.
To delete an application:
In the Details tab, select the application that you want to delete from the drop-down menu at the top of the screen.
Click Delete Application.
Read the cautionary text in the confirmation window.
If you are certain you want to do so, click Delete Application again.
If you change your mind, click Cancel to cancel the delete operation.
To update an application.
In the Details tab, select the application that you want to update from the drop-down menu at the top of the screen.
Update the application details as needed.
You can change the application name and update the client secret. To update the client secret, see Generate a Client Secret. If you change the client secret, you will need to provide it to the authentication server.
Select an application type, either Native for a mobile application or Web for a desktop application.
Enter a meeting URI, if you want to enable meetings for the application in the form. Enter one of the following
or, for EMEA customers
Click Update to save your changes.
A client secret is generated when you register your application. The client secret is a text string that is known only to the application and the authorization server. You must make a note of it to provide to the authorization server.
To generate a new client secret, access the Details tab in the Application section:
Click Display Secret.
The Generate Secret dialog explains that a new client secret will be generated and that you will need to modify your application with the new client secret.
Click Generate if you wish to regenerate the client secret. Otherwise click Cancel.
Live Experience returns you to the Application Details screen.
Make a note of the new client secret and provide it to your authorization server.
Return to the Docs Home Page