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
6 replies
Subscribers
7 subscribers
Views
1894 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
Team,I am trying to create a manual dropdown field in an expression by the below
Manikandan Ganapathy
over 10 years ago
Team,I am trying to create a manual dropdown field in an expression by the below syntax:
='<select> <option value="0"' selected="selected">Please select a name</option> <option value="1">One</option> <option value="2">Two</option></select>'
It is showing the dropdown while i test the rule, but it throws error when i use it in a process model. Please let me know where i went wrong here and suggest to correct the same?...
OriginalPostID-92632
OriginalPostID-92632
Discussion posts and replies are publicly visible
0
Sathya Srinivasan
Appian Employee
over 10 years ago
Why are you doing this? Why can't you use the OOTB drop down component or SAIL dropDown field?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Sathya Srinivasan
Appian Employee
over 10 years ago
If you want to dynamically populate the data in a drop down based on 'some' rule, you can do that via expression editor.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Manikandan Ganapathy
over 10 years ago
Satya,
Let me explain the scenario.
1. There is a common process model which is being used by other applications as well.
2. This model has a form which is being made of message fields that shows the html data to the user.
3. So adding OOTB dropdown is not possible as working in the common process model is restricted.
4. We have a requirement where we need to show a dropdown of values in the form of the common process model.
5. So I am trying to send a expression rule which can create a drop-down as a parameter to this common process model from my process model.
Let me know if you need any more clarifications.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Sathya Srinivasan
Appian Employee
over 10 years ago
Thanks for the details.
I am still not convinced that creating a drop down from the message is the right approach. Firstly, it restricts the usage and increases maintainability of the solution. So I suggest you reconsider your architecture to provide a solution OOTB.
Now coming to your issue, the other issue I can think of causing the problem is Appian's ANTISAMY. Appian uses antisamy to restrict users from using certain tags or attributes (check antisamy.xml file in your installation). This is most likely the reason why the components are not rendering in your UI.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Malathi
Certified Lead Developer
over 10 years ago
In case it helps, here is the relevant documentation reference to what Sathya has mentioned.
forum.appian.com/.../Expressions
forum.appian.com/.../Expressions
forum.appian.com/.../Expressions
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Manikandan Ganapathy
over 10 years ago
Thanks sathya.srinivasan & malathik
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel