Need help decyphering meaningless error message!

So I've migrated a v7.6 process and gone through all the code converting the 'Evaluate' entries into real v9 code. I've validated it with no problems and now I've got the stage where I want to publish it for the first time.

I get the following error message:

The type arguments for method 'Metastorm.Runtime.Core.Scripts.Activities.WF4.MstmCodeActivity.If<T>(Metastorm.Runtime.Types.Check, T, T)' cannot be inferred from the usage.  Try specifying the type arguments explicitly.

No component mentioned, no indication of what the problem is, what code function is generating it or where it is.

I've got 7 admin forms, 9 business objects, 2 flags, 6 forms, 2 process maps with 25 stages and over 50 actions to look through with no clear idea of what it is I'm looking for. Like looking for a needle in a haystack when you don't know what a needle looks like.

Can anyone suggest what I might be looking for please?

Find more posts tagged with

BPM

Comments

Richard Burt

Thanks to Jerome who responded to my post on the Process Mapping forums. He suggested removing bits of code one at a time until the problem went away.

Using this approach I found the issue in this code:

If(Inbound_EMailData.SupportTeam=="", "appropriate", Inbound_EMailData.SupportTeam

I built this using the expression builder so if it wasn't going to work you would expect it to fail validation when you clicked 'OK' but it didn't. I've removed it and the oh-so-helpful error message has gone away.

I also logged this with Opentext and I am hoping they will tell me the correct syntax to accomplish this.

Jacob_Eastman

It looks like it doesn't like the type that the if() is returning. It might not be returning a string like you expect. I'd try adding .ToString() to it.

Jerome_Pearce

But .....

First you have to find the piece of code. The Designer is extremely unhelpful at this. Even if you can guess the cause from the meaningless error message, the find function often blows up on you when used. When it does work, it does NOT go to event code either.

All in all, after four years now, this really should be addressed. I have lost count of the posts here and on our forums where people have had problems because of this fundamental failure in the Designer. You could solve that by by fixing this functionality.

While there, fix the engine error messages so they actually point to the code causing the fault, and provide a meaningful error, as we have had since version 5 onwards.

Colyn_Pierre

I had the same issue and the ToString() solution fixed it.

E.g.

If(Inbound_EMailData.SupportTeam=="", "appropriate", Inbound_EMailData.SupportTeam

should be:

If(Inbound_EMailData.SupportTeam=="", "appropriate", Inbound_EMailData.SupportTeam.ToString()