'Site' Data Query & Restrictions

[Hannah Stella]

We have a need to select multiple sites in progressive captures (specifically for Change tickets). Upon testing we've found some limitations:

Option 1: use the 'get site' node in the progressive capture. This only allows us to select ONE site and because we have the 'use customer site' setting turned on the site in the details will change to the site tied to the customer of the request. This setting, for all other needs, must stay ON. 

Option 2: use a custom form (currently using) in the progressive capture doing a data query checkbox where all sites launch based on the 'sites' table in Hornbill. Only one can be inserted into the details and only one will be listed on the email template - however all affected sites are still visible in the Questions section of the ticket.
Option 3: use the custom form (currently using) in the progressive capture creating custom checkboxes. The downside to this not doing a data query is that we have another progressive capture to manage - and at the rate we're growing and opening new sites this isn't realistic. Only one site will be inserted in the details of the ticket and in the email template (which will default to the USERS site with the above setting). However, all affected sites are still visible in the Questions section of the ticket. 

Is there a way we can have the details include more than one site? 

[Steven Boardman]

@Hannah Stella with option 3 have you considered:

* Creating a simple list of your sites

* Then in your progressive captures, you can reference the simple list, and make it a checkbox picker - for the multiple selection of sites

* Then if you sites are added, you only need to update the one simple list, not each and every progressive capture seperately?

* In order to have the multiple sites available for your email templates, you could map the progressive capture question to a custom request field, and then use this custom field in your email templates