Skip to main content
Nintex Community Menu Bar
Question

Explicitly rendering a queue results in queue header additional queue header section displayed


Forum|alt.badge.img+13

I thought I had logged this before but was unable to find it - possibly it was the same issue for a different component. Apologize if this is a duplicate.

When explicitly calling “render” on a queue, an additional header section is displayed instead of fully “re-displaying” the entire queue. For example, if you call render 5 times on a queue, you will see 6 header sections.

Note - This stems from https://community.skuid.com/t/queue-component-title-search-labels-template-string-not-cha….

Steps to reproduce:

  1. Create page using XML below
  2. Preview page
  3. Click “Force Queue Render” button

Expected Result
Queue displays completely re-rendered with 1 header section

Actual Result
Queue displays with a 2nd header section

Sample Page XML

<skuidpage unsavedchangeswarning="yes" personalizationmode="server" showsidebar="true" useviewportmeta="true" showheader="true">    <models>
        <model id="Opportunity" limit="20" query="true" createrowifnonefound="false" datasource="salesforce" type="" sobject="Opportunity">
            <fields>
                <field id="Name"/>
            </fields>
            <conditions/>
            <actions/>
        </model>
    </models>
    <components>
        <buttonset model="Opportunity" uniqueid="sk-25Keii-196">
            <buttons>
                <button type="multi" label="Force Queue Render">
                    <actions>
                        <action type="custom" snippet="renderQueue"/>
                    </actions>
                </button>
            </buttons>
        </buttonset>
        <queue model="Opportunity" tagrendertype="template" searchbox="true" tokenizesearch="true" showsearchbydefault="true" uniqueid="oppQueue" searchmethod="server" searchplaceholdertext="Search Opportunities" emptysearchbehavior="query" title="Opportunity Queue">
            <rendertemplate>{{Name}}</rendertemplate>
            <interactions>
                <interaction type="tap">
                    <action type="abandonRows" querystring="id={{Id}}" model="Opportunity" affectedrows="context"/>
                    <action type="custom" snippet="updateOpportunityTracker"/>
                </interaction>
            </interactions>
            <searchfields/>
        </queue>
    </components>
    <resources>
        <labels/>
        <javascript>
            <jsitem location="inlinesnippet" name="renderQueue" cachelocation="false">var params = arguments[0],
$ = skuid&#46;$;
skuid&#46;$C('oppQueue')&#46;render();</jsitem>
        </javascript>
        <css/>
    </resources>
    <styles>
        <styleitem type="background" bgtype="none"/>
    </styles>
</skuidpage>
Translate
Did this topic help you find an answer to your question?

6 replies

Forum|alt.badge.img+3
  • Nintex Employee
  • 22 replies
  • July 10, 2024

I’m not getting that result.  When I hit ‘Force Queue Render’ my opportunities disappear, but no extra queue header appears.  What version are you using?

Translate

Forum|alt.badge.img+13

Thanks for looking in to this Gregory.  I’m running 9.5.4 and just tested again and am able to reproduce in Chrome & IE on Windows 10.  What version are you running?  I don’t think browser or OS should matter in this case but what browser & OS are you using?

Translate

Forum|alt.badge.img+3
  • Nintex Employee
  • 22 replies
  • July 10, 2024

9.5, Let me update and look again

Translate

Forum|alt.badge.img+3
  • Nintex Employee
  • 22 replies
  • July 10, 2024

I see it.

Translate

Forum|alt.badge.img+3
  • Nintex Employee
  • 22 replies
  • July 10, 2024

I will fill out a bug report, Thanks Barry.

Translate

Forum|alt.badge.img+13

Thanks Greg.  Interesting that it didn’t happen in 9.5.  In my OP, I mentioned that I thought I had seen this problem before but that i had logged it and it had been fixed (I couldn’t find the community thread, possibly it was closed).  In any case, your findings indicate that this is likely a regression introduced in a version after 9.5.

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings