We have been discussing how to handle different IdM engine versions from
inside Designer.

Is it common for you to have different versions of the IdM engine within the
same project or within the same customer deployment? Do you stay on older
versions of admin and design tools like iManager and Designer for working
with older projects? How do you expect these tools to behave when they
encounter an older version?

Here are some ideas we are throwing around on how to handle older engine
versions in Designer...

option 1- Hide UI: Would you like to see the UI hide features based on the
detection or preference of an older engine version?

Option 2- Grey out UI: Would you like to see the UI grey out or identify
somehow the new features based on the detection or preference of an older
engine version?

Option 3- Show all features for most current engine version: Would you like
the UI to always support just the most current version of the engine and
display all available features?



Preventative action:
Should UI block you or prevent you from configuring policy against an older
version of the engine where the feature/policy wouldn't be supported?

Should we prevent you from deploying newer versions in a project to older
versions in the Identity vault?

Any other ideas/suggestions would be great.


Thanks

Bill.