Bursting traditionally refers to the distribution of a single report to multiple users, where each user receives a limited portion or "slice" of content based on his/her security permissions or needs. Launch Bursting provides a similar method for ensuring users of a given domain access only the data appropriate for their domain.
Launch bursting leverages domain awareness and standard BOE scheduled instances. Based on a user's domain, only instances with a matching prompt value can be accessed through the dashboard portal. 

  • Create a BOE group for each domain. The groups will represent different domains to which users belong. Include them under a single "parent" group. Set the "parent_group" application attribute to the name of this parent group.
  • Name each of the above groups using the following convention: {DomainName}_{DomainID}, where {DomainName} is the name or description the domain, and {DomainID} is the value you would use in the WebI report to filter data for that domain. Also copy the {DomainName} into the description of the group.
  • For each user, add them to one or more domain BOE groups defined above.
  • For each report a user will access via the portal, create a single prompt based on the field that represents the domain. (To support Launch Bursting, it is assumed a field representing the domain exists in the Universe; otherwise, domain-specific filtering is not possible.)
  • Be sure the universe object used in the prompt filter (i.e. the "domain field") is also included in the report. It does not need to appear in the report visually, but it needs to be included in the query. Launch uses this as a final data-check to ensure data security.
  • Create a scheduled instance of each report for each domain value: Modify the instance title to include {DomainID}. You may also include the domain name for visual identification purposes. Specify the {DomainID} as the prompt value. The scheduled instance may be configured with any recurring interval (e.g. daily, monthly, etc.).Note: For larger implementations consisting of numerous domains, manual configuration of scheduled instances, as described above, is not necessary. An automated process using Activity Launch may be implemented according to your organization's needs.
  • Set the following application attributes in the Launch Administration Console (Log into the Launch Administration Console; from the Application Control Panel, click the View Applications link; click Edit under the desired application; click More Attributes on the Application Settings page.):burst_type: launchparent_group: {parent group described above}hidden_prompt: {name of domain universe object described above}


Enabling Launch Bursting


To enable Launch Bursting for reporting, Administrators will need to specify a folder, or set of folders for the application to look for Burst instances.

This defined folder, or Parent Folder if subfolders exist, is identified by the burst_folder attribute described in section 1.3. Once defined, any reports in this folder(s) will run using Launch Bursting behavior based off domain awareness

Launch Bursting can be run alongside of standard/prompt based reporting allowing for multiple reporting behaviors to exist in a single report template. This can be completed by using both a root folder attribute (for on-demand or ad hoc reporting behavior) as well as a burst_folder attribute for launch bursting behavior.

Note: Adding folder access at multiple levels to the report list may require a review of the access to each report for users who are/aren't allowed to view both folders as these folders may exist in separate locations. 


Viewing Burst Instances in the Report LaunchPortal

Viewing burst instances in the Report Launchportal is accomplished from the Reports tab of the portal. The only difference in viewing a burst instance vs an ad-hoc report to the user, will be the lack of any kind of prompting screen. Assuming that all of the above requirements are met for application attribute as well as domain management and instance name, the user will simply be presented with the results of the instance in the format they have chosen.