Exciting news - Release 313 is here!
The Tulip team has rolled out some fresh updates across multiple features, along with some bug fixes. Check out the release notes and dive into what’s new.
Share your thoughts and questions below
![]()
Exciting news - Release 313 is here!
The Tulip team has rolled out some fresh updates across multiple features, along with some bug fixes. Check out the release notes and dive into what’s new.
Share your thoughts and questions below
![]()
An awesome feature included in this release that many folks have been interested in: Capture App Screenshot ![]()
This resolved the following requests - Thanks @OzanB @Julian @michael.wood for the suggestions here!
Let us know what you think ![]()
Hi Beth- What feature is the pdf document product suggestion seen in r313? Thanks!
Hi Nicolette ![]()
So the released feature is the ability to capture a screenshot of an app during execution. While this is not a pdf, it does allow you to save the screenshot as a variable, save it to a Table Record, or include it in an email or completion.
I believe this would solve most of the use cases mentioned on this thread, but if that is not the case for you, let us know!
You can read more about it here: Capture App Screenshot
For customers on standard releases, a 4-release/week grace period will be given to upgrade each OPCH before its compatibility with the cloud is not guaranteed.
Please let me know from when will my OPCH lts13 compatibility be not guaranteed?
When my instance reaches r317?
Hello @ta-aoki -
That is correct. r317 will be the first version of Tulip where we don’t guarentee support for <lts14 OPCH versions.
Pete
I am not sure if this is the right place to ask, but why do I see LTS14 now separated into two rows in this table?
I see biweekly version from r317 to 331 missing in this table. Which OPCH tag should they use?