JaideepBrar​, thanks very much for the quick answer.

We are on AEM 6.3.3.5.  We also use AEM Forms Server on a completely separate set of servers.  When we upgrade AEM from 6.3 to 6.5, must we also upgrade AEM Forms server?  I'm not asking if it's best practice to upgrade both at the same time, because it surely would be nice to do.  We are trying to ...

Appreciate you suggesting a possible alternative gauravb10066713​.  For now, we only have one affected workflow (maybe two), so writing/maintaining additional and possibly unsupported custom workflow code doesn't quite seem worth the trade-off of manually enabling/disabling the workflow launcher.  W...

As usual, you are right smacdonald2008​.  Thanks very much for answering.

Very logical idea, and I tried something similar before posting, but no dice.  I even tried it again in case I missed something the first try, both with and without the square brackets for runModes value in .content.xml.  Thanks so much gauravb10066713​ for your awesome suggestions and time.

gauravb10066713​, thanks again for commenting.  We do use different runmodes on all our servers.  Unlike regular osgi configs for stuff like com.day.cq.mailer.DefaultMailService.xml, the workflow launcher config is in one folder, and the file is named .content.xml.  For our example workflow, it's:-u...

Hi gauravb10066713​.  The runModes property only limits where this single configuration gets applied for the specified workflow launcher.  We're trying to use multiple configurations that are selectively applied to different servers.  The runModes property might be part of the solution, but it doesn...

We're using AEM 6.3.3.2.  Is it possible to customize configurations in our source code for individual workflow launchers on a per environment basis, similar to OSGI configs?  The goal is that each Maven build will apply the custom settings to each workflow on a per environment basis.  We'd like to ...

Jorg, thanks for your additional perspective.  Very nice to know that the added complexity could even cause us unexpected issues.  Going to follow the KISS principle!

smacdonald2008​, thanks a lot for the quick reply.  It definitely helps!  Based on your answer (and well known expertise), I think we'll avoid including namespaces in our custom property names.  Good to know it's an option, but not a hard rule.