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
3760 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
Context of Related Action
joanneh
over 8 years ago
Hello! Please may I know when I was adding an "update" function as an RELATED ACTION on the Record page, what should be filled in the "Context" Box?
I have filled in every input that the process model required but it still did not work...
OriginalPostID-235348
Discussion posts and replies are publicly visible
0
ammireddys
A Score Level 1
over 8 years ago
@joanneh, Please check if there is any process start form for that "update" process model if so, Delete the start form and republish it.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Rajasekhar Pamidipati
A Score Level 2
over 8 years ago
Also, You cannot use 'rule!SC_queryCallLogByID(rf!callLogId).callLogCustomer' format. I got that you want to read only one particular value from that rule but it will not work like that. either you need to return that single value or you need to use some other rule which will call the above rule then return only required value.
same will be applicable for 'rule!SC_queryCallLogById(rf!callLogId).callLog'
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sikhivahans
over 8 years ago
@joanneh Check few more criterion as follows:
1. Are you trying to see the Related Action as a Basic User? If so, make sure that basic user ATLEAST holds the initiator privilege.
2. Did you configure any visibility expression? Is it returning a single boolean value? If not, ensure that a single boolean value is returned.
Afaik, usage of query rule to assign values for the inputs might work and it may not be the reason for non-working of your Related Action. Keeping the working/non-working aside, I would say that it should be taken care as the part of design. Though this may be irrelevant, I would suggest one of the following and also refraining from the usage of query rule those many times as it hampers performance:
1. Pass only rf!callLogId as context to the Related Action from the Record Type.
2. If you have a start form, query the data in the load(), assign to fields, and in the saveInto of Submit Button, push the local variables into PVs if you aren't interacting with any of the fields associated with Parameterised Variables(or you can also save values under a required field or in the script task after the start event). If you are not making use of a start form, query the data from rf!callLogId at a required place (might be prior to the first user input task as per your design).
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
joanneh
over 8 years ago
@ammireddys @rajasekharp Thanks for your advice. I have tried removing the start form and it works! :)
@sikhivahans Yes,sometimes my process models work with start form and query rules, therefore i was searching other ways to keep the start form there. Your detailed recommendation helps a lot. Thank you so much!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sikhivahans
over 8 years ago
@joanneh My pleasure. :)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel