RE: Deprecated Objects: 17.2 to 17.4 upgrade

aijaza — Tue, 20 Mar 2018 20:56:17 GMT

Thank you for the detailed reply, it is really helpful, we have the upgrade server and we are going to test the upgrade on this server, thanks again.

RE: Deprecated Objects: 17.2 to 17.4 upgrade

Robert Shankin — Tue, 20 Mar 2018 20:20:46 GMT

Hi Aijaz -

Appian product releases are backwards compatible except where explicit notice of deprecation is given.
- Thus, it's not a requirement to revise your code in preparation for the upgrade.
Deprecation information can be found in the release notes
- 17.3 deprecations
- 17.4 doesn't site deprecations but does note evolved functions.
Just to add some more detail on Harrison's answer:
- Search within expressions was added in 17.3. See the docs here.
  Since it's not available in 17.2, you won't be able to use it until after you upgrade.
- You may choose to search for evolved functions after you upgrade if you wish.
  - again, it's not mandatory to update functions to the evolved versions right now.
  - note, too: you would be effectively updating you application to use NEW functions.
    - Some evolved functions take different parameters.
    - I recommend you do not rush into changing these functions without planning.
    - This would be no different than other functional changes to your application, a regression test would be wise.
Finally, do you have an upgrade server?
- Not all customers do have an upgrade server, but one of these can be an asset.
  - An upgrade server is very similar to QA in that it matches prod, except the plan for this server is to test all Appian product upgrades on this server first.
    - Upgrade this machine well in advance of the prod upgrade
    - Run any available test scripts of your Appian applications on the upgrade server
    - Invite product owners and application design teams to test their applications on this server
    - Appian releases are backwards compatible, and you should not experience service impacting issues with the upgrade. However behavior changes are possible. It can be beneficial to understand behavior changes prior to upgrading production.
    - In the unlikely event that you do observe an issue with the upgrade, this can be communicated to Appian support, and can likely be resolved prior to you scheduled production upgrade.

Good luck with the upgrade!

RE: Deprecated Objects: 17.2 to 17.4 upgrade

harrisont606 — Tue, 20 Mar 2018 19:40:14 GMT

Are you referring to actually deprecated functions or evolved functions? For example, some functions were evolved and their old versions now end in _17r3. If you want to find those you can search by text in objects now if you go to design, so just search for 17r3 and you can find them all.