Prevent Designer from "upgrading" the version of a PRD?

[dgersic]

I have, for various reasons, a system here where the engine has been upgraded to 4.6, but UserApp is, and will remain, 4.02. Designer is 4.6.2.

Every time I open a PRD to edit it, Designer "upgrades" it to v4.5.0. This updates two of the XML blobs in the PRD object. This, if deployed, breaks the PRD, because UserApp 4.02 insists that the version be 3.6.1. I can fix it via LDAP, but that's getting to be annoying.

Anybody know how to get Designer to stop doing this?

[Alex McHugh]

dgersic <dgersic@no-mx.forums.microfocus.com> wrote:
>
I have, for various reasons, a system here where the engine has been
upgraded to 4.6, but UserApp is, and will remain, 4.02. Designer is
4.6.2.
>

Why? 4.6.2 and especially 4.7.1 are starting to show the true potential of
the new improved IDM apps. (After years of features being deprecated). We
can’t be tied to an 8 year old version of a product for ever!

> Every time I open a PRD to edit it, Designer "upgrades" it to v4.5.0.
This updates two of the XML blobs in the PRD object. This, if deployed,
breaks the PRD, because UserApp 4.02 insists that the version be 3.6.1.

I seem to recall there was some discussion about this auto conversion years
back. The other way though. A specific designer version downgraded the PRD
version.

I can fix it via LDAP, but that's getting to be annoying.
>
> Anybody know how to get Designer to stop doing this?


Maybe an older version of designer.

[dgersic]

alexmchugh;2488380 wrote:
dgersic <dgersic@no-mx.forums.microfocus.com> wrote:
>
I have, for various reasons, a system here where the engine has been
upgraded to 4.6, but UserApp is, and will remain, 4.02. Designer is
4.6.2.
>

Why? 4.6.2 and especially 4.7.1 are starting to show the true potential of
the new improved IDM apps. (After years of features being deprecated). We
can’t be tied to an 8 year old version of a product for ever!

Because it's not up to me, it's up to my client. And they've decided, for good or bad, that the UserApp will remain v4.02. Yeah, I know, there's all sorts of reasons to upgrade. They're aware of the reasons. They have reasons of their own. We've discussed it, they know the reasons, and the risks, and have decided. That discussion has ended.

alexmchugh;2488380 wrote:

> Every time I open a PRD to edit it, Designer "upgrades" it to v4.5.0.
This updates two of the XML blobs in the PRD object. This, if deployed,
breaks the PRD, because UserApp 4.02 insists that the version be 3.6.1.

I seem to recall there was some discussion about this auto conversion years
back. The other way though. A specific designer version downgraded the PRD
version.

I can fix it via LDAP, but that's getting to be annoying.
>
> Anybody know how to get Designer to stop doing this?


Maybe an older version of designer.

I may have found a way to get it to stop. Designer won't show why it's doing this, but after a Live/Compare and Update Designer from the root of the UserApp driver, it has stopped trying to upgrade PRDs to v4.5.0.

[cpedersen]

On 03.10.18 21:16, dgersic wrote:
>
> alexmchugh;2488380 Wrote:
>> dgersic <dgersic@no-mx.forums.microfocus.com> wrote:
>>>
>> I have, for various reasons, a system here where the engine has been
>> upgraded to 4.6, but UserApp is, and will remain, 4.02. Designer is
>> 4.6.2.
>>>
>>
>> Why? 4.6.2 and especially 4.7.1 are starting to show the true potential
>> of
>> the new improved IDM apps. (After years of features being deprecated).
>> We
>> can’t be tied to an 8 year old version of a product for ever!
>>
>>
>
> Because it's not up to me, it's up to my client. And they've decided,
> for good or bad, that the UserApp will remain v4.02. Yeah, I know,
> there's all sorts of reasons to upgrade. They're aware of the reasons.
> They have reasons of their own. We've discussed it, they know the
> reasons, and the risks, and have decided. That discussion has ended.
>
>
> alexmchugh;2488380 Wrote:
>>
>>> Every time I open a PRD to edit it, Designer "upgrades" it to
>> v4.5.0.
>> This updates two of the XML blobs in the PRD object. This, if deployed,
>> breaks the PRD, because UserApp 4.02 insists that the version be 3.6.1.
>>
>> I seem to recall there was some discussion about this auto conversion
>> years
>> back. The other way though. A specific designer version downgraded the
>> PRD
>> version.
>>
>> I can fix it via LDAP, but that's getting to be annoying.
>>>
>>> Anybody know how to get Designer to stop doing this?
>>
>>
>> Maybe an older version of designer.
>
> I may have found a way to get it to stop. Designer won't show why it's
> doing this, but after a Live/Compare and Update Designer from the root
> of the UserApp driver, it has stopped trying to upgrade PRDs to v4.5.0.
>
>

As far as I know Designer looks at the Engine version when it determines
what version the PRD should have.

In general you are 100% unsupported, as we officially do not support
this, except for a short transmission period during migration.

But I can feel your pain. My suggestion would be to open an SR / BUG,
and see if you can convince people to change it so that it uses the UA
version instead, to determine the PRD version.

It was never intended or designed to be possible to run a split version
setup (Engine+RBPM) that people do it, is a fully different discussion.


Casper

[dgersic]

cpedersen;2488396 wrote:
On 03.10.18 21:16, dgersic wrote:
>
> alexmchugh;2488380 Wrote:
>> dgersic <dgersic@no-mx.forums.microfocus.com> wrote:
>>>
>> I have, for various reasons, a system here where the engine has been
>> upgraded to 4.6, but UserApp is, and will remain, 4.02. Designer is
>> 4.6.2.
>>>
>>
>> Why? 4.6.2 and especially 4.7.1 are starting to show the true potential
>> of
>> the new improved IDM apps. (After years of features being deprecated).
>> We
>> can’t be tied to an 8 year old version of a product for ever!
>>
>>
>
> Because it's not up to me, it's up to my client. And they've decided,
> for good or bad, that the UserApp will remain v4.02. Yeah, I know,
> there's all sorts of reasons to upgrade. They're aware of the reasons.
> They have reasons of their own. We've discussed it, they know the
> reasons, and the risks, and have decided. That discussion has ended.
>
>
> alexmchugh;2488380 Wrote:
>>
>>> Every time I open a PRD to edit it, Designer "upgrades" it to
>> v4.5.0.
>> This updates two of the XML blobs in the PRD object. This, if deployed,
>> breaks the PRD, because UserApp 4.02 insists that the version be 3.6.1.
>>
>> I seem to recall there was some discussion about this auto conversion
>> years
>> back. The other way though. A specific designer version downgraded the
>> PRD
>> version.
>>
>> I can fix it via LDAP, but that's getting to be annoying.
>>>
>>> Anybody know how to get Designer to stop doing this?
>>
>>
>> Maybe an older version of designer.
>
> I may have found a way to get it to stop. Designer won't show why it's
> doing this, but after a Live/Compare and Update Designer from the root
> of the UserApp driver, it has stopped trying to upgrade PRDs to v4.5.0.
>
>

As far as I know Designer looks at the Engine version when it determines
what version the PRD should have.

Testing shows that not to be the case. I did a compare/import all on the userapp driver. Now Designer isn't trying to upgrade my PRDs anymore. Engine version is correct, still 4.6.

cpedersen;2488396 wrote:

In general you are 100% unsupported, as we officially do not support
this, except for a short transmission period during migration.

Yes, I know. Client knows. That's the choice they've made, accepting the risks of having done so. I can explain why, if you have a couple of hours, but it doesn't matter.

[al_b]

dgersic;2488381 wrote:
Because it's not up to me, it's up to my client. And they've decided, for good or bad, that the UserApp will remain v4.02. Yeah, I know, there's all sorts of reasons to upgrade. They're aware of the reasons. They have reasons of their own. We've discussed it, they know the reasons, and the risks, and have decided. That discussion has ended.

I may have found a way to get it to stop. Designer won't show why it's doing this, but after a Live/Compare and Update Designer from the root of the UserApp driver, it has stopped trying to upgrade PRDs to v4.5.0.

I completely understand this point (and this is related to one of the weaknesses of UserApp architecture, at least for me): workflow links/relations in UA "hardcoded".
The client already invested time and resources in this workflow and finally got it working.
Not every client want to repeat this exercise again.