Description
Environment
Potential Workaround
Attachments
- 20 Jan 2023, 03:25 PM
- 19 Jan 2023, 11:40 AM
- 18 Jan 2023, 04:46 PM
- 18 Jan 2023, 09:09 AM
- 12 Jan 2023, 02:32 PM
- 12 Jan 2023, 02:32 PM
- 12 Jan 2023, 02:31 PM
- 12 Jan 2023, 02:31 PM
- 10 Jan 2023, 09:49 AM
- 08 Dec 2022, 11:59 PM
- 08 Dec 2022, 11:50 PM
is cloned by
relates to
Checklist
hideTestRail: Results
Activity
Khalilah Gambrell January 21, 2023 at 10:23 PM
Yauhen Viazau January 20, 2023 at 3:25 PM
Verified on Snapshot-2 environment - works as expected :check_mark:
Please see attached screencast:
Dmytro Melnyshyn January 19, 2023 at 11:40 AM
Hi @Khalilah Gambrell
Yes, but this only works in the default auto-layout mode. Now the snapshot uses a landscape layout and the user can't change it to a portrait.
The auto-layout mode gives the user the ability to choose the layout. Also, the first time the user tries to print the page, the page layout will be a portrait, but the user can change it to landscape and landscape will be automatically selected the next time the user wants to print the Source record (the previous selection is remembered).
In some cases, a portrait landscape is even preferable because fewer sheets of paper are required for printing.
Khalilah Gambrell January 18, 2023 at 4:48 PM
Hey @Dmytro Melnyshyn.
When the user selects Microsoft to PDF, the PDF output rotates the record 90 degrees (see attached
). Is it possible for when the user selects Microsoft to PDF and the PDF is generated that the output retains the same display as what is shown when user selects Print? If the answer is Yes then what is the estimate to make this change? And should I create a separate story for this work, if possible?
Yauhen Viazau January 18, 2023 at 9:13 AM
Verified on Snapshot-1 environment - works as expected per description :check_mark:
Please see attached screencast -
Issue described in a comment above is still reproducible for "Microsoft Print to PDF" print option.
Moving this Story to "In Review" for now.
Something went wrong on our end
If this keeps happening, share this information with your admin, who should contact support.
Hash ZRKH7O
Trace f17a4037c3f041e3a3276ccc07247b44
Thank you @Yauhen Viazau and @Dmytro Melnyshyn