Recovering deleted collections.

https://postmanlabs.atlassian.net/browse/PRODASH-947

https://www.getpostman.com/docs/v6/postman/sending_api_requests/history

Postman avoids duplicating GET requests with the same URL in the history.

This behavior is not longer present in our stable apps. We create a new history for every request you send in Postman. We can remove this line from the documentation.

(Screenshots are of a version previous than v6.0)

URL: https://www.getpostman.com/docs/v6/postman/collection_runs/using_environments_in_collection_runs

As described on the title, there is a web API whose value of the parameter is Integer, how can I set it?

https://www.getpostman.com/docs/v6/postman/launching_postman/syncing

"Deleting your Postman account" section needs updating. Please work with @abhijitkane for correct info.

https://www.getpostman.com/docs/v6/postman/launching_postman/settings

Clarify that "Editor Font Size" setting only impacts Test Scripts, Pre-request Scripts and Response Pretty View.

https://www.getpostman.com/docs/v6/postman/launching_postman/creating_the_first_collection

Congratulations! You can see all of your collections under the Collections tab of the sidebar on the left.

It would be good if we introduce a screenshot of the collection sidebar.

https://www.getpostman.com/docs/v6/postman/launching_postman/sending_the_first_request
https://www.getpostman.com/docs/v6/postman/launching_postman/creating_the_first_collection

https://www.getpostman.com/docs/v6/postman/launching_postman/syncing

These entities can sync with our server and be saved to the cloud:

List of supported OS versions: https://github.com/electron/electron/blob/1-8-x/docs/tutorial/supported-platforms.md#supported-platforms

Doc page: https://www.getpostman.com/docs/v6/postman/launching_postman/installation_and_updates

Describe the bug
Documentation page for integrations has old screenshots.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://learning.getpostman.com/docs/postman_pro/integrations/intro_integrations/#___gatsby

Expected behavior
Use new dashboard screenshots

Screenshots

Given that there are constant updates to the app- keeping a check on this particular doc page will help. Especially because it is very often shared with users also.

https://www.getpostman.com/docs/v6/postman/launching_postman/navigating_postman

To start with it'd be great if the documentation includes the below items that are mentioned in the screenshot. ie, the Team button along with the drop down and options.

https://www.getpostman.com/docs/v6/postman/launching_postman/installation_and_updates

The latest version of the native app also has a built-in console, which allows you to view the network request details for API calls.

console should deep link to https://www.getpostman.com/docs/v6/postman/sending_api_requests/debugging_and_logs#network-calls-with-postman-console

https://www.getpostman.com/docs/v6/postman/launching_postman/installation_and_updates

The download should take a few minutes depending on your internet connection. Once you’ve downloaded the app, you can launch Postman.

I want to test my API, that 1 function has many test cases, how can I do this in Postman. Have I write many requests for 1 function?
Ex: I want to test login function, and I write 2 requests, 1 for correct email/password, and 1 for wrong email/password?

https://www.getpostman.com/docs/v6/postman/launching_postman/installation_and_updates

The native apps are not restricted by the Chrome standards for the menu bar. With the native apps, you can create collections, switch to history requests, and more.

you can no longer create collections or switch history via menu bar. Replace these with 'Check for Updates, create Postman Windows, etc'

OP: @loopDelicious postmanlabs/postman-app-support#5271

Customer is reporting a number of 404s throughout the Postman docs, throughout monitoring pages, documentation pages, and probably throughout the rest of the docs

• 404s
• also some variables (like email) are not resolving in the new learning center docs - see screenshot
• also consider running Link Checker collection template to monitor for broken links

https://www.getpostman.com/docs/v6/postman/launching_postman/postman_account

Sync and back up your history, collections, environments, and header presets.

OP: postmanlabs/postman-app-support#5338 by @loopDelicious

Currently there are commonly searched topics that either aren't covered in the Postman docs OR they aren't indexed properly in the search.

Example
When someone searches for jwt in the Postman docs, they see zero results. However, we can add a JSON Web Token (JWT) example under the Bearer Token Auth helper section of the Authorization page, or link to our YouTube video on JWT authorization. Alternatively, just add the text "JWT" in this section, and the section will be indexed in the search. This will point them in the right direction, when they do this search, instead of showing zero results.

We know some of these metrics:

Most popular searches
Search results that return zero results

I gave Arif access to our Algolia team account, so he has access to these search metrics. We can also compare with Google Analytics to see search bounces for when a person lands on a page they weren't expecting.

https://www.getpostman.com/docs/v6/postman/launching_postman/installation_and_updates

The latest versions of the native apps let you send headers like Origin and User-Agent. These are restricted in the Chrome app.

restricted should point to restricted headers section on the interceptor page.

https://www.getpostman.com/docs/v6/postman/sending_api_requests/interceptor_extension#restricted-headers

https://www.getpostman.com/docs/v6/postman/launching_postman/creating_the_first_collection

Save button screenshot points to 'Save As'

https://www.getpostman.com/docs/v6/postman/launching_postman/newbutton

1. In the first paragraph of Create New section, the first two lines just explain what is in the UI. Let's expand this with a one line summary of these blocks and then link to the relevant sections below for each

In BUILDING BLOCKS, create a new request, collection, or environment.
In ADVANCED, create new documentation, a mock server, or a monitor.

2. Blocks are incorrectly mentioned as features.

You can also directly create a new feature when you click the down arrow at the right side of the New button.

3. Highlight or draw attention to the New dropdown in the screenshot below.
   https://s3.amazonaws.com/postman-static-getpostman-com/postman-docs/WS-new-button-menu-blk.png

4. Update environment screenshot at https://s3.amazonaws.com/postman-static-getpostman-com/postman-docs/WS-manage-environments-newButton.png

Article is here:
https://learning.getpostman.com/docs/postman_pro/managing_postman_pro/managing_your_billing/

Dead Links:

Change your plan (Pro Monthly)
Add user slots to your plan (Pro Annual)
Set instructions for next billing cycle
Set the monitoring block count
Manage your invoices
Cancel your plan

Dead links contain: docs/pro/...
/docs/pro/managing_pro/changing_your_plan

Correct URL is: docs/postman_pro/...
/docs/postman_pro/managing_postman_pro/changing_your_plan

https://www.getpostman.com/docs/v6/postman/collections/managing_collections#delete-a-collection

Undo delete option is not longer supported. Please remove this.

The following learning center documents have broken links & incorrect template rendering:

https://learning.getpostman.com/docs/postman/collection_runs/command_line_integration_with_newman/ -> this has a broken link too

https://learning.getpostman.com/docs/postman/collection_runs/building_workflows/

https://learning.getpostman.com/docs/postman/scripts/postman_sandbox/

https://learning.getpostman.com/docs/postman/collection_runs/newman_with_docker/#___gatsby

In the list of variable scopes and the illustration, the local variables are lower in the hierarchy then data variables. The local variables have the highest precedence among all the variable scopes.

The list should be
Global
Collection
Environment
Data
Local

and same in illustration

Also the local variables are set using pm.variables.set. This is not documented anywhere. Maybe we could just mention it as to what local variables are somewhere in this doc.

{:target="_blank"} is seen in some of the files due to how the old docs site worked. These aren't needed anymore and are improperly rendered on the Learning Center.

I have started to remove these as I get around to them but if anyone else has the time, please also remove these while working on docs.

Thanks!

https://www.getpostman.com/docs/v6/postman/collection_runs/starting_a_collection_run

"To learn how to run multiple iterations, see Running multiple iterations" incorrectly points to https://www.getpostman.com/docs/v6/postman/collection_runs/using_environments_in_collection_runs.

It should point to https://www.getpostman.com/docs/v6/postman/collection_runs/running_multiple_iterations

The following URLs for articles on the Learning Center regarding Mock Server usage return 404:

https://learning.getpostman.com/docs/v6/postman/mock_servers/intro_to_mock_servers
https://learning.getpostman.com/docs/v6/postman/mock_servers/mocking_with_examples
https://learning.getpostman.com/docs/v6/postman/mock_servers/mock_with_api
https://learning.getpostman.com/docs/v6/postman/mock_servers/matching_algorithm

There may or may not be others, this is just what I noticed initially.

If the first response is 200 and empty body
All the following example response will gone.

Video

https://youtu.be/6CjFMiZ5Tmo

Possible reason

All the response example is in the same html DOM if the first one do not have response. The response DOM will not be created. Therefore, all the following response will not shown.

User: I'm having real issues drilling down into a pm.sendRequest response header in a pre-request script. Syntax like res.header[x].value barfs in postman (the value is there, though), while the same JSON object in the browser console is fine. Known issue? #testing

Postman: The response you get in the callback is not a plain javascript object. It is a postman-collection response instance. You can find the API reference here https://t.co/rxLc4yFlo8

The documentation for send request https://t.co/BjbaqrVA1i has more details.

You might want to try this out

pm.sendRequest('http://postman-echo.com', function (err, res) {
  console.log(res.headers.toObject());
});

It doesn’t communicate the caveat with the response type. But it points to the link for the right response type.

On https://www.getpostman.com/docs/v6/postman/launching_postman/settings the modal shown looks very old

Following options are missing

• SSL certificate validation
• Automatically persist variable values
• Variable auto-complete

https://www.getpostman.com/docs/v6/postman/launching_postman/settings

You can force re-sync or disable it under Settings.

Electron's home page is pointing to http://electron.atom.io/. The updated one is https://electronjs.org/.

https://www.getpostman.com/docs/v6/postman/launching_postman/installation_and_updates

Postman’s native apps are built on Electron, and overcome a number of restrictions of the Chrome platform.

Currently in Postman documentation around variables we do explain different types of variable scopes but do not provide enough context on "when to use which type of scope". With 4 types of scopes users have a lot of confusion around which variable should they use, how to manage them etc.

https://www.getpostman.com/docs/v6/postman/launching_postman/sending_the_first_request

Reference user issue: postmanlabs/postman-app-support#4514

We need to provide the workaround for the users as suggested in the issue ticket.

We mentioned that Pro and Enterprise users can make their mock servers private. We should also mention that this feature is available to free users as well.

https://www.getpostman.com/docs/v6/postman/mock_servers/intro_to_mock_servers

https://www.getpostman.com/docs/v6/postman/launching_postman/settings

Read more about managing client certificates.

This setting is not related to client certificates

Page: https://www.getpostman.com/docs/v6/postman/launching_postman/installation_and_updates

1. Linux installation is not different for different distributions, creating postman.desktop file is common for all supported distributions for us. so specify that it as an extra step to link the app executable.

2. Desktop entry file needs to specify executable path instead of just the name.

cat  > ~/.local/share/applications/postman.desktop
[Desktop Entry]
Encoding=UTF-8
Name=Postman
Exec=<Your_Install_Dir>/Postman/app/Postman
Icon=<Your_Install_Dir>/Postman/app/resources/app/assets/icon.png
Terminal=false
Type=Application
Categories=Development;

OP: @loopDelicious postmanlabs/postman-app-support#5269

Throughout the Postman docs, kramdown needs to be scooched to markdown.

• Rendering inline code (attached screenshot)
• Rendering target blanks, and markdown hyperlinks
• Relative links are hardcoded v6, and redirects are not yet active, so relative links are 404

https://www.getpostman.com/docs/v6/postman/launching_postman/postman_account

You can turn off sync any time and still use Postman.

Remove this bullet point as Sync cannot be turned off from Postman v6.0+

https://www.getpostman.com/docs/v6/postman/launching_postman/settings

Proxy functionality inside the Settings > Proxy tab need to be documented or referenced here

https://www.getpostman.com/docs/v6/postman/collections/managing_collections#adding-folders

Folders are initially ordered alphabetically by name and folder name.

This info is outdated. New folders are created at the end. Please remove this sentence.

postmanlabs/postman-app-support#4637

We need to add the link to a desktop file to create an icon in launcher just like how this gist provided.

https://gist.github.com/aviskase/e642248c35e400b56e2489430952369f

Refer comment from dev at postmanlabs/postman-app-support#4588 (comment)

https://www.getpostman.com/docs/v6/postman/launching_postman/settings

"Automatically persist variable values"
"Always open requests in new tab"
"Variable autocomplete"

We should not recommend people to use path variables, instead, they should be using environment, collection or global variables. I don't see a use case where new users should be using path variables.

But, in our docs, even the core concepts like sending a request is teaching people how they can use path variables.

We can talk about briefly variables in general there and link to the variables docs. In the variables docs we can talk about path variables and then recommend to use other variables also explaining the reasons.

Here's a link to a issue on our community where a new user started using path variables after checking the docs.
https://community.getpostman.com/t/advantage-of-path-variables-over-environment-or-global-variables/2697/3

Some past issues with path variables

• postmanlabs/postman-app-support#4423
• postmanlabs/postman-app-support#2427