Determining Hotfix version

RE: Determining Hotfix version

Ankur V — Wed, 20 Dec 2017 18:55:37 GMT

Yes in the past applying recommended hotfix would cause issues with our custom plugins and applications hence before deploying the hotfix we need to document the findings

RE: Determining Hotfix version

Colton Beck — Wed, 20 Dec 2017 18:40:23 GMT

Is there a specific reason you need to know which hotfix you're running? Given that Hotfix G is cumulative, it includes all previous 17.2 hotfixes, so there won't be any gaps in hotfix updates.

RE: Determining Hotfix version

Ankur V — Wed, 20 Dec 2017 18:37:33 GMT

I know that location that's how I got the build 6ddf8cc6f0f0a478aa0526615ec3f4fa02077aec we are on, but how do I know which build is this is this corresponding to Hotfix A,B,C,D the only info on the hotfix link is for Hotfix G and the build number associated with it.

RE: Determining Hotfix version

Colton Beck — Wed, 20 Dec 2017 18:36:14 GMT

And to clarify, Hotfix G is cumulative, meaning it shouldn't matter which 17.2 hotfix you're currently running.

RE: Determining Hotfix version

Colton Beck — Wed, 20 Dec 2017 18:34:34 GMT

Open the build.info file located in <APPIAN_HOME>/ear/suite.ear/conf. The contents of this file should match the build.revision of the hotfix packages available here.

RE: Determining Hotfix version

Ankur V — Wed, 20 Dec 2017 18:29:36 GMT

We are on-prem

RE: Determining Hotfix version

Colton Beck — Wed, 20 Dec 2017 18:28:41 GMT

Are you on-premise or Cloud?

If Cloud, I recommend creating a support case.