Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
5 replies
Subscribers
7 subscribers
Views
2911 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
EVAL:@reason=Rule 'substitute' has 1 parameters, but instead passed 3 pa
Jess
over 12 years ago
EVAL:@reason=Rule 'substitute' has 1 parameters, but instead passed 3 parameters. I don't know what happened with the substitute function. Based on the syntax: substitute( text, find, replace_with, [instance_num] ), it should require 3 parameters, but why am i getting this error?Please clarify. Thanks....
OriginalPostID-66150
OriginalPostID-66150
Discussion posts and replies are publicly visible
0
Arjun Devadas
over 12 years ago
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.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jess
over 12 years ago
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".
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 12 years ago
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
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jess
over 12 years ago
it works when i used fn!substitute. how can we solve this for cloud instances?i can't find the created rule.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 12 years ago
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.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel