WSO2 esb configuration page (under source view) says
Make the required modifications to the configuration and click
'Update' to apply the changes to the server. Use 'Reset' button to
undo your changes.
When I do a change and click update the configuration gets updated, but when I do a reset, it does not undo the changes. what is the problem here?is it a bug?
It resets only the unsaved changes. When you click update and then immediately click reset nothing will happen since the changes are saved when you update.
But if the reset button doesn't work at all (popup confirmation doesn't appear), then this can be due to a browser compatibility issue, so try with a different browser and see.
Make the required modifications to the configuration and click 'Update' to apply the changes to the server. Use 'Reset' button to undo your changes.
It means that while you are doing the changes in the source view, at the middle of changing, you can click 'Update' to save the current changes and you can click 'Reset' to clear/undo the changes currently you are doing. But if you click 'Update' and then 'Reset', it will not undo the changes which are already saved.
Related
I have an app on retool and I want to try out some different layouts. Is there a way to duplicate an app or have version control that you can revert to?
You can duplicate an app by going to the "Create New App" screen, and then instead of selecting "Blank App" you can choose "Duplicate". That'll allow you to choose an existing app to copy from.
Revision History is possible by hitting the "..." button in the top right, and then selecting "View history".
Not sure if Retool updated their UI, but I wasn't able to do this with the accepted answer.
I needed to hover over the name of the app in the list view (before you actually edit the app) and click the ... button on the right. Then, I selected duplicate from that dropdown.
I'm using Postman to test API and like its GUI and ease of use. But some things it does are completely incomprehensible to me. Example: I save an API request to a collection. Sometime later I try to recall it and it has changed. Why?
Scenario: testing against ElasticSearch API
GET _cat/indices.
Save to collection ElasticSearch.
Send other ES API requests.
Delete an index: DELETE /index0
Recall saved _cat/indices
Instead DELETE /index0 is recalled. Why?
It is possible that you turned off the "Always ask when closing unsaved tabs" option in Settings -> General. When this is off, it does not require you to hit Save, it will automatically save when the tab is closed.
Postman has tabs along the top, where each tab holds the data for a given request. When you edit the contents of a tab, you are editing the saved request as well. If you manually hit "save", the changes to the request are saved.
The way to avoid this would be to make sure that any time you are writing a new request and not intending to make it a change to an existing one, you do it in a new request tab (click the + button on the tab line), which you can then optionally save as a new named request.
To Turn Off Autosave, do the following:
Go to Settings -> General
Turn On Always ask when closing unsaved tabs.
Open a saved request, then change something in the request.
Close the request tab. Postman will ask if you want to save the changes. There will be a checkbox "to always discard unsaved changes". Tick the checkbox.
Click on "Don't Save".
I have an addon in Outlook which adds warning to mailbody and links in the email when email is coming from external or untrusted sources.
Anyway, when I replace something in body, when email is opened in full view (no reading pane, double click full view of mail item), I hook mailItem close even and I discard changes, everything works well. (mailitem.onclose(olDiscard))
When I do this with reading pane on, when I discard the changes, Outlook still either saves the changes or when user is trying to close Outlook it asks user "Do you want to save changes to ....." and if user clicked on multiple emails during this period, it shows popup question for ALL emails user clicked and we replaced its body.
What's the solution here? What can I do to fix this? I want to make changes to link and to body, but discard them when user clicks away on another email. End goal is not having Outlook to ask user "Do you want to save changes ..." popups. Please advise.
I can't also make changes to inspector, because inspector is read-only.
P.S. plugin is written in C++.
The solution is to avoid modifying the message body if you do not want to keep the changes.
If you want to show a warning to the user, add a task pane to the inspector. Or simply stamp the message with a category - it will be shown in the inspector.
The Outlook object model doesn't provide anything for handling hyperlinks clicks. As a possible workaround you may consider implementing the following functionality:
When the item is selected or opened in Outlook you may replace the original URL with your own where you can pass the original URL as an encoded parameter if needed. So, if it is allowed to open the URL you can redirect the request further. Note, you can use the SelectionChange event of the Explorer class which is fired when the user selects a different or additional Microsoft Outlook item programmatically or by interacting with the user interface. This event also occurs when the user (either programmatically or via the user interface) clicks or switches to a different folder that contains items, because Outlook automatically selects the first item in that folder. However, this event does not occur if the folder is a file-system folder or if any folder with a current Web view is displayed.
Also you may consider handling the Open event of Outlook items which is fired when an instance of the parent object is being opened in an Inspector. When this event occurs, the Inspector object is initialized but not yet displayed. The Open event differs from the Read event in that Read occurs whenever the user selects the item in a view that supports in-cell editing as well as when the item is being opened in an inspector.
Another possible solution is to register a custom URL handler. So, basically, your registered application will be launched instead of a web browser where you can decide whether to launch a web browser and follow the URL or not. See Installing and Registering Protocol Handlers for more information.
I have an issue in workflow while triggering fast approve.
Steps:
1)Through Content editor, i edit an item.
2) I click on Fast approve button which pops up a comments window
3) On clicking OK or Cancel button, the UI is somehow refreshed and the content tree is now collapsed to base level "sitecore/content/ First-Node-Under-Content".
I am unsure why and what is causing this behavior. Also, I have created and applied workflow which is using in-built fast approve functionality.
This issue exists only in Firefox and IE .
I have a content editor that, when she logs into the Sitecore content editor and clicks an item, nothing happens. The item doesn't load for editing. If she clicks off of the item to another item she's prompted "do you want to save the changes to the item"?
Logging in with another account resolves the issue. Logging in with her account on another PC resolves the issue.
Has anyone ever seen this before? Sitecore is non-functional on this user's PC.
When you say that the item doesn't load for editing, you need to be more specific? Obviously, if she's clicking off the item and getting prompted to save, then the user is able to edit the item. What is it that she can't do?
Also, it depends on what role you have the user set to use, but depending on how you have your site configured, a user can simply click the item, see the fields and enter content in them. There may not be any "edit" queue. Is this not the case? If not, then there's more details that are needed to properly answer your question.
It sounds like a browser / caching issue. I usually try the following.
1. If IE 9 the I try and open a session in private and try again
2. Clear all browser history
3. If that doesn't work try with another browser.
4. If other browser fixes the issue then try to reset the original browser's settings to the defaults.
Last check if you are using a proxy server and try without. This is a long shot.
What version of Sitecore is being used? Older versions using IE9 require compatibility mode to be enabled (this was resolved in later updates of 6.5)
I find the Content Editor most stable in Firefox and IE9 compatibility mode. Chrome has a few finicky issues but generally works.