EVAL:@reason=Rule 'substitute' has 1 parameters, but instead passed 3 pa

RE: EVAL:@reason=Rule 'substitute' has 1 parameters, but instead passed 3 pa

Eduardo Fuentes — Mon, 06 May 2013 05:38:48 GMT

If that worked but you can't find the rule then it means the person who created it by mistake, realized he was using a name he shouldn't be using and deleted the rule. Please review the steps from the link I posted (it includes steps even if the problematic rule has already been deleted).

Once you finish with those steps, through your authorized support contact, request via support case, the restart of the application server as instructed in those steps.

RE: EVAL:@reason=Rule 'substitute' has 1 parameters, but instead passed 3 pa

Jess — Sun, 05 May 2013 17:47:20 GMT

it works when i used fn!substitute. how can we solve this for cloud instances?i can't find the created rule.

RE: EVAL:@reason=Rule 'substitute' has 1 parameters, but instead passed 3 pa

Eduardo Fuentes — Sun, 05 May 2013 17:32:27 GMT

To test if this was introduced by somebody accidentally creating a rule or a custom function plug-in with the name "substitute", wherever you are testing with the out of the box function "substitute" just add the prefix fn! to the function name with the right parameters and test (e.g. test in the rules interface) that should work confirming the issue is somebody created a rule or a function that is now in conflict with the out of the box one.

fn!substitute(...)

To solve the issue take a look at the instructions I posted here: forum.appian.com/.../6055

RE: EVAL:@reason=Rule 'substitute' has 1 parameters, but instead passed 3 pa

Jess — Sun, 05 May 2013 16:35:02 GMT

how can i check it the fastest way?if that's the case i need to check all the rules in our instance?i'm pretty sure that there's no expression rule the same name with substitute,since our naming convention for rules starts with "get".

RE: EVAL:@reason=Rule 'substitute' has 1 parameters, but instead passed 3 pa

Arjun Devadas — Sun, 05 May 2013 13:13:33 GMT

Hello,
Can you please check if some has created any expression rule with the same name of Appian function substitute in any of the applications on the same environment where you facing the problem.