BITeamwork is collaboration management plug-in for Oracle Business Intelligence (OBIEE) 11g that provides Collaborative and Social Business Intelligence (BI) functionality. Most of its functions that you will make use of are transparent as they provide an intuitive augmentation of the main BI System. It is a complete comment management system allowing for customizations and integration capabilities with well-adopted enterprise Social networks such as Salesforce Chatter. It is the packaged solution for leaving comments on dashboards, cell annotations, and inline cell comments on reports with context-based information which can be referenced by other users in OBIEE when using data from any type of data source including Oracle Essbase.

As a user, to get started, the easiest way to learn is watch our BITeamwork videos. Second to that, read the documentation below to gain specific knowledge of how to manage your user settings, send cross vendor comments to Salesforce.com Chatter or Yammer, create dashboard comments, and more. You'll find that BITeamwork is quite intuitive and powerful. And, if you think that it is not, then we want to hear from you on our forums so that we can make it better.

Also, check our browser certification guide, BITeamwork Device and Browser Support , to make sure you're using a compatible browser version.

The main user interface to using BITeamwork is based on the Global Header of the Business Intelligence dashboard portal. This is seen in the image below as the area of the BI Application where the navigation links reside. This is called the BITeamwork Toolbar.


Figure Header_1

Figure Header_2

Per the image here is a brief description of each BITeamwork Toolbar navigation element based on the indicating letter reference.

  1. Comment Count
    • A link that provides a real-time count of "dashboard" comments on the current dashboard. This count will always be the total number of comments on the current dashboard. Comments types included in this count are dashboard and view comments, not cell comments.
    • Tip: Hover over the link to see a count of all potentially visible commments on the dashboard
  2. View Augmenter
    • A button icon that turns on the BITeamwork dashboard augmentation feature that highlights all View Objects on the dashboard enabling the View Commenting functionality as well as the Cell Comment functionality.
      1. Click this to turn on the grid of objects in the dashboard
      2. Hover over a cell in the augmentation grid to view the action bar to create a view comment or dashboard comment
      3. When the augmentation grid is active, click in any cell of a table or pivot table to create a Cell Comment
  3. New Comment
    • A button that opens the BITeamwork pop-up window in order to create a new Dashboard Comment
    • Also use this option to quickly look at your comment history or to see your BITeamwork user settings tabs

The BITeamwork Toolbar is the main access point for working with commentary. The ability to see this option is controlled by your BI Administrator. Meaning if you don't have privileges for the BITeamwork Toolbar then it is not visible to you when accessing dashboards.

NOTE: If there is no view content on a dashboard BITeamwork does not engage and the BITeamwork Toolbar will not be visible.

Each BITeamwork user, if given the correct privileges by your organization's BITeamwork Administrator, will have the ability to manage one or more settings or configurations associated with their account.

The Settings tab can be accessed from clicking the View Dashboard Comments link on the BITeamwork Toolbar. Users may have only few or all of the options below depending on privileges.


Figure Settings_1
  1. Access Links to Comments
    • Allows the ability for comments to have a URL/Link which can be passed along for viewing your comments.
      • An example of this would be that a user could send a link in an email that provided a reference to a comment where the comment and any subsequent replies to that comment may be read/consumed.
  2. Show Prompt Context Cell Comments Only
    • Regarding Comment Context Sensitivity for any user viewing a cell comment or cell annotation on a dashboard or report containing commentary, this option dictates if the comment should only be shown when having context to the current users point-of-view currently active on the dashboard.
    • Example: If a dashboard page contains a table with a cell comment which was created when the prompt value was YEAR=2014 and MONTH=January, then if this box is unchecked then any combination of the prompt selections on that dashboard page will render the cell comment as visible. If this checkbox is checked then only when the user views the dashboard with the applied prompt filter of YEAR=2014 and MONTH=January will the cell comment be visible.
      Said another way...if this checkbox is checked then a user viewing the dashboard page with an applied prompt filter of YEAR=2014 and MONTH=June, will not see an active cell comment for the coment authored at the context of YEAR=2014 and MONTH=January.
  3. Show Prompt Context Comments Only
    • Same as above but applies to Dashboard Comments and View Comments.
  4. Show Only Most Recent Cell Comment
    • When checked this provides an override to the cell annotations that it should always only show the latest comment for that particular table cell in question.
    • Because a cell can have multiple cell annotations within it for the same or different context when multiple comments are viewed by hovering or double-right-clicking the cell then by default all available comments will render one above the other in a list. If this option is checked then only one of the n
    • number of comments will be visible. There is also an option in each cell comment display window that also controls this feature on a cell comment by cell comment basis. Otherwise, this checkbox acts as an override.
  5. Show Bookmark Rename Prompt
    • This feature has been disabled in BITeamwork 3.0 for al
  6. Send all of my comments to Yammer
    • Turns on the automation of sending any Dashboard, Cell, of View comments directly to Yammer without being prompted. This allows for a seamless integration with the Social Vendor when configured by the Administrator.
  7. Send all of my comments to Chatter
    • Turns on the automation of sending any Dashboard, Cell, of View comments directly to Salesforce Chatter without being prompted. This allows for a seamless integration with the Social Vendor when configured by the Administrator.
  8. Hide All Comments On Dash
    • Checking this option provides the means to hide all comments otherwise visible on the dashboard. The original intent of this option is to hide cell comments visibility from taking screenshots of a dashboard, etc.
  9. Enable View Hover Options
    • When checked, if a user has access to the Create Embedded BI Objects privilege then this will show the menu icon visible when hovering the mouse over any dashboard view.
    • BITeamwork 3.0 introduced this option

Dashboard comments are created to annotate or otherwise communicate activity or action in respect to the dashboard. There are many use cases for leaving dashboard comments for other users within the organization to view. BITeamwork also has the ability to pass comments on to other Social Vendors such as Chatter and Yammer. Dashboard comments are dashboard page specific and are not transferred to another dashboard. Dashboard comments have the ability to reference comment context specific to the dashboard such as that denoted by changing prompt values, etc.

Creating a Dashboard Comment increments the Dashboard Comment count in the BITeamwork Toolbar found in the OBIEE Global Header.

How to Create a Dashboard Comment

  1. Click on the "Add Dashboard Comment" icon button from the BITeamwork icons on the BITeamwork Toolbar.
    • The BITeamwork pop-up modal appears with the Comment tab selected.
  2. Select a Category from the Category drop-down menu (optional and privilege based)
  3. Enter a comment in the Comment textbox area
    • Comments may have minimum and maximum character length check performed when submitting your coment. This is dictated by your BITeamwork Administrator who controls this setting. The default setting for the minimum is 6 characters and the maximum 2000 characters.
    • The Advanced Editor for entering comments may or may not be visible to you depending on your administrators configuration of the BITeamwork Application
  4. Click the Submit Comment button to save the comment.

You must have appropriate privileges to create dashboard comments.


Figure DashComment_1

Assign Comments to User(s) or Application Role(s)

Assigning Comments to a user or Application Role directly when submitting a new comment (not a Reply) will initiate a direct Email and Oracle BI Agent Alert to the recipient(s) defined in the list. This is a call to action for the recipient(s) of the comment. If you assign a comment, the comment is still added to the system. It will still abide by all comment object properties such as being global to the context in which it was created (i.e.: Dashboard, View, Cell via any prompt selections).
To assign a Comment Notification to a user or application role (group):

  1. Start by typing the first few characters of a person/group name in the Notify field when creating a new comment
    • Enter an @ symbol first and then the first characters of a person's name to find another user from the BI System. This would be the same username that one would log into the BI portal using.

      Figure DashCommentNotify_1
    • Or, to notify one or more groups, Type the Application Role name directly (no '@' symbol) to find the Application Role in the list

      Figure DashCommentNotify_2

You must have appropriate privileges to assign notification of comments. Only the Enterprise licensed edition of BITeamwork allows assigning comments.

See also Receiving Assigned Comments

A View (Dashboard View) comment is very similar to a Dashboard Comment in that by creating either a Dashboard Comment or View Comment the Dashboard Counter in the Global Header of the application will increment. The main difference is that a View Comment is specific to an individual object within the dashboard. Objects are also referred to as Views based on the way they are created during the report and dashboard development process. The objects available for a View Comment are:

  • Charts & Graphs
  • Tables & Pivot Tables
  • Narration View
  • ...basically everything except prompts.

How to Create a Dashboard View Comment

  1. Click on the new Dashboard Comment icon from the BITeamwork icons in the Global Header.
    • The BITeamwork pop-up appears with the Comment tab selected.
  2. Select a Category from the Category drop-down menu
  3. Enter a comment in the Comment textbox area
    • Comments must be a minimum of 5 characters in length.
  4. Assign a Comment to a user or application role (group) by typing the first few characters of a person/group name.
    • Enter a & symbol first and then the first characters of a person's name to find another user from the list
    • Type the Group / Application Role name directly to find it in the list
  5. Click the Submit Comment button to save the comment.

You must have appropriate privileges to create dashboard view comments.

See also Assigning Comments to Users and Application Roles and Dashboard Comment Security

Comments that annotate a table or pivot table cell to indicate a comment or call to action can be achieved by clicking the augmentation icon from the BITeamwork icons on the Global Header.

How to Create a Cell Comment

  1. Click on the Dashboard Augmentation icon from the BITeamwork icons in the Global Header.
    • The dashboard will appear with a grid-like pattern that delineates each respective view object available for commenting on the dashboard..

    Figure cellcomment_1
  2. Hover over the view containing the table of pivot table for which you wish to leave a cell comment.
  3. Click in the desired cell of the table or pivot table to select the cell for comment
    • If the cell currently has any navigation link associated with the value currently inside of the cell, you will need to click carefully in any white space within the cell to effectively select that cell.
    • The BITeamwork pop-up will appear once the cell has been accurately selected.
  4. Select a Category from the Category drop-down menu
  5. Enter a comment in the Comment textbox area
    • Comments have a minimum length as determined by your BITeamwork Administrator.

    Figure cellcomment_2
  6. Assign a Comment to a user or application role (group) by typing the first few characters of a person/group name.
    • Enter a & symbol first and then the first characters of a person's name to find another user from the list
    • Type the Group / Application Role name directly to find it in the list
  7. Click the Submit Comment button to save the comment.

    Figure cellcomment_3

You must have appropriate privileges to create dashboard comments.

See also Assigning Comments to Users and Application Roles and Dashboard Comment Security

In-line cell comments are those that are built directly within the the row or record for which the table or pivot table is constituted. These comments are only available in a table or pivot table view. These comments are based on the same comment "object" as the dashboard, view, and cell annotation comments. Which means the comments have the same key attributes and properties for security, context sensitivity, etc.
Currently this feature is compatible in OBIEE versions 11.1.1.7.0 and above. ( View API Attributes )

How to Create a In-Line Cell Comment

Follow the steps below in order to successfully implement this functionality for any given report:

  1. Create a new analysis request or open an existing one
  2. Click on the Criteria tab
  3. Add a dummy column to the open analysis ad-hoc report
  4. Edit the formula of the column from the above step by selected “Edit Formula”
  5. Check the “Custom Headings” and “Contains HTML Markup” checkboxes
  6. Enter the in the Folder Heading text field to “Commentary”
  7. Enter the in the Column Heading text field, “Comments”
  8. Enter or copy the following text in the Column Formula area:
    '<div id="twICDiv_" class="twICDiv" twTextBoxCSS="width:250px;" twRId="' '"></div>'

    NOTE: It is very important to initially leave the blank row intact. This will be filled in with your unique combination of data or columns which will make each row distinguishingly unique in order to reference the comment. This will be explained further at the bottom of this example.

  9. In the blank row enter a concatenation symbol (||), the double pipe, so that the criteria column(s) from you subject area selections can be added to the string text you entered in the step above so that it forms a single string statement.
  10. Add a column from the subject area which specifies the uniqueness of each row and add more double pipes (||) as necessary to complete the concatenation.

    NOTE: The syntax for the concatenation filling in the blank row from above is: || “Cust Regions”.”C52 Country Name” || “Products”.”P1 Product” ||

    Here there are two columns used to distinguish each unique row in the table for which a comment will be associated.

    Preceding the initial double pipe (||) is: twRId=”’ (after the twRId= there is a double-quote and then a single-quote)

    At the end of the last double pipe (||) there is: ‘“></div>’ (a single-quote and then a double-quote followed by ></div> and a single-quote)

  11. Click the OK button to close the Edit Column Formula dialog window.
    • There should be no errors in the syntax formula as the syntax is completely compliant with the Oracle BI parsing syntax for an custom column formula.
  12. Open the Column Properties of this column by clicking on the “Column Properties” option of the select column we are using in this example.
  13. Select the Data Format tab
  14. Check the Override Default Data Format checkbox
  15. Select the HTML option from the Treat Text as dropdown
  16. Click the OK button to save.
  17. Save the ad-hoc analysis request by click the save icon button.
  18. Add the report to a dashboard page and then view the report in the dashboard
    • You will now see the report in the dashboard with the comment column containing a text area for entering comments as well as some options for saving the comment.

    NOTE: Clicking the “Results” tab of the analysis editor will not see the comment text area for this new comment column. The column text area will only show when the report is rendered on the dashboard as the testing of entering comments in the Results tab is not optimal for the commentary solution.

  19. Add a comment in the respective row where a comment is needed and then click on the “Save Comment” link button.
    • A notification will appear stating that the comment was Saved Successfully and disappear within a few seconds.
  20. Update the comment by modifying it so that you change the comment text and then click the “Update Comment” link button.

    NOTE: Version 3.0 provides this inline comment functionality in a read/write single comment per filter context capability. All comments are tied into our common commenting framework but as of 2014/10/20 the inline comment functionality defined as you’ve read above until we receive further customer requests for additional features or enhancements

  21. View your results.

See also:

API for Customizations

BITeamwork 3.0 now has controls in place to allow customers to customize several features of the platform. Part of which to do with the inline commenting is the ability to modify the style, size, and color of the text area in the cell for which inline commenting is needed. Following the API instructions with examples below will allow you to customize the areas outline below using the API. We are looking for additional customer enhancement requests for this topic at the moment to expand this capability. View API Attributes


  • Text Area Input

    • The attributes of the text field can be fairly completely customized to the look and feel that you need from a Cascading Stylesheet (CSS) perspective. In order to do this, in the DIV object used in the Custom Formula you will need to add an attribute, twTextCSS. This attribute will hold CSS attributes for an HTML5 textarea object.

    • By default, the comment text area is defined with only the following attributes:

      • border: 1px #aaa solid; resize: none; width:400px;

    • Example:

'<div id="twICDiv_" class="twICDiv" twTextBoxCSS="width:230px;height:20px;background-color:#ccc;" twRId="' || "Time"."Per Name Year" || "Products"."Product" || '"></div>'


  • Enabling Standard Comment Object Features

    • By default in BITeamwork 3.0 the inline commenting option is set to provide a streamlined simple system of commenting although it is well grounded as a comment object in the BITeamwork framework. As of this release when a comment is created is stays in place in the table. The “Save Comment” option immediately changes to “Update Comment”. The comment can then be appended to or erased entirely as it is configured to be a transient comment placeholder.

    • In order to provide standard comment functionality such as that seen for dashboard comments or the cell annotation functionality, the following attribute should be added to the DIV tag in in the inline column custom formula,

      • twMode=”[basic|full]”

        • basic - is the default mode described above

        • full - provide options as seen on other aspects of the BITeamwork integration functionality feature set under the Options… links.

          • this is not available in BITeamwork 3.0 but will be accessible in a later version

      • Intentionally Left Blank

    • API Attributes:

      • twAPI_ph_text

        • Place Holder text value showing in the inline comment text box when no comment yet exists.

        • Possible values:

          • Any text characters except !, &, or %

        • Not entered or No Value

          • Defaults to “Enter Comment…”

          • You can use “...” as the value so that no characters are shown

      • twAPI_auto_exp

        • Determines if the textboxes will auto expand to the size of the commentary entered for the respective inline comment field. Auto or on provide auto expanding to match text entered.

        • Possible values:

          • [auto|on|off]

        • Not entered or No Value

          • Default: auto

      • twTextBoxCSS

        • Cascading Style Sheet and styling of the text box

        • Possible values:

          • Any CSS, however avoid !,&, or % characters as these characters will break the rendering of the inline comments

        • Not entered or No Value

          • Defaults to “Enter Comment…”

      • twAllowEdit

        • If editing is allowed for inline comments fields in the report

        • Possible values:

          • [true|false]

        • Not entered or No Value

          • Defaults to editing allows

      • twAPI_ilc_actions_visible

        • Determines if the menu (icon with three lines) is showing per each ILC.

        • Possible values:

          • [true|false]

          • Default: true

      • twAPI_ilc_actions_position

        • Determines the positioning of the menu (icon with three lines) is showing per each ILC.

        • Possible values:

          • [right|none]

          • Default: none

      • twAPI_save_text

        • Sets the "Save" link button text displayed to the user for each ILC of the column.

        • Possible values:

          • Characters limited to 10.

          • Default: "Save"

      • twAPI_update_text

        • Sets the link text displayed for editing an ILC

        • Possible values:

          • Any Characters limited to 20 max characters

          • Default: Update

      • twIgnoreCmtLen

        • Allows the ILC column to accept any character range of characters greater than 0. This is typically used for capturing numeric values for custom ILC field use cases. As of version 3.8.6, it allows any empty or no length input. Typically one would use this fro numeric values and can further support validation using the API attribute, twAPI_reg_ex_check.

        • Possible values:

          • [true|false]

          • Default: false

      • twAPI_reg_ex_check

        • Allows the inline cell comment to have the ability to pass a myriad of specifications before the input value can be considered successful.
          The value for this attribute is a Regular Expression, which can be tested/asserted against the input comment (string/value) entered into the inline comment field.
          This is perfect for validating input where a specific format or structure is required. For example, if your input requires, only numeric values, only characters, characters with a specific lenght, phone numbers, or any characters meeting a specific format.

        • Possible values:

          • Any testable Regular Expression which results is a pass (true) or fail (false) recognition of the ILC input.

          • Default: (There is no default value. If used in the ILC custom formula it must be a valid Reg Ex, otherwise the result is false)
            One may use the attribute with an empty value, for example: twAPI_reg_ex_check=""

      • twAPI_menu_delim

        • Sets the separator area between the ILC save/edit/update link and the menu (icon with three stripes. This HTML and can be as simple as a "|" pipe which is the default or a HTML string such as &nbsp&nbsp|&nbsp&nbsp

        • Possible values:

          • Characters limited to 10.

          • Default: "|"

      • twAPI_ilc_hide_menu

        • If set, will hide the icon menu from showing for the respective ILC column.

        • Possible values:

          • [true|false]

          • Default: false

      • twAPI_html_only

        • N/A

        • Possible values:

          • [true|false]

          • Default: false

      • twAPI_read_only

        • N/A

        • Possible values:

          • [true|false]

          • Default: false

      • twAPI_html_doc_mode

        • N/A

        • Possible values:

          • [true|false]

          • Default: false

      • twILCDataType

        • Data type to aim for providing one field that could contain numbers and be aggregated, other option here would be number

        • Possible values (as text string):

          • [string | number]

          • Default: "string"

      • twAttrDataDelim

        • Delimiter for separating the data attributes from the ILC

        • Possible values:

          • Any URL able strings.

          • Default: | (a single pipe)

    • The Commenting API for inline comments will be expanded upon future releases and additional real-world client enhancement requests.

Having an issues:
See Troubleshooting Inline Cell Comments


A key feature of BITeamwork is the abililty to lock a comment to the Point of View (POV) of when the comment is originally authored. If a comment needs to be locked only one prompt selection value (or rather the values selected by a specific prompt) and not the selected values of the other prompts are inconsequential to the POV of the comment then Prompt Fix is used

Example

For example: In the example report seen below there are two prompts which help predicate the report data. If the Time (T02 Per Month Name) dropdown has a value of 2010/07 selected and we only care about the context of that prompt value in reference to our column then this will become the "Prompt Fix". Even though the Product (P1 Product) prompt exists and can have values selected, if we use the Prompt Fix option to select the Time dimension option as the "Prompt Fix", then when another user views the report the comment context sensitivity is only relevant for the prompt fix POV select, Time, regardless of any or no values in the Product prompt value.


Figure promptfix_ex

How-To: Step-by-Step

  1. Create any type of comment using the options described in the above sections
  2. Click on the option for Prompt Fix, Lock Comment to One Prompt Point-of-View

    Figure promptfix_1
  3. Select an option which will then focus on only one prompt for the context sensitivity of the comment

    Figure promptfix_2
  4. Click the OK button to close the Prompt Fix dialog window
  5. Submit the comment (or use the other options) as you normal
  6. Test the working nature of this by modifying the one prompt that was not selected as the "Prompt Fix". The result should be that the comment should still be showing. Now modify the prompt with which you've selected as the "Prompt Fix". Now the comment should not be visible.

All comments can be secured. If a user is given the privilege to create a comment type then that user also has the ability to secure a comment.

How to Secure a Comment

  1. Adding a cell, dashboard, or view comment from the comment prompt provides all options available to secure a comment.
  2. Click the security lock icon next to the Notify input field.

    Figure securecomment_1
  3. The Add Comment... dialog expands to show the security options area.
    • Comments have a minimum length as determined by your BITeamwork Administrator.

    Figure securecomment_2
  4. Begin typing in the field under the Find a User or Application Role label.
    • Use the auto-suggest feature here; to find users start the search with an @ symbol, to find application roles to secure the comment by, just being typing.
  5. Click the green + icon at the end of the field once the user or application role has been found and selected. This will add the user/application role to the security list.
    • You will need to remove the Everyone user/item from the list by clicking the x associated with it. The Everyone user is a placeholder identifying that the comment is open to Everyone. Once you locate user(s) or application role(s) for which to secure access to the comment, then this item should be removed from the list.

      Figure securecomment_3
    The system highlights from the auto-suggestion drop-down the names of users or application roles currently identified in the system. If you select a user or application role not in the list then no security will be assigned as there is no link to the user/application role submitted as no check is performed on arbitrary vs. existing principals (i.e.: users, application roles).

    Figure securecomment_4
  6. Click the Submit Comment button to create the comment with the applied security.
    • Comments will then appear with the lock icon to privileges users with read access of the secure comment to indicate that it is a secure comment.

      Figure securecomment_5

NOTE: You must have appropriate privileges to create comments.

See also Assigning Comments to Users and Application Roles

Viewing all dashboard comments can take place in several different ways. One or more of these approaches for an individual end-user or group may be restricted by the organization's BITeamwork administrator.

  1. View Dashboard Comments Count in the Global Header
    • On any dashboard, you can easily view the count of comments existing on the dashboard by viewing the value next to the word Comments.
    • The count is the total number of Dashboard and View Comments and does not include the count of Cell Comments or replies to any type of comments.
  2. Clicking on a Cell or View Comment
    • If a cell comment exists on a dashboard object, indicated by an icon or specific color shading on the cell, or if the object, such as a chart or header, contains a comment bubble then a comment is associated with that object. Clicking on either of these elements in read (non-augmentation of the dashboard) will only render the cell or view comment from the comment panel in the global header and not reveal dashboard comments. In the dashboard augmentation mode, the user can click on the respective view object area to create a View Comment and the BITeamwork pop-up will appear allowing access to View All Dashboard Comments as another tab option. A similar occurrence happens when clicking on a table/pivot-table cell in dashboard augmentation mode.
  3. Accessing the Dashboard RSS Feed
    • Each dashboard's comments are accessible from a XML-based Syndication Feed which is consumable via web browser, MS Outlook, or any other RSS reader having access to your network. The RSS Feed for a dashboard provides a listing of the most recent comments left on the dashboard. Access privileges to the RSS feeds are managed by the BITeamwork Administrator.

Creating a dashboard comment or a cell annotation may immediately provide you with a text field for entering comments. This field can either be a plain textbox area or it will be a text area having several formatting and insert options available above it. This latter type of entry field is referred to as the "Advanced Editor"

The Advanced Editor is a global configuration setting managed by your BI Administrator.
As of BITeamwork 3.0, this means that if the option to use the advanced editor is switch on, then all users will see the advanced editor. If switched off, then users only see the basic plain textbox area when leaving comments. This does not apply to inline cell comments.


Figure aeditor_1

As you can see in the screenshot above the advanced editor is robust and allows for many formatting features including adding images.

Using the View Dashboard Comments link in the Global Header, the BITeamwork pop-up will appear with several tabs. The initial tab from clicking on this link will always render the View All tab. Clicking on the History tab will review all comments posted by the current user.


Figure History_1

The comments shown in the History tab are comments entered via BITeamwork and not of those entered in any third party Social Vendor tool.

Observing comments left on a dashboard can be viewed in a few different ways:

All comment types can be replied to in order to create a collaborative thread based on responses from other users.


Figure Reply_1

How to Reply to a Comment?

As you are viewing any comment, below the comment, a Reply button/link is shown.

  1. View a dashboard or cell comment
  2. Click on the Reply or Comment button
  3. Type your reply to the comment in the Reply text field
  4. Click the Post Reply button to save the reply

Comments persist indefinitely in the BITeamwork system unless:

  • Purged by the BITeamwork Administrator
  • Deleted by the user who created the comment


Figure delete_1

How to Delete a Comment?

Comments can be deleted by only the user who created the comment. Once the comment is deleted it is removed from all viewable areas of the the dashboard, table cell, etc.

  1. View any cell, view, or dashboard comment you've created via the normal means of reading a comment. For dashboard and view comments you may also click on either the History tab or the View All tab from the comment folder pop-up on the Global Header.
  2. Locate the comment which you intend to remove/delete
  3. Click the trash can icon beneath your comment to delete it
  4. Follow the instructions on the prompt, if any
  5. Done
If a comment is deleted all replies related to the comment are also deleted (i.e.: no longer visible). In addition, when using Social Vendor integration, any related comments sent to a Social Vendor will NOT be deleted automatically on the Social Vendor application.

RSS Feeds allow dashboard comments to be leveraged by other applications such as Microsoft Office to consume information about dashboard comments without requiring an account to log in to the Enterprise Business Intelligence application. These XML based Feeds are a industry standard for distributing up-to-date news and information about one or more subjects; in this case dashboard comments and collaboration.

Users can access a Dashboard's comments RSS Feed by opening the BITeamwork pop-up window and clicking on the RSS Feed icon on the View All tab.


Figure delete_1

Doing so will open a new window/tab in the browser with the respective Dashboard Comments.

If you observe the URL in the browser window for the RSS Feed you may notice the dashboard name is present along with some other details. The last segment of the URL provides the ability to restrict the number of records returned in the RSS Feed. This can be helpful if attempting to display comments in a persistent fashion on a dashboard which could be accomplished in Oracle BI 11g by using a Narrative view for example.

At the top of the Business Intelligence application web page, the BITeamwork Administrator has the ability to turn on and off a banner that indicates which enviornment a user is currently operating within. This simple and unobtrusive banner is referred to as the Environment Eye.


Figure delete_1

A user has no control over the Environment Eye. It is simple an indicator to your current environment (i.e. Development, Test, SIT, QA, etc.). Its intent is to prevent mis-development or mis-directed activity if environments a user is working in are confused.

Environment Eye is typically used in all environments except for Production in which case it would obstruct the clean representation of the Business Intelligence application and portal.

The Splash Page pop-up window is a global means within the Business Intelligence Application to display current alerts , information, and direction to all end-users.

The BITeamwork Administrator controls the ability to turn on and off, or schedule a Splash Page, in order to display global information. The Splash Page may contain HTML content such as images and hyperlinks. If a user dismisses a splash page for the day, but then the administrator makes a modification to the splash page within that same day then the user will again see the splash page as it has potentially been reloaded with new content.


Figure splashpage_1

A Business Use Case for Splash Pages

An organization that has implemented Oracle BI 11g for the first time or has upgraded from a previous version of the tool may wish to provide training and other information about the new implementation to end-users. A Content Management System such as MS SharePoint or Oracle WebCenter may be used to house training documents etc. However, a Splash Page could be scheduled to show (pop-up) at the home page and login page of the dashboard portal as a user accesses the Business Intelligence application during the project Go-Live. The Administration may create the content of the Splash Page so that it contains links to the SharePoint CMS site for training documentation, and perhaps a short video welcoming the end-users to the new BI systems.

Once the end-user has read the message(s) from the Splash Page and/or accessed the links they can then choose to close the Splash Page and continue on to the BI portal having now been explicitly informed within the BI application itself.

When a user creates a Dashboard, View, or Cell Comment with the Enterprise Edition of BITeamwork they have the ability (if the user's privileges permit) to notify a User or Application Role about a comment. Once the notified User(s) and/or Application Role(s) for which the comment are selected and the comment submitted, the user(s) will receive an email (requires Oracle BI Delivers to be configured) and a dashboard alert. This alert is pushed through the native Oracle BI 11g infrastructure and does not use any custom emailing mechanism etc. The notified user(s) are given this comment notification to suggest priority and a call-to-action on their part.


Figure notification_1

Regardless of the comment notification assignee(s) the comment is still available to any users having access to the dashboard, or assigned privileges to the comment, once the comment is submitted.

If your organization has chosen to implement its Salesforce.com (SFDC) Chatter account with Oracle BI using BITeamwork in order to add Collaborative BI then just follow the steps below from the Oracle BI Dashboards to get setup. Otherwise, please contact your Oracle BI Administrator, CFO, or CTO and let them know you want BITeamwork.

  1. Navigate to any Oracle BI Dashboard
  2. Maximize the BITeamwork Collaboration Panel
  3. At the top of the Collaboration Pane, change the dropdown value from the default, BITeamwork, to Salesforce Chatter

    Figure sfdc_1
    NOTE: if there is no extra option for Salesforce Chatter then two things should be attempted:
    • Click the "Settings" (gear) icon and click the refresh button at the bottom of the pop-up window.
    • Ask you BI Administrator to double-check and test the Salesforce Chatter integration is properly configured.
  4. In the display area, the Salesforce.com Chatter logo will appear with a link. Click the Authorize Chatter link to navigate to the Salesforce.com login page.

    Figure sfdc_2
    This navigates you to the Salesforce.com authorization website which integrates your account with the Collaborative BI solution.
  5. Click the Authorize Application button on the Salesforce.com Authorization page.

    Figure sfdc_3
  6. Sign/Log in to Salesforce.com, if prompted.

    Figure sfdc_4
    If you were already signed-in to Salesforce.com, using Chatter or the Salesforce.com application you may not need to sign in. However, if your session has expired (i.e.: it's been a while since you've accessed the Salesforce.com application) you will need to sign in at this time. Please note that after you Authorize the Collaborative BI application you will not need to conduct this process each time you access the BI Dashboards or the Collaborative BI Solution.
  7. You will be returned to your network's webpage with the message below if all was successful with the integration.

    Figure sfdc_5
  8. Refresh Oracle BI dashboard page from which you initiated the Authorize Chatter process. You will now have the option for Salesforce.com Chatter and should see a new dropdown menu for the Chatter groups to which you belong.
    This may be in a different browser window or different browser tab or you can just re-open the BI Dashboards in a new window.

    Figure sfdc_6
  9. Done

As an advanced configuration, Salesforce.com allows users to have control over which portals have access to their personal information. BITeamwork uses the company-wide OAuth Remote Access configuration to integrate with Salesforce.com Chatter. At any time a user can interrupt this access, effectively breaking the previously established communication link between BITeamwork and their individual Chatter account. In order to do so, follow the instructions below:

  • Login to Salesforce.com
  • Select Setup from the user drop down menu
  • Expand the My Person Information section under Personal Setup on the left navigation pane
  • Select Personal Information
  • Scroll down the page to the Remote Access section
  • Click the Revoke button for the row(s) corresponding to established access connections created on your behalf
    WARNING: Be aware that the Application name associated with BITeamwork is established by your Salesforce.com administrator. Ensure that you are selecting the correct one in order to prevent breaking connectivity with another application you are currently utilizing. It is recommended to leave this section alone unless you know what you are doing.

If your organization has chosen to implement its Yammer system account with Oracle BI using BITeamwork in order to add Collaborative BI then just follow the steps below from the Oracle BI Dashboards to get setup as a user. If you are the BI administrator and have not yet configured this in integration BITeamwork please read the instructions in the BITeamwork Administration guide or BITeamwork Social Network Administration guide Otherwise, please contact your Oracle BI Administrator, CFO, or CTO and let them know you want BITeamwork.

User Authorization Steps:

  1. Navigate to any Oracle BI Dashboard
  2. Maximize the BITeamwork Collaboration Panel
  3. At the top of the Collaboration Pane, change the dropdown value from the default, BITeamwork Collaboration, to the Yammer option

    Figure yammer_1
    NOTE: If there is no extra option for Yammer then two things should be attempted:
    • Click the "Settings" (gear) icon and click the refresh button at the bottom of the pop-up window and try the above steps again.
    • Ask you BI Administrator to double-check and test that the Yammer integration is properly configured and enabled and that your login or your group (application role) has the correct access privilege.
  4. In the display area, the Yammer logo will appear with a link. Click the Authorize Yammer link to begin the authorization process which will navigate to the Yammer.com login page (usually a pop-up window).

    Figure yammer_2
    NOTE: Performing this step navigates you to the Yammer.com authorization website which integrates your account with the Collaborative BI solution.
  5. Click the Authorize Application button on the Yammer.com Authorization page.

    Figure yammer_3
  6. Sign/Log in to Yammer.com, if prompted. If not prompted, go to next step.

    Figure yammer_4
    After clicking the Log In button you will see the option shown in Step 6 above, so click the approve button when prompted.
    If you were already signed-in to Yammer.com, using the application you may not need to sign in. However, if your session has expired (i.e.: it's been a while since you've accessed the Yammer.com application) you will need to sign in at this time. Please note that after you Authorize the Collaborative BI application you will not need to conduct this process each time you access the BI Dashboards or the BITeamwork unless you've revoked access from the Yammer.com website or control application. In which case you will simply follow the above steps once more to connect.
  7. The open prompt will then be returned to a response page which is actually part of the BITeamwork system. The response webpage message will look similar to the one below if all was successful with the integration.

    Figure yammer_5
  8. Close the prompt window in which you conducted the last few steps above
    NOTE: This may be in a different browser window or different browser tab or you can just re-open the BI Dashboards in a new window.
  9. Refresh the Oracle BI dashboard page from which you initiated the Authorize Yammer process. You will now have the option for Yammer and should see a new dropdown menu for the Yammer groups to which you belong.

    Figure yammer_6
  10. Done

As an user profile configuration, Yammer.com allows users to have control over which portals have access to their personal information. BITeamwork uses the company-wide OAuth Remote Access configuration to integrate with Yammer. At any time a user can interrupt this access, effectively breaking the previously established communication link between BITeamwork and their individual Yammer account. In order to do so, follow the instructions below:

  • Login to Yammer.com
  • Click on the "..." (More) menu to expose the drop down menu
  • Select the Edit Profile option
  • Select My Applications from the left menu
  • Click the Revoke Access link/button for the row(s) corresponding to established application access connections created on your behalf
    WARNING: Be aware that the Application name associated with BITeamwork is established by your Yammer administrator. Ensure that you are selecting the correct one in order to prevent breaking connectivity with another application you are currently utilizing internally at your organization for another purpose. It is recommended to leave this section alone unless you know what you are doing.

If using a social app connection for Yammer, Chatter, etc. with BITeamwork you may wish to have any comment that you create be sent directly to the social app generically. First make sure that you have been given privileges by your BI Administrator and you have configured connectivity to the social application using the methods located in this user-guide. Follow the steps below and be sure to test this logic after setting the options so that you can determine the value of this interactivity to your and your business.

  1. Navigate to any Oracle BI Dashboard
  2. Maximize the BITeamwork Collaboration Panel
  3. Click the "Settings" (gear) icon to reveal the Settings tab of the prompt
  4. Check the checkbox for the application to which you'd like to post comments to upon each comment submission

    Figure social_direct_1
  5. Click the "Refresh" icon at the bottom of the prompt in order to refresh the page and affect your settings.
  • Collaborative Business Intelligence
    • The means for users and groups within an organization to collectively analyze data, share information, spread ideas, drive activity, annotate dashboards, and make better business decisions by augmenting existing Business Intelligence practices.
      See a broader definition for What is Collaborative BI?
  • Comment Context
    • The specific point-of-view of an analysis or query used when a comment was authored. Technically this includes not only prompt selection, but position of a view as it was being referenced during the creation of the comment. Any example of the position of a view would be a pivot table that is expanded to the third tier of hierarchy when a comment was authored.
  • Comment Context Sensitivity
    • The awareness of a comment to render or otherwise be affixed to the point-of-view of a user accessing a dashboard or report on which a comment has been authored. Taking this several steps further, a tangent of this concept is that a comment can be viewed whether it matches the specific context, partially matches the context, or does not match the context of the originally authored comment based on a viewing users preference. In BITeamwork, this level of control is one of the key reasons our Collaborative BI solution for Oracle BI is so accurrate and successful for our customers.
  • Comment Bookmark
    • A means to capture the specific context of a dashboard or report when the comment was originally authored. BITeamwork leverages the native BI System's bookmarking capability as the primary mechanism for capturing bookmark link references.
  • Embedded BI
    • The concept and ability to capture a view,graph, chart, or table from the BI System and render it on another web based system such as an Intranet page, SharePoint, etc. without requiring additional coding logic or development processes.
  • Social Business Intelligence
    • The ability to relay information about the exploration activities of users and groups within a Business Intelligence system while invoking decisions and actions through personal reward and other influencing factors.
  • Social Vendor
    • A centralized organization providing services that empower one or more organizations or groups of users to communicate with other users within one or more public or private groups in order to quickly disseminate timely information about activities, ideas, and perspectives. Yammer, Podio, Salesforce.com, and the Oracle Social Network are examples.
  • Social Vendor Integration
    • The means, act, and solution of incorporating a Social Vendor's services into an existing consumption based services or solution. As an example the BITeamwork solution allows for several social vendor integrations with Yammer, Salesforce.com Chatter, and Oracle Social Network.
  • BITeamwork Pop-up (or Modal)
    • The main entry point to reading and creating comments using BITeamwork. The pop-up interface (often referred to as a modal window) is a temporary augmentation of the current web page which directs the user to focus on navigating or selecting the desired functionality presented. Once the desired operation is completed, the BITeamwork pop-up will close automatically. Alternatively, a user may cancel the BITeamwork pop-up by clicking X at the upper-right corner of the pop-up to have it closed.
  • Pop-up Window
    • Windows that navigate a user to other information without disrupting the content of the current web page are referred to as Pop-up Windows. These can either be in the form of a new browser window opening in a new browser tab or single window or they can appear on top of an existing web page. BITeamwork uses this concept during Social Vendor authorization to connect users to a Social Vendor website. If your browser settings are configured to block pop-up windows, the address bar may appear with one of the images seen below preventing you from accessing the necessary Social Vendor web site page requiring your attention to authorize BITeamwork to integrate your social settings to use Collaborative Business Intelligence within your BI application. Allow the pop-up by clicking on the address bar image and accepting the pop-up.
  • Global Header
    • The main menu bar horizontally placed at the top of the Business Intelligence application. This header or bar provides the core navigation functionality for the application. It also houses the BITeamwork menu (icons) system. Most of the user-based operations are launched from this area including access to the user settings.
  • User
    • An individual account having access to the native Business Intelligence system. This account, representing a single person or purpose, typically has an account profile, settings, and privileges managed by the native Business Intelligence application on which BITeamwork augments with its Collaborative Business Intelligence functionality. This account may also have additional separately accessed Social Vendor accounts whether under a Single Sign-On security method or otherwise accessed.
  • Application Role
    • An object that allows the object oriented management of users, group, and other Application Roles ("Principals") in a Middleware system such as your native Business Intelligence application. Application Roles are controlled by your Business Intelligence Administrator and typically created and defined with some coordination on the business units having access to the BI application or the management of dashboards, reports, etc. existing in the BI application.
  • OAuth Security Standard
    • A popular and evolving Internet standard for authorizing heterogeneous applications without passing sensitive security information over a network. OAuth is a token-based security system based on a Allow-Deny-Revoke principal which allows a user's publishing application to maintain the control it provides any subscribing application. OAuth is the preferred security authorization mechanism for exchanging data within an Social Vendor.