We have some nastily huge configurations. Can we make a rule that will not allow certain configs to be checked in? Or a rule that only allows certain or only one config to be checked in?
Well, you can't strip the configuration out a file and check the rest in. But Dispatch can catch it before check-in I think, and if the Active Configuration is something you don't want you can stop the check-in.
It would be in a Jump: If %CurrentConfig% is equal to or not equal to something specific then cancel EPDM command. If you have more than one condition you need more than one Jump (within a single Dispatch script).
Hi Brian, thanks! I will try.
Yes I meant blocking if the active configuration was a bad one.
For a good user experience, can I add a custom pop up error explanation?
Pop up dialogue is easy. Dispatch has one with an Okay button, and one with a drop-down menu "combobox". Can show any text you want.
It will require some testing, good luck.
Has anyone been able to use %CurrentConfig% for anything? I haven't. I've tried to set a Dispatch variable of type "current configuration" and nothing get's assigned. I've also tried creating a variable of type "static string" and value %CurrentConfig% and still nothing.
SPR 571124 suggests something is amiss too.
Retrieving data ...