I am using a template for adding/editing an event. What I would like to do is be able to add an event but keep the window open and retain the entered data so the user can change a couple of fields and save that other event. There are 2 save buttons, "SAVE", and "SAVE and ADD NEW". The first button will save the entered event and close the dialog window. The second button will save the entered event but will keep the window open, user changes one or more fields, then save that new event (repeat as necessary).
Any advice or pointing me in the right direction is appreciated.
You can try using the "save" event of the Scheduler to make copy of current event and then call the "addEvent" method of the Scheduler with it. Check the Scheduler API below:
Scheduler: API
Related
I need to show new modal after the submit of the previous one, but I need a trigger_id for it, and there is nothing about it after the submit.
I can use views.update API only instead, and I have a valid response, but the submit button closes the window and nothing happens on the client side after it all.
Slack doesn't show an input in modals without a submit button, so I can't use alternative buttons in the modal too, because a user anyway can click on the submit button and it will be closed.
Is it possible to show or update the modal after an input submit? For example, I need to take a data from the input and show it in the modal after, is it possible?
You could try updating the view using the response_action. That needs to happen within 3 seconds, but doesn't require a trigger_id. Docs for that are here.
My mission is: after the user clicks on cancel order button, I need to check some data and if the data is true, I need to prevent from the button functionality to run and alert the user, where can I insert my code?
Mscrm.Form.salesorder.CancelOrder is a vanilla button and seems close to add or edit, how can I do that?
Either you can do a pre-update plugin, check the business logic and throw InvalidPluginExecutionException if it is satisfied
You can use custom action by customizing the OOB cancel button or by hiding it and introducing a custom cancel button to invoke custom action or script to alert
I have an oracle application express process, written in PL/SQL and it fires off a confirmation email, supposedly when you click on the related button, (It is an after submit attached to the button) however, it is firing every time you refresh the page. Is there a different way of doing this so it only fires when you click the save changes button?
Take note of the execution point attribute. It will won't apply to page refreshes if it's either 'Processing' or 'After Submit'.
You can also associate these after-submit processes with specific buttons, using the 'when button pressed' property.
You may also wish to consider the 'Enable duplicate page submissions' page property.
If you're still having issues, you can build a demo at apex.oracle.com, and updated your question.
I have a modal window that shows a panel which contains a form that has some textfields and a submit button
on submit an insert into the database occurs and then I have some ajax behaviour that i want to activate on the modal windows containing page on click of the button.
So flow is at present:
click link
modal window appears
user fills out form
user submits form
form data persisted to db
modal window closes
I need it to do this in addition:
activate some ajax behaviour on the page that contains the panel
any help on how best to do this in the wicket way is appreciated.
I resolved this by passing an instance of the page containing the panel to the panel (i.e. - in the constructor), then calling a method on the page from the panel to perform the Ajax update.
I would be interested to see what others have done or to hear if there are issues with the approach I have taken.
Set up a WindowClose callback.
In the WicketStuff project called ModelX (Disclaimer: I'm the developer of that) I have created an IWindowClosedListener interface which has a method:
void windowClosed(Panel panel, AjaxRequestTarget target)
So then any Page or Panel that can open a modal that needs to do something when that modal is closed simply implements that interface and its windowClosed method gets called at the right time.
My extension needs to know that the tab is displaying something from the history rather than the latest loaded document.
onload doesn't seem to be the right event. It doesn't always fire.
Use the pageshow event, it fires after the onload event and has a parameter called persisted that will be set to true when the page is loaded from the cache.