Unexpected REST connector calls
A Data page is created in Requestor scope. The data source for the data page is a REST Connector.
The connector appears to call the corresponding web service far too many times for unknown reasons.
Steps to Reproduce
1. Create a REST connector.
2. Create a datapage and use the above connector as data source.
3. Access a property of data page in ApplicationProfileSetup activityin order to preload the data page upon user login.
An issue in the custom application code or rules,
the usecase is to load the DataPage as soon as a user log into the Portal. the ApplicationProfileSetup activity get called whenever a new requestor get created. This includes child requestors created from H requestors. Some actions from portal creates child B* requestor from H* requestor.
Because the data page is at requestor level, the creation of child requestors also load the Data page and hence invoking the REST connector.
Perform the following local-change steps:
- Remove the access of Data Page property (used to trigger the page load) from ApplicationProfileSetup.
- Add the Datapage property in a section shown in the Portal with “Hidden Text” control.
Published July 28, 2016 - Updated October 8, 2020
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.