nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

WFM 1.0.0.1 changes

Pawan

I have installed the WFM 1.0.0.1 client on my system. Whenever, i try to download an existing workflow created by WFM 1.0, it always asks me to convert to the new model and after that on validation its shows me a list of errors even though the workflow is running alright.
Does anybody know the reason for it? It asks me to change the name of the links between tasks.

Find more posts tagged with

Comments

Adam Stoller

I have installed the WFM 1.0.0.1 client on my system. Whenever, i try to download an existing workflow created by WFM 1.0, it always asks me to convert to the new model and after that on validation its shows me a list of errors even though the workflow is running alright.
Does anybody know the reason for it? It asks me to change the name of the links between tasks.

Are you running 671SP1?
I believe this was fixed in the 672 distribution - i.e. the WFM's for the OOTB workflows were fixed.

I ran into this in 671SP1 - and didn't bother trying to go any further with the OOTB WFM's as I needed to create a custom one anyway.

msrinivas

I have installed the WFM 1.0.0.1 client on my system. Whenever, i try to download an existing workflow created by WFM 1.0, it always asks me to convert to the new model and after that on validation its shows me a list of errors even though the workflow is running alright.
Does anybody know the reason for it? It asks me to change the name of the links between tasks.

You can choose not to convert and you should be ok. You will not be able to use some of the new stuff in the new version.

HTH

Pawan

Are you running 671SP1?
I believe this was fixed in the 672 distribution - i.e. the WFM's for the OOTB workflows were fixed....

Yes Adam, I am on 671SP1 Patch2. Have you faced any compatibility issues with the existing WFM workflows with TS672?

Pawan

Can you please direct me to some documentation where can I get the list of limitation and or advantages of converting the existing WFM workflows to the new format?
If I select not to covert, then will these still be working fine with newer versions of TS and WFM. I just want to make sure, if they need to be converted, better do it now then later.

You can choose not to convert and you should be ok. You will not be able to use some of the new stuff in the new version.

HTH

Adam Stoller

Yes Adam, I am on 671SP1 Patch2. Have you faced any compatibility issues with the existing WFM workflows with TS672?

I haven't dealt with WFM in 672 yet - and, chances are when I do - it will be new WFM's not pre-existing ones -- at least in the near term.