Microsoft Teams connector. removeUrl page is not being loaded - microsoft-teams

When I set up may connector, I call microsoftTeams.settings.setSettings:
microsoftTeams.settings.setSettings({
entityId: "MyConnector002",
contentUrl: `https://msteams.whatever.com/connectorsetup.html`,
removeUrl: `https://msteams.whatever.com/connectorremove.html`,
configName: 'Active'
});
I know the settings are being called at the right time because the contentUrl page is appearing when it should. However my connectorremove.html page is not being loaded when I click the "remove" button from the "configure" list ("manage" button). The connector does remove, but the page at my configured removeUrl is not loaded.
I've set console.log, alert and debugger statements at the top of the connectorremove.html page, and they are never hit. So obviously my call to microsoftTeams.settings.registerOnRemoveHandler isn't being hit. If I just copy and paste the removeUrl into a browser address field, it loads fine.

I found what I was doing wrong. The removeUrl page should not be loading in the use case where you select your connector in the "Manage"/"Configured" list, click the "1 configured", then click the "Manage" button. This brings up the page you specified in the settings' contentUrl. You click the "remove" button at the bottom of that page and, instead of the removeUrl being involved, it expects that in the contentUrl page you have set up a remove handler function using the settings.registerRemoveHandler function.

Related

How to redirect to previous page after clicking "ok" on the apex.confirm message box in oracle apex dynamic action

How to navigate back to the previous page after I hit ok on the confirm message box on apex. I used a dynamic action on the delete button but it only deletes the record not navigate back to the previous page. Is my code below correct?
if(apex.confirm(htmldb_delete_message,'DELETE') == true)
{
apex.navigation.redirect(window.history.back());
}
If you are using the default delete button that is created by the form creation wizard, then on the button properties you'll see that the button's behavior target is defined by a javascript which prompts a confirmation window. After the user hits "OK" on that window, the page is submitted so your delete process can execute.
Trying to execute a javascript code before that to force the navigation may be a bad idea and you would have to restructure your delete process to be processed at the right point
Try to create a branch (https://docs.oracle.com/cd/E59726_01/doc.50/e39147/nav_branch_using.htm#HTMDB25149) instead of using a dynamic action to navigate back to previous page. You can configure it to occur "after processing" and either manually set the page that you to go back to or use a hidden item to always go back to the page which the user came from as described in here: How do add a button to go back to another page in oracle apex interactive grid

Modal dialog - refresh the parent page on close modal dialog or submit button

Using Apex 5.1.3
I have everyting working, but I have a requreimet to refresh the entire page (parent page) on the close of the modal page or press submit button.
I have tried quite a few things in dynamic actions on the parent page etc, but nothing is working.
How can I get the parent page to fully refresh when the modal dialog is submitted and closed.
Your help would be most appreciated.
Regards,
Morshed
You could either place a branch after processing on your modal that redirects to the parent page, or create a dynamic action 'on dialog close' on the button/region that invokes the dialog page, which then submits/refreshes the page.
If you think 'nothing is working', put APEX in debug mode, open your browser console, and check if the dynamic actions are actually firing.

Refresh a Fusion block on click of a button wordpress Avada

I have some buttons on a page and on click of each button the page gets reload and the data changes. Now, I would like to refresh that particular fusion block only without reloading the page. The buttons are added to the page as a widget (with some valid reasons) and the fusion block is on the page itself. Would it be possible to achieve what I am looking for?

Remain within magnific popup

I have an ajax popup working nicely with Magnific Popup. However the page that I am loading into the popup via the ajax call contains a hyperlink.
The only contents of the page is:
test
When I click on the "test" link "anotherpage.html" loads in the original parent window.
Is it possible for the page that this link points to to be loaded in the same popup window?
you can achive this effect by following these steps:
download the html page with jQuery into a temporay variable
from the variable get the link address
send Magnific Popup the link you want to display in the first place
for the first part, you can you this great post on stackoverflow: How do I load html into a variable with jquery
for the second task, all you need is to query the first (and only) link in your html page and get it's href attribute:
var target = $('a:eq(0)').attr('href');
now that 'target' variable stores the requested url - send it over to Magnific Popup
include a empty iframe in the popup.
create a function onclick in Test for change the src of iframe and hide or destroy the old thinks in the popup,

AJAX webpage to navigate on previous page

The data is displayed in gridview with paging on an AJAX enabled webpage. The gridView contains Item templates containing a link button. On itemCommand event, page redirects to display data in new page. When the Back button on browser is pressed, the previous state of the page doesn't load.
Perhaps set a cookie and use it to get the right page when initializing the gridview. Or modify the hash at the end of the URL (eg, add "#page2" to the location bar and read it back on init).
Look at this js stuff from google
Use Google Web Toolkit, it allows the state to be bookmarked and isn't affected by back/forward button.
Otherwise your options are:
Telling the user to not press the back button.
Putting the state in the url, e.g mypage.asp#page_123 and using that to determine the state in your javascript at page load.

Resources