In postman, how to save all open tabs, which are having unsaved changes, with a keyboard shortcut? - postman

How to save all currently open tabs having unsaved changes in them with a single shortcut key or key combination?
In certain interfaces, CTRL+Shift+s does the work and in some others, it can be configured. Is there such an option in postman?

Related

Oracle APEX 20.2 - handling opening app in new TAB

I'm trying to handle opening app in new tab in the same browser.
When I am logged in to one tab and will open a new tab and log in again, then return to the first tab and click wherever the error page appears with information about the ended session.
How can I handle it so that when opening the application in a new tab, there is a message that app is already open and that you cannot log in again and the session does not end in the first tab. Another solution is to prevent the error page from appearing in the first tab, but to open the login page.
This is an an annoying facet to APEX session management that usually boils down to becoming a training issue. There are a few options to explore.
If the users are opening the URL from a standard link, then you could enable re-join session for that home page.
You could suggest users open a new tab from a link within the application.
Both options will result in two tabs using the same session, which can cause issues with shared session state, but the new tab link could be defined to clone the session.
Either way, when one of these tabs times out, then the other tabs using that session will have also timed out, and the only pleasant way forward is to close all but one tab.
You might also consider enabling some form of single-sign on.

Django: How to request data and simultaneously have it editable

I have a simple app that gets user input and when a button is clicked, the input is saved as an entry on the database. I'm thinking of creating another app that not only displays the same information (think of view profile) but also simultaneously lets the user edit the text that is displayed in the text field.
I'm guessing the solution is to have the text-fields be auto-filled by pulling the data from the database, and allow overwriting the data once the submit button is clicked.
Typically read and edit views are separated for good reasons like avoiding accidental edits, allowing different levels of access, things like that. But this capability does exist in Django via forms. If you already have a Form built for submitting the data, you can provide a page with existing data pre-filled by initializing the Form instance with the data - in the docs they call this a bound form. See this example in the docs to get an idea of the mechanics.

Why does Postman change saved API requests

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".

C++ Outlook MailItem replace body and discard on close

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.

Infopath 2013 Buttons

We have developed a form that is being used via SharePoint 2013. We would like the audience to be able to click on a list item to open up the InfoPath form and then when in the InfoPath form, press on the created buttons to load different views of the form and hide/show certain sections....without it being in Edit mode.
The premise being that the end user has an interactive form that is quick and easy to use upon loading.
Is there any way that a user can activate the rules applied to the buttons in Read mode or does Edit mode always have to be activated first?
Many thanks in advance for any hints or tips!
Well technically you can create a Read-Only form by making all the Pages Read-Only in their settings and use data connections to pull the data into the form fields you want.
So I would make a landing page with buttons that would change the view, run a query and set fields values that you want to display for each Read-Only page/view.