• State Not Answered
  • Replies 7 replies
  • Subscribers 12 subscribers
  • Views 860 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Data and Records

Service Back Record - a!recordActionField component

Sandeep
Certified Senior Developer
 Hi All,
 I have designed service back records and having some related actions added on it. Having this, i am using new component record action(a!recordActionField) on form to perform some actions.
  E.g: Record A
          Record B
   My design :                                          
    1. I have interface designed and called on records summary on 'Record A'.
    2. In Interface one of the section, i am calling actions of 'Record B' with record action component(a!recordActionField).
    3. Now, problem Statement- every time i refresh summary tab/view, call goes to source integration of 'Record B' by record actions added.
    It does seems standard behavior of service back record with record actions but it cause response time issue on given interface since integration execution happening every time.
    Expectation: Record source integration should not invoke until I click on record actions from interface sections.

    Can you please help me with this.
    Thanks in advance.
   
   

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    You cannot avoid this call in the backend as Appian requires some of the data. This becomes even worse when you put the recordActionField into a grid. Then Appian performs that call for each row.

    If you cannot turn that data source into a synced record, then you could go with a two-click approach to show the record actions only on demand. Not great, but avoids the initial loading time.

Reply
  • 0
    Certified Lead Developer

    You cannot avoid this call in the backend as Appian requires some of the data. This becomes even worse when you put the recordActionField into a grid. Then Appian performs that call for each row.

    If you cannot turn that data source into a synced record, then you could go with a two-click approach to show the record actions only on demand. Not great, but avoids the initial loading time.

Children

© 2024 Appian. All rights reserved.