A.On the customer portal admin dashboard, click Widget Inspector to go to the customer portal and press "Alt + I."

B.Use a WebDav tool to go into File Manager. Open the home.php file to check all the widget rn tags.

C.On the home page of the customer portal, press "Alt + I" to initiate Widget Inspector.

D.On the customer portal admin dashboard, go to Widget Info to find where the widget has been used on the customer portal pages.

A.For all supervisor accounts, open the Add-In tab of the Account Workspace and select the Administrator check box next to the add-in.

B.You can create a serverconfigProperty called supervisorRole, which will be defaulted to false. When you deploy the add-in using the Add-In Manager, you will change the SupervisorRole to true for the Supervisor profiles. The code within the add-in will use this serverconfigProperty to determine if full functionality of the add-in should be allowed.

C.Using the Add-In Manager, go to the Profile Access section of the add-in. For all of the Supervisor profiles, select the Run as Administrator check box.

D.Add-ins are deployed as DLLs to Oracle B2C Service and there is no way to divide permissions of these DLLs.

E.You can deploy the add-in with a configuration file zipped with the DLL. Change the configuration file for the supervisor profiles so that the DLL will allow full access for those users.

A.CRUD permissions for custom objects can be set per profile.

B.Saved custom objects can be used in the development environment of a Customer Portal, but the custom objects must be deployed to be used in the production environment of the Customer Portal.

C.It is not possible to roll back deployment of custom objects.

D.Indexes for custom objects cannot be user defined. They are autogenerated by the system after query analysis.

E.Custom objects can be exported from an Oracle B2C Service instance and imported to a different Oracle B2C Service instance.

F.Fields on a custom object can be created, but they can never be deleted.

A.Run network calls within a separate thread to avoid locking the user interface.

B.Identify your most common requests and pre-load those data in the getcontrol1 ( ) method of each of your add-ins.

C.Implement a caching mechanism, and a data expiration mechanism, within your model to avoid duplicate network traffic.

D.Implement a distinct model for each of your addins to avoid network contention.

E.Update your user interface thread from your network-call thread to allow real time status updates.

A.A unique interaction ID is allocated for each unique user and can be reused by the users for multiple visits for the duration specified by the VISIT_MAX_TIME configuration value.

B.A new interaction ID is automatically created as soon as an old ID expires.

C.In the customer portal framework, each unique visit by a user is tracked through an interaction I

D.In the customer portal framework, each unique visit by a user is tracked through the web session