broadleaf admin framework - delete operation confirmation required - broadleaf-commerce

Sometimes, on the admin, delete button is clicked by user by mistake. Specially, when working with collections, Instead of Edit button, sometimes user ends up clicking on delete button. Adding back the deleted entity becomes a hassle.
Is there a way to hook up a confirmation dialog before deleting any entity from the website.

Yes, add a JQuery click handler to $('.entity-form-actions .delete-button'). In this clickhandler, show a popup and then return true or false to continue execution of the normal click handler.

Related

How to make popUp not submit form on startup?

I am using JDeveloper 11.1.2.3.0,
I have a createInsert button that has ShowPopUp Behavior operation included. In the popUp I have inserted a form whose attributes will be clean from the createInsert operation. When I click the button the popUp shows up all right but showing an error about the mandatory fields of the form. The fields of the form of course are empty because I just opened it. So I think that the popUp is autoSubmiting the form at the starting point.
Does anyone have an idea how to stop it from doing this?
I have changed the createInsert button PartialSubmit property to false but nothing changed.
Ok found the solution. The popUp was not submitting anything actually but during the CreateInsert operation the iterator opens a new row in every related component within that page (form, table etc). So when my popUp opened up with the new form fields, a new row was being created in the back-stage in my read-only table. I changed the iterator in a new one from another Application Module for each case and everything is fine now.

How to identify a button click in coded UI Customised code

In UIMAP.CS file in both the Recorded method and assertion method, I am not able to identify the button click.
Is there any way I can get hold of the button click event?
I am able to get hold the button in to a UITESTCONTROL variable but the options I was able to see are "exists", "enabled","name" etc...
I tried checking it with assertions too when I dragged the cross hair on to the clicked button , assertions are generated only for checking the existence,correctness of text and name but not the events occured on it..
Please help in this regard..
Please make sure that the Control/Object on which you want to use the Click operation is a button and not any Web Element or control which does not support the Click operation.
Once verified, you can do the following:
Record a New Session and while recording click on that button, stop your recording.
Open the UIMap.cs and navigate to that button control. The intellitrace would show you all the available options for that control.
Thanks
Nikhil

JSF: Create a "dummy" button which does nothing?

In our JSF web application, we have an input field where the user can enter a numeric ID, which is then looked up by the app. To help the user, the lookup is bound to "onchange", thus it will be triggered as soon as the user tabs out of the field or clicks elsewhere.
So, user enters "123", presses tab (or clicks), lookup runs. This works fine; however, for usability reasons, we also want to provide a button that users can click on, for users who will otherwise wonder "where should I click to trigger a lookup?". To do this, we'd like to provide something that looks and feels like a HTML / JSF button, but does nothing (as the click will trigger the "onchange" event anyway).
Is there a way to make a JSF button that does nothing? I tried using h:commandButton without the "action" attribute, but it still fires a request.
p:commandButton type="button" will just provide a push button.
Since you tagged this question also as a usability issue, I would advise against a button in the first place if the onchange already triggers the lookup.
From a user's perspective it is confusing whether or not clicking the button is mandatory. After they have entered the field and skipped to the next, they see the lookup occur without clicking the button. If there is a button they will assume it's there for a reason.
The option that I favour in these cases is a onkeypress handler with a timeout of half a second, after which the value is looked up.

Automatically submit/save InfoPath form to SharePoint

I'm designing an InfoPath form that will be saved to a SharePoint 2010 library. This will occur automatically when the user performs a certain action on the form. If the user closes the form, it should prompt them to save changes and if necessary, save to SharePoint.
Problem is I don't want the users to have control over where the form is saved or what it's called, as I intend to handle that automatically.
Now it's possible to capture the onSave event and perform a custom action. But if I did this, I'd need to set the property to cancel the save event, or the user will be shown the "save file" dialog box anyway. But cancelling the save event causes InfoPath to display a warning to the user - "InfoPath cannot save the form. The OnSaveRequest event handler returned a value indicating that the save failed".
Is there any way to facilitate custom save events while still allowing the user to use the save button? It's also important that the user is promted to save changes if they try to close the form, however disabling the save option removes that prompt.
I worked out what to do. The solution is much simpler than I thought.
Capture the onSave event, perform the custom save action, set the cancel flag to false, and remove the call to PerformSaveOperation(). This eliminates the mentioned error message, and doesn't prevent the user from closing the form.

UILocalNotification - Later

In my application I am using UILocalNotification which works fine. But I need "Later" button in the alert instead of "Cancel". When the user clicks on the "Later" button I want to show the notification after sometime. Is that possible?
Thanks
No man, you are on the wrong way.Due to the limitations of iphoneSDK such thing is not possible.In local notification it will only show the two buttons in alert View.
1)Cancel
2)View
Still you can rename the View button to you wish:
localNotif.alertAction = #"Snooze";
rahter than renaming the Cancel button.

Resources