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
8 replies
Subscribers
7 subscribers
Views
2009 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
Hello, I would like to ask a question regarding the reevaluation of S
thanosm
over 9 years ago
Hello,
I would like to ask a question regarding the reevaluation of SAIL interfaces, one that I have not been clear on so far.
Does ANY user interaction with SAIL components cause the whole interface to be reevaluated?
For example, changing the value of a radioButton or the value of a textField, would that cause the whole SAIL interface to be reevaluated?
And reevaluation, if I have understood correctly, means that all expressions within all SAIL components of an interface will be reevaluated, even to return the same result that is already being displayed.
Also, I have a question regarding the with() function, in relation to my previous question, that stems from the implementation of cascading drop down fields.
We have been using a series of cascading drop down fields where the choices of each drop down field must be updated from the database using the selected value of the previous drop down field. Now, given that each drop down field is within a ...
OriginalPostID-156756
OriginalPostID-156756
Discussion posts and replies are publicly visible
Parents
0
sikhivahans
over 9 years ago
Hi thanosm, to the best of my knowledge here goes the answers to your questions:
Does ANY user interaction with SAIL components cause the whole interface to be reevaluated? - Yes an interaction with a SAIL component causes entire interface (the code present in with() block) to be evaluated.
For example, changing the value of a radioButton or the value of a textField, would that cause the whole SAIL interface to be reevaluated? - Yes it's true. To reiterate, interaction with any component evaluates the interface again.
Is anyone aware if the implementation I have just described is not recommended or if anyone has had issues with this? - As far as my experience is considered, some of the users have been following the similar style and this is evident from the uploaded code snippets which I study as part of answering the forum posts.
I don't think that we can't judge that the approach is recommended or not but so far my expereince is considered I would like to make few statements about the approach you have opted for:
1. It's true that this kind of approach hasn't been particularly mentioned any where but this kind of approach has been in use since 7.3 indirectly in form of cascading dropdown feature. We have made an similar implementation in our internal projects(built on 7.3) and I further remember that this has been mentioned in one of the SAIL recipes. To reiterate I have seen in some of the code snippets uploaded as part of forum posts.
2. We need to remember that this kind of implementation may not be possible all the times. This is highly possible when the components are highly inter dependent and less possible when components are completely independent of each other.
3. The approach you opted for might let you shift some pieces of code from with() (the code being written above the final statement) to a specific component's saveInto area which every other team member might not follow. I would like to suggest to put some comments around this kind of code so that others can follow your intentions and make updates accordingly when a rework is done on the same interface.
4. One last note I would like to make is, this kind of approach is completely acceptable when components are highly dependent (for example, say cascading dropdown) and at the same trying to opt for the approach in case of non dependent components also leads to the issues which I am not elaborating here as I feel that this elaboration would become out of context.
Hope the above explanation helps you to some extent.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
sikhivahans
over 9 years ago
Hi thanosm, to the best of my knowledge here goes the answers to your questions:
Does ANY user interaction with SAIL components cause the whole interface to be reevaluated? - Yes an interaction with a SAIL component causes entire interface (the code present in with() block) to be evaluated.
For example, changing the value of a radioButton or the value of a textField, would that cause the whole SAIL interface to be reevaluated? - Yes it's true. To reiterate, interaction with any component evaluates the interface again.
Is anyone aware if the implementation I have just described is not recommended or if anyone has had issues with this? - As far as my experience is considered, some of the users have been following the similar style and this is evident from the uploaded code snippets which I study as part of answering the forum posts.
I don't think that we can't judge that the approach is recommended or not but so far my expereince is considered I would like to make few statements about the approach you have opted for:
1. It's true that this kind of approach hasn't been particularly mentioned any where but this kind of approach has been in use since 7.3 indirectly in form of cascading dropdown feature. We have made an similar implementation in our internal projects(built on 7.3) and I further remember that this has been mentioned in one of the SAIL recipes. To reiterate I have seen in some of the code snippets uploaded as part of forum posts.
2. We need to remember that this kind of implementation may not be possible all the times. This is highly possible when the components are highly inter dependent and less possible when components are completely independent of each other.
3. The approach you opted for might let you shift some pieces of code from with() (the code being written above the final statement) to a specific component's saveInto area which every other team member might not follow. I would like to suggest to put some comments around this kind of code so that others can follow your intentions and make updates accordingly when a rework is done on the same interface.
4. One last note I would like to make is, this kind of approach is completely acceptable when components are highly dependent (for example, say cascading dropdown) and at the same trying to opt for the approach in case of non dependent components also leads to the issues which I am not elaborating here as I feel that this elaboration would become out of context.
Hope the above explanation helps you to some extent.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data