InSite Current Release Documentation v0.8.4

  1. Log on Screen
  2. InSite Dashboard
  3. General Screen Navigation
  4. InSite Data Menu
    1. Jive Users Screen
    2. Jive Invites Screen
    3. Jive Places Screen
    4. ALL CONTENTS Data Screen
    5. Remaining Jive Content Screens
  5. Custom Views (CVs) Menu
    1. All Custom Views (CVs) Screen
    2. Building a Custom View Primer
    3. New or Edit Custom View Menu
      1. Custom View Stages
        1. General Stage Navigation
        2. New/Edit Custom View Header Section
        3. Filter Stage
        4. Select Stage
        5. Group Stage
        6. Sort Stage
        7. Limit Stage
        8. Skip Stage
        9. Unwind Stage
        10. Join Stage
        11. Sample Stage
        12. Custom View Presentation Section
        13. Custom Views - APPENDIX A - Available Fields By Data Source
        14. Custom Views - Appendix B - Data Set expressions
  6. InSite Templates Menu
    1. All Templates Screen
    2. Creating a New Template
      1. Template Fields
      2. Template Commands and Functions
        1. Subject Field Commands
        2. Template Body Field Commands
        3. Insert Menu Commands
    3. Cloning an Existing Template
  7. InSite User Sets Menu
    1. Dynamic User Sets
    2. All User Sets Screen
    3. Creating a New User Set
    4. Adding/Defining Filters for a User Set
  8. InSite Campaign Menu
    1. Components of a Campaign
    2. Types of Campaigns
    3. All Campaigns Screen
    4. Cloning an Existing Campaign
    5. Creating a New Campaign
      1. Campaign Fields
      2. Starting a Campaign
        1. Starting an Email Campaign
        2. Starting a Direct Message Campaign
  9. InSite Reports Menu
    1. Management Report
      1. Managed User Graph
    2. Content Report
    3. Places Report
  10. InSite System Menu
    1. Settings Submenu
      1. Jive Settings Screen
      2. Email Settings
      3. Campaign Approver Screen
      4. Configure Data Pull Screen
      5. Security Screen
        1. Password Complexity Screen
        2. User Login and Session Screen
    2. Pull Data Screen
    3. Users and Permissions
      1. InSite Users Screen
      2. Roles Screen
    4. Voice Command
    5. Full Screen
    6. Logout
  11. InSite Help Menu
    1. Help Documentation
    2. Report a Bug
    3. Release History

1.Section 1: Log on Screen

When logging on to InSite, please remember:

  1. To access your InSite instance, go to enter yourcompany.411labs.net.  This URL is unique to your company and will display your corporate or Jive site logo.  
  2. Your InSite instance is secured by 256-bit SSL encryption.  This ensures that communication between the InSite servers and your browser are encrypted.
  3. Your username and password are for InSite only and should be unique and distinct from your Jive log on.
  4. The username and password fields are both case-sensitive.
Yes No Suggest edit
Last updated on July 12, 2017

2.InSite Dashboard

  The InSite Dashboard is the default page that is displayed after you log in.  The InSite dashboard displays current high level metrics for your Jive instance, including the Userbase Trend and Content Trend graphs.  The UserBase Trend graph is a stacked line graph that displays the number of users in different Jive point categories over time.  The Content Trend graph is a stacked line graph of the number of content items in different categories over time.  In the future, you will be able to customize the Dashboard.

Yes No Suggest edit
Last updated on July 12, 2017

3.General Screen Navigation

Use the numbers on the images and the text below to learn about the functionality that is available on most of InSite’s screens:

1 – SEARCH BOX:  Searches across all fields, including those not in view

2 – CREATE CUSTOM VIEW:  Creates Custom View (CV) from the current screen setup.  Setup includes Fields displayed; Field Order, Filter(s), and Sort(s).

3 – CREATE FROM FILTER:  Creates customized user sets that from pre-defined filters.  For more information, see Dynamic and Static Users Sets below.

4 – EXPORT BUTTON:  Creates CSV, JSON and TDE (Tableau ) export files from the current view

5 – SHOW/HIDE COLUMNS:  Allows you to add or remove columns from the current view.  If all the columns won’t fit on the screen, a scroll bar will appear on the bottom of your browser .

6 – FILTER ROWS: Use these rows to filter your current view so that you can display your data however you want.

The Filter/Sort area has two types of filter field types that work together:  Match Type and String Type.  Use the Match Type to select one of the drop-down selections below.  Your selection works in tandem with your entry in the String Type to filter your data.  For example, if you wanted to filter down to users who have “Smith” as their last name, select the “Equal” Match Type in the top row and type “Smith” in the String Type.   You can filter on multiple fields at the same time.  For example, you can a filter that combines Last Name is equal to “Smith” AND Location is equal to “Baltimore”.   

Match Type selections:

  • Any
  • Contains
  • Equal
  • Starts With
  • Ends With
  • Matches RE (Regular Expression) – Looks for an exact match in the String row.
  • Is Blank
  • Does Not Contain
  • Does Not Start With
  • Does Not End With
  • Does Not Match RE
  • Is Not Blank

Note:  Some Match Types have custom selections based on the field type (e.g. Enabled, Manager, Approver fields)

7 – SORT ROWS:  Sorts the data in your current view by any column.  To sort, click on any column heading (below the filter rows and above the first record row) in your current view.  When you do, that column in the Sort row will turn red and the up caret will turn black signifying that your view is sorted on that field in Ascending order.  Click the same column heading again and it will turn light blue, indicating the table will be sorted by that field in Descending order. To sort on multiple fields, hold down the Shift key before you select the second or third column.  InSite will sort on the first column you selected, and the secondary sort will be nested into the first one.  

An additional function of all InSite screens is reordering the field columns.  Simply click on the field name in the field header row area and drag it to the new location you would like it to appear on the screen.  

If you wish to add or remove fields from the current view, click on the Add/Remove Columns button (#4 in the image)

8 – JIVE PROFILE LINK:  Takes you to that Jive User’s Jive Profile.  If you click on the Username in the table, the link will take you to that Jive User’s profile on your InSite-connected Jive site.  If you are not logged in to that Jive site, you will be brought to your Jive logon screen.

9 – JIVE USER AVATAR:  If you are logged into your InSite connected Jive site in a tab in the same browser as your InSite session, you will see the image of the Jive User’s avatar in this column.  If you are not logged on to your Jive site you will only see the broken image link icon.

10 – JIVE USER EMAIL LINK:  Opens an email to the address stored in the User’s Jive Profile.  Clicking on a user’s email address will open an email to the Jive User using the default email client on your PC, Mac, or mobile device – such as Outlook or Thunderbird.

11 – EDIT ROW ICON:  Sets the Jive user to be an InSite Campaign Approver or not.  Please note that clicking on this icon does not allow you to edit the user’s Jive Profile.  You will see only one field that can be changed – the Campaign Approver checkbox.  If this is checked and saved, the User’s name will appear in the Approver/Sender dropdown list when you are creating a new Direct Message (DM) Campaign.

12 – TOTAL RESULTS AREA: Shows you how many rows you are displaying per page and the total number of records based on your current Filter(s) out of the entire user list.  This is actually quite powerful.  To see how many total pieces of Content you have on your entire Jive site, go to the Contents screen and scroll to this area.

13 – PAGE NAVIGATION AREA: Lets you move between the current page of data, Next or Previous pages as well as First and Last pages.

Yes No Suggest edit
Last updated on July 12, 2017

4.InSite Data Menu

   The Data menu lists the different screens that display data extracted from your Jive Instance. For a description of how to use common interface found in each of these screens, see General Screen Navigation.  InSite displays Users, Invites, Places, and most Content from your Jive instance in fully customizable views, which can give you deep insights into the . the activity on your Jive site.  The  Jive Users screen can be used to create a Campaign to communicate with your Jive users and Potential Users across the entire site.

 

Yes No Suggest edit
Last updated on July 12, 2017

4.1.Jive Users Screen

This screen displays any of the Fields that you have chosen from  the Jive User Profile record that are available via the Jive APIs (see Show/Hide Columns). Use the Sort Rows and Filter Rows to change the current views which then can be used to generate a Dynamic User Set or a Static User Set.  

The following is a list of the fields that are available to display in the InSite Jive Users screen:

Username1
Jive ID
Avatar
Display Name
Given Name
Family Name
Formatted Name
Points
Level
Emails2
Manager
#Followers
#Following
Published
Updated
External
Visible

Enabled3
Ext Contributor
Federated
Last Update
Locale
Sendable
Timezone
Thumbnail ID
Status
Tags
Addresses
Profile
Phones
Location
Approver4
Edit4

1Username is a linked field.  Clicking on it will take the InSite user to the Jive User’s Jive Profile page.

2Email is a linked field.  Clicking on the link will start an email to the User in the To: field.

3Insite only shows Enabled Users in the default view. To view ALL users, select ANY in the Enabled field filter.(note that performance may be significantly impacted)

4InSite fields only – Not in Jive Database.

Yes No Suggest edit
Last updated on July 12, 2017

4.2.Jive Invites Screen

When an Invite Campaign Action is created – either an Invite to join your Jive community, or a Place Invite Action to existing Users – the Campaign Action injects the Invites into Jive.  Jive treats these Invites as if they were sent directly from within the Jive platform itself.

The Invites screen displays the status of Invites originating from an InSite Campaign.  Use the data from these Campaigns to determine which ones are more successful bringing users into your Jive instance or Jive place.  In this way, you can continually refine your Campaigns to maximize join rates for your Jive Instance.

The following is a list of the fields from Jive Invites that can be displayed in the InSite Invites Table screen:

Inviter
Invitee
Jive ID
State
Email
Place Type
Place

Body
Published
Sent Date
Revoker
Revocation Date
Updated

Yes No Suggest edit
Last updated on July 12, 2017

4.3.Jive Places Screen

The Places screen displays the data stored for each Space, Sub-Space and Social Group in your Jive instance. As with all other InSite data screens you can filter and sort the display of your Jive Place data.  In the future, the Jive Places screen will also display data for Jive Projects and Blogs.

The following is a list of the fields from Jive Places that are available to display in the InSite Jive Places screen:

Body
Jive ID
Type
Display Name1
Description
Status
View Count
Follower Count
Published
Updated
Owner
Like Count

Place ID
Place Topics
Visible to Ext
Content Types
Promoted Result
Group Type
Member Count
Tags
Child Count
Due Date
Start Date
Project Status

1Display Name is a linked field.  Clicking on the link will an InSite user to that Place’s Overview or Activities Page in your Jive Instance.

Yes No Suggest edit
Last updated on July 12, 2017

4.4.ALL CONTENTS Data Screen

The All Content screen displays the data stored for all content in your Jive instance – regardless of content type. As with all other Jive data screens you can filter and sort the display of your Jive Content data. The data in the All Contents view cannot currently be used to start a Campaign.

The following is a list of the fields from Jive Content that can be displayed in the InSite All Content screen:

Subject1
Type
Content_id
Jive ID
Author
Follower Count
Like Count
Parent
Parent Content Visible
Parent Place

Parent Visible
Published
Reply Count
Status
Tags
Updated
View Count
Visible To Ext
Promoted Result

1Subject is a linked field. Displays the current content in your Jive Instance (you must be logged into Jive)

Yes No Suggest edit
Last updated on July 12, 2017

4.5.Remaining Jive Content Screens

The remaining Jive Content screens (see list below) are identical to the All Content screen except they filter the content to the type that you select from the menu.  Alternatively, you can use use the filter rows in the All Content screen to achieve the same effect.  For example, the Documents Data screen will display the same data as if you filtered the All Content by applying the filter EQUALS and the string type “document” to the Type column.  For a description of how to use the common interface found in these screens, including Sorting and Filtering, see General Screen Navigation.

The remaining Jive Content screens are listed below:

  • Discussions/Questions Table Screen
  • Documents Table Screen
  • Uploaded Documents (Files) Table Screen
  • Polls Table Screen
  • Blog Posts Table Screen
  • Favorites Table Screen
  • Tasks Table Screen
  • Status Updates Table Screen
  • Videos Table Screen
  • Direct Messages
Yes No Suggest edit
Last updated on July 12, 2017

5.Custom Views (CVs) Menu

The Custom Views menu allows you to create, clone, edit and manage your written Custom Views (CVs).  CVs are InSite queries that are more complex and robust than our regular Jive data screens and allow you to create and save queries that use more than one Jive table or even multiple data sources.  Saved CVs can be saved, re-executed in the background and exported from Insite in a variety of formats.

 

Yes No Suggest edit
Last updated on July 12, 2017

5.1.All Custom Views (CVs) Screen

This screen displays all your existing Custom Views, allowing you to review/edit, copy, re-execute, delete, and view the resulting reports from your CVs using a single interface. As with all other InSite screens you can search, filter, sort, export as well as other actions from this screen.

In the Subject field of a Template the commands available are:

  To Clone a Custom View
  To Delete a Custom View
  To Edit a Custom View
   To Re-generate a Custom View
  To View a generated a Custom View generated Report

 

 

Yes No Suggest edit
Last updated on July 13, 2017

5.2.Building a Custom View Primer

asigairga

Yes No Suggest edit
Last updated on July 12, 2017

5.3.New or Edit Custom View Menu

iwfiowEFiwfoi

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.Custom View Stages

arigar[i

Yes No Suggest edit
Last updated on July 12, 2017

5.3.1.1.General Stage Navigation

General Stage Navigation

Adding a Stage to a CV

Disable Stage – To temporarily deactivate a Stage, click on the checkmark to the left of the trashcan icon in the upper right corner of the Stage you wish to disable.  This is very useful when trying to debug a complex Custom View, since you don’t need to delete a Stage to determine if it is the source of a problem.  you can deactivate it and then re-enable it to see if there is any effect on CV error messages you have been getting or changes to the Preview CV Report results at the bottom left of the Edit CV screen.

Delete Stage – You can delete a Stage by clicking on the trashcan icon in the upper right corner of the Stage you are working on.  This cannot be undone,  You will have to add the Stage back, move it to the proper place in the overall CV and edit the Stage parameters in order to restore it.  As a safety measure you should get into the habit of disabling a Stage to see if removing it will have the desired effect – before you delete it.

Moving a Stage – You can easily reorder Stages simply by clicking in the Header/Title area of the Stage and moving it up or down in the Custom View you are creating/editing.

Delete Row

Add Row

Yes No Suggest edit
Last updated on December 3, 2017

5.3.1.2.New/Edit Custom View Header Section

The CUSTOM VIEWS HEADER Stage

Name

Give your CV a meaningful name that will help you to separate it from another, similar CV when you need to find it again in 6 months.

Description

The description is a long text field where you can and should provide a more detailed description of the purpose and use of the CV.  We also recommend using the Description field to provide some help text about how other users can change or update some of the parameters of the CV, such as changing the Date Range to run the CV against.

Data Source

The Data Source is the first or primary data source that the CV will use to produce the generated report.  Select the Data Source that is central to the finished report.  You have many options under Data Source to choose from:

 

No, Data Source Description
1. Campaigns Pulls data from the Campaigns list in InSite.
2. Custom Views Pulls data from the Custom Views list in InSite.
3. Data Exports Pulls data from the Data Exports list in InSite.
4. Jive Content Pulls data from the Jive Content table in InSite.
5. Jive DES Pulls data from the Jive DES table in InSite.
6. Jive Invites Pulls data from the Jive Invites table in InSite.
7. Jive Messages Pulls data from the Jive Direct Messages table in InSite.
8. Jive Places Pulls data from the Jive Places table in InSite.
9. Jive Users Pulls data from the Jive Users table in InSite.
10. Logs Pulls data from the InSite log files.
11. Pulls Pulls data from the Data Pulls record list in InSite.
12. Templates Pulls data from the Templates list in InSite.
13. User Groups Sets Pulls data from the User Sets list in InSite.
14. Users Pulls data from the InSite Users list.
15. List of Existing CVs All CVs that you create will also be listed at the bottom of the drop down list and can be a data source for another CV.

 

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.3.Filter Stage

The FILTER Stage

The Filter stage allows you to restrict the list of records displayed – based on that filter.  While not a hard and fast rule, it is usually a good idea to have a Filter stage as your first stage in your CV.  This generally will make your CV more efficient as following stages will just be working on the restricted number of records based on the filter.

Field

Field is a drop-down list of fields you can filter your CV query on.  The list of available fields is populated once you select a Data Source in the CV Header stage.  See Appendix B [Link] for a list of available fields per data source.

Filter

Based on the Field you select on the left, the Filter type will automatically update.  So if you pick a numerical field the Filter will switch to a greater than/less than filter.  If you choose a text field, the filter will switch to a “Contains”, etc. filter with an open field for you to put your filter string in.

Add another Filter Field

You can filter on multiple fields within your selected Data Source.  You can also do multiple filters on the same field.  More than one filter on the same field behave as an AND function.  InSite currently does not have an OR or other functions.

 

To add another filter click the “+” sign on the left of the Filter Stage.  Then choose your field and set up your filter for that field.

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.4.Select Stage

The SELECT Stage

Field

Display

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.5.Group Stage

The GROUP Stage

Group By Field

Expression

Accumulator Field

Expression

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.6.Sort Stage

The SORT Stage

Field

Order

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.7.Limit Stage

The LIMIT Stage

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.8.Skip Stage

The SKIP Stage

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.9.Unwind Stage

The UNWIND Stage

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.10.Join Stage

The JOIN Stage

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.11.Sample Stage

The SAMPLE Stage

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.12.Custom View Presentation Section

The CUSTOM VIEWS PRESENTATION Stage

The presentation Stage is the one stage in a Custom View that you can neither add nor remove.  It controls how your CV data displays in the final report.

Field

The original name of your CV field.  This is not editable and will always display the name of the field in the database.  Also, you can click and drag in this column to reorder the display order of your fields on your final report.

Title

The name of your field as it will be displayed in the column headings in your final report.  You can rename the column header labels here so that they are more understandable to someone looking at your report for the first time.  As an example, you could change the default column label for Username from “Username (username)” to “Login ID”.

Visible

If checked the field (column) will display in the final report.  If unchecked it will not display.

Type

Number

String

Boolean

Date

Filter Type

Number

String

Boolean

Date

No Filter

List

Checkbox

Other

Searchable

If checked the field (column) will searchable via the Global Search box in the final report.  If unchecked it will not be searchable.

 

Sortable

If checked the field (column) will sortable in the final report.  If unchecked it will not be sortable.

 

Width

Controls the width the column will display in the final report.

Render-As

Render-As controls how the data will be display in the final report.

No, Parameter Description
1. Action
2. Array Count
3. As-Is
4. Attachments
5. Campaign Action
6. Checkbox Renders boolean data (Yes, No) as a checked or unchecked box in the final report.
7. Content Versions
8. Custom View Action
9. Data Export Filename
10. Date and Time
11. DES Activity
12. DES Actor
13. DES Object
14. DES Object Type
15. Dump
16. Edit Only
17. Favorite
18. Filter Specification
19. HTML Text
20. Jive User Emails
21. Jive User Primary Email
22. Jive User Tags
23. Jive User Thumbnails
24. Join Addresses
25. Join Values
26. Linked
27. Linked to Jive HTML
28. List
29. Log Details
30. Log Subject
31. Mixed
32. Object ID
33. People
34. Person
35. Place
36. Preview
37. Profile
38. Simple Mixed
39. String Array
40. User Array
41. Wrapped Text
42. Yes No
43. Yes No Flagged

 

Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.13.Custom Views - APPENDIX A - Available Fields By Data Source

Custom Views – APPENDIX A – Available Fields By Data Source

Data Source: Campaigns

 

No,

Field

Description

1.

Archived

 

2.

Author

 

3.

Campaign Approver

 

4.

Created

 

5.

Description

 

6.

Disapproval Reason

 

7.

InSite ID

 

8.

Name

 

9.

State

 

10.

Template

 

11.

Type

 

12.

Updated

 

13

User Set

 

Data Source: Custom Views

 

No,

Field

Description

1.

# Members

 

2.

Author

 

3.

Created

 

4.

Data Source

 

5.

Datatables Specification

 

6.

Description

 

7.

Error

 

8.

InSite ID

 

9.

Last Generated

 

10.

Name

 

11.

Specification

 

12.

State

 

13

Updated

 

Data Source: Data Exports

 

No,

Field

Description

1.

Author

 

2.

Created

 

3.

Filename

 

4.

Finished

 

5.

InSite ID

 

6.

Name

 

7.

Parameters

 

8.

Started

 

9.

Status

 

10.

Status Comment

 

11.

Type

 

Data Source: Jive Content

No,

Field

Description

1.

Author

 

2.

Author ID

 

3.

Content ID

 

4.

Created

 

5.

Follower Count

 

6.

InSite ID

 

7.

Jive ID

 

8.

Like Count

 

9.

Parent

 

10.

Parent Content Visible

 

11.

Parent Place

 

12.

Parent Visible

 

13.

Promoted Result

 

14.

Reply Count

 

15.

Status

 

16.

Subject

 

17.

Tags

 

18.

Type

 

19.

URL

 

20.

Updated

 

21.

View Count

 

22.

Visible to Ext

 

Data Source: Jive DES

 

No,

Field

Description

1.

Activity

 

2.

Actor ID

 

3.

Actor Type

 

4.

InSite ID

 

5.

Object ID

 

6.

Object Type

 

7.

Parameters

 

8.

Timestamp

 

9.

UUID

 

Data Source: Jive Invites

 

No,

Field

Description

1.

Body

 

2.

Created

 

3.

Email

 

4.

InSite ID

 

5.

Invitee

 

6.

Inviter

 

7.

Jive ID

 

8.

Place

 

9.

Revocation Date

 

10.

Revoker

 

11.

Sent Date

 

12.

State

 

13

Updated

 

Data Source: Jive Messages

 

No,

Field

Description

1.

Created (Published)

 

2.

Created (Question)

 

3.

Followers (like-count)

 

4.

Followers (on_behalf_of)

 

5.

Followers (reply_count)

 

6.

InSite ID

 

7.

Jive ID

 

8.

Manager (answer)

 

9.

Manager (answered_question_count)

 

10.

Manager (attachments)

 

11.

Manager (author)

 

12.

Manager (content)

 

13.

Manager (content_images)

 

14.

Manager (content_videos)

 

15

Manager (discussion)

 

16.

Manager (follower_count)

 

17.

Manager (from_quest)

 

18.

Manager (helpful)

 

19.

Manager (helpful_count)

 

20.

Manager (last_activity)

 

21.

Manager (outcome_counts)

 

22.

Manager (outcome_type_names)

 

23.

Manager (outcome_types)

 

24.

Manager (parent_place)

 

25.

Manager (via)

 

26.

Manager (view_count)

 

27.

Manager (visible_to_external_contributors)

 

28.

Name (highlight_body)

 

29.

Name (highlight_subject)

 

30.

Name (highlight_tags)

 

31.

Name (parent)

 

32.

Name (parent_content)

 

33.

Name (parent_content_visible)

 

34.

Name (parent_visible)

 

35.

Name (promoted_visible)

 

36.

Name (status)

 

37.

Name (subject)

 

38.

Name (tags)

 

39.

Type (search_rankings)

 

40.

Type (type)

 

41.

Type (unhelpful_count)

 

42.

Undated

 

Data Source: Jive Places

 

No,

Field

Description

1.

Child Count

 

2.

Content Types

 

3.

Created

 

4.

Description

 

5.

Display Name

 

6.

Due Date

 

7.

Follower Count

 

8.

Group Type

 

9.

InSite ID

 

10.

Jive ID

 

11.

Like Count

 

12.

Member Count

 

13.

Name

 

14.

Owner

 

15.

Place ID

 

16.

Place Topics

 

17.

Project Status

 

18.

Promoted Result

 

19.

Start Date

 

20.

Status

 

21.

Tags

 

22.

Type

 

23.

URL

 

24.

Updated

 

25.

View Count

 

26.

Visible to Ext

 

Data Source: Jive Users

 

No,

Field

Description

1.

Addresses

 

2.

Approver

 

3.

Avatar

 

4.

Created

 

5.

Display Name

 

6.

Emails

 

7.

Enabled

 

8.

External Contributor

 

9.

External User

 

10.

Family Name

 

11.

Federated

 

12.

Followers

 

13.

Following

 

14.

Formatted Name

 

15.

Given Name

 

16.

InSite ID

 

17.

Jive ID

 

18.

Last Login

 

19.

Last Update

 

20.

Level

 

21.

Locale

 

22.

Location

 

23.

Manager

 

24.

Manager Display Name

 

25.

Manager Emails

 

26.

Phones

 

27.

Points

 

28.

Primary Email

 

29.

Profile

 

30.

Sendable

 

31.

Status

 

32.

Tags

 

33.

Thumbnail ID

 

34.

Timezone

 

35

URL

 

36.

Updated

 

37.

Username

 

38.

Visible

 

Data Source: Logs

 

No,

Field

Description

1.

Action

 

2.

Created

 

3.

Details

 

4.

InSite ID

 

5.

Kind

 

6.

Scope

 

7.

Subject

 

Data Source: Pulls

 

No,

Field

Description

1.

Author

 

2.

Component

 

3.

Created

 

4.

Description

 

5.

Error

 

6.

InSite ID

 

Data Source: Templates

 

No,

Field

Description

1.

Author

 

2.

Created

 

3.

Description

 

4.

Editable

 

5.

InSite ID

 

6.

Name

 

7.

Subject

 

8.

Template

 

9.

Type

 

10.

Updated

 

Data Source: User Sets

 

No,

Field

Description

1.

# Members

 

2.

Author

 

3.

Created

 

4.

Description

 

5.

Editable

 

6.

InSite ID

 

7.

Name

 

8.

Specification

 

9.

Type

 

10.

Updated

 

Data Source: Users

 

No,

Field

Description

1.

Created

 

2.

Deleted

 

3.

Email

 

4.

First Name

 

5.

InSite ID

 

6.

Last Name

 

7.

Role

 

8.

Updated

 

9.

Username

 

Data Source: List of Existing CVs

 

No,

Field

Description

1.

Archived

 

2.

Author

 

3.

Campaign Approver

 

4.

Created

 

5.

Description

 

6.

Disapproval Reason

 

7.

InSite ID

 

8.

Name

 

9.

State

 

10.

Template

 

11.

Type

 

12.

Updated

 

13

User Set

 
Yes No Suggest edit
Last updated on December 2, 2017

5.3.1.14.Custom Views - Appendix B - Data Set expressions

Appendix B – Data Set expressions

Expressions

Expressions can include field paths and system variables, literals, expression objects, and expression operators. Expressions can be nested.

Field Path and System Variables

Aggregation expressions use field path to access fields in the input documents. To specify a field path, use a string that prefixes with a dollar sign $the field name or the dotted field name, if the field is in embedded document. For example, “$user” to specify the field path for the user field or “$user.name” to specify the field path to “user.name” field.

“$<field>” is equivalent to “$$CURRENT.<field>”where the CURRENT is a system variable that defaults to the root of the current object in the most stages, unless stated otherwise in specific stages. CURRENT can be rebound.

Along with the CURRENT system variable, other system variables are also available for use in expressions. To use user-defined variables, use $let and $map expressions. To access variables in expressions, use a string that prefixes the variable name with $$.

Literals

Literals can be of any type. However, MongoDB parses string literals that start with a dollar sign $ as a path to a field and numeric/boolean literals in expression objects as projection flags. To avoid parsing literals, use the $literal expression.

Expression Objects

Expression objects have the following form:

{ <field1>: <expression1>, … }

If the expressions are numeric or boolean literals, MongoDB treats the literals as projection flags (e.g. 1 or true to include the field), valid only in the $project stage. To avoid treating numeric or boolean literals as projection flags, use the$literal expression to wrap the numeric or boolean literals.

Operator Expressions

Operator expressions are similar to functions that take arguments. In general, these expressions take an array of arguments and have the following form:

{ <operator>: [ <argument1>, <argument2> … ] }

If operator accepts a single argument, you can omit the outer array designating the argument list:

{ <operator>: <argument> }

To avoid parsing ambiguity if the argument is a literal array, you must wrap the literal array in a $literal expression or keep the outer array that designates the argument list.

 

Boolean Expressions

Boolean expressions evaluate their argument expressions as booleans and return a boolean as the result.

In addition to the false boolean value, Boolean expression evaluates as false the following: null, 0, and undefined values. The Boolean expression evaluates all other values as true, including non-zero numeric values and arrays.

Name

Description

$and

Returns true only when all its expressions evaluate to true. Accepts any number of argument expressions.

$or

Returns true when any of its expressions evaluates to true. Accepts any number of argument expressions.

$not

Returns the boolean value that is the opposite of its argument expression. Accepts a single argument expression.

Set Expressions

Set expressions performs set operation on arrays, treating arrays as sets. Set expressions ignores the duplicate entries in each input array and the order of the elements.

If the set operation returns a set, the operation filters out duplicates in the result to output an array that contains only unique entries. The order of the elements in the output array is unspecified.

If a set contains a nested array element, the set expression does not descend into the nested array but evaluates the array at top-level.

Name

Description

$setEquals

Returns true if the input sets have the same distinct elements. Accepts two or more argument expressions.

$setIntersection

Returns a set with elements that appear in all of the input sets. Accepts any number of argument expressions.

$setUnion

Returns a set with elements that appear in any of the input sets. Accepts any number of argument expressions.

$setDifference

Returns a set with elements that appear in the first set but not in the second set; i.e. performs a relative complement of the second set relative to the first. Accepts exactly two argument expressions.

$setIsSubset

Returns true if all elements of the first set appear in the second set, including when the first set equals the second set; i.e. not a strict subset. Accepts exactly two argument expressions.

$anyElementTrue

Returns true if any elements of a set evaluate to true; otherwise, returns false. Accepts a single argument expression.

$allElementsTrue

Returns true if no element of a set evaluates to false, otherwise, returns false. Accepts a single argument expression.

Comparison Expressions

Comparison expressions return a boolean except for $cmp which returns a number.

The comparison expressions take two argument expressions and compare both value and type, using the specified BSON comparison order for values of different types.

Name

Description

$cmp

Returns: 0 if the two values are equivalent, 1 if the first value is greater than the second, and -1 if the first value is less than the second.

$eq

Returns true if the values are equivalent.

$gt

Returns true if the first value is greater than the second.

$gte

Returns true if the first value is greater than or equal to the second.

$lt

Returns true if the first value is less than the second.

$lte

Returns true if the first value is less than or equal to the second.

$ne

Returns true if the values are not equivalent.

 

Arithmetic Expressions

Arithmetic expressions perform mathematical operations on numbers. Some arithmetic expressions can also support date arithmetic.

Name

Description

$add

Adds numbers to return the sum, or adds numbers and a date to return a new date. If adding numbers and a date, treats the numbers as milliseconds. Accepts any number of argument expressions, but at most, one expression can resolve to a date.

$subtract

Returns the result of subtracting the second value from the first. If the two values are numbers, return the difference. If the two values are dates, return the difference in milliseconds. If the two values are a date and a number in milliseconds, return the resulting date. Accepts two argument expressions. If the two values are a date and a number, specify the date argument first as it is not meaningful to subtract a date from a number.

$multiply

Multiplies numbers to return the product. Accepts any number of argument expressions.

$divide

Returns the result of dividing the first number by the second. Accepts two argument expressions.

$mod

Returns the remainder of the first number divided by the second. Accepts two argument expressions.

String Expressions

String expressions, with the exception of $concat, only have a well-defined behavior for strings of ASCII characters.

$concat behavior is well-defined regardless of the characters used.

Name

Description

$concat

Concatenates any number of strings.

$substr

Returns a substring of a string, starting at a specified index position up to a specified length. Accepts three expressions as arguments: the first argument must resolve to a string, and the second and third arguments must resolve to integers.

$toLower

Converts a string to lowercase. Accepts a single argument expression.

$toUpper

Converts a string to uppercase. Accepts a single argument expression.

$strcasecmp

Performs case-insensitive string comparison and returns: 0 if two strings are equivalent, 1 if the first string is greater than the second, and -1 if the first string is less than the second.

Text Search Expressions

Name

Description

$meta

Access text search metadata.

Array Expressions

Name

Description

$size

Returns the number of elements in the array. Accepts a single expression as argument.

Variable Expressions

Name

Description

$map

Applies a subexpression to each element of an array and returns the array of resulting values in order. Accepts named parameters.

$let

Defines variables for use within the scope of a subexpression and returns the result of the subexpression. Accepts named parameters.

Literal Expressions

Name

Description

$literal

Return a value without parsing. Use for values that the aggregation pipeline may interpret as an expression. For example, use a$literal expression to a string that starts with a $ to avoid parsing as a field path.

Date Expressions

Name

Description

$dayOfYear

Returns the day of the year for a date as a number between 1 and 366 (leap year).

$dayOfMonth

Returns the day of the month for a date as a number between 1 and 31.

$dayOfWeek

Returns the day of the week for a date as a number between 1 (Sunday) and 7 (Saturday).

$year

Returns the year for a date as a number (e.g. 2014).

$month

Returns the month for a date as a number between 1 (January) and 12 (December).

$week

Returns the week number for a date as a number between 0 (the partial week that precedes the first Sunday of the year) and 53 (leap year).

$hour

Returns the hour for a date as a number between 0 and 23.

$minute

Returns the minute for a date as a number between 0 and 59.

$second

Returns the seconds for a date as a number between 0 and 60 (leap seconds).

$millisecond

Returns the milliseconds of a date as a number between 0 and 999.

$dateToString

Returns the date as a formatted string.

Conditional Expressions

Name

Description

$cond

A ternary operator that evaluates one expression, and depending on the result, returns the value of one of the other two expressions. Accepts either three expressions in an ordered list or three named parameters.

$ifNull

Returns either the non-null result of the first expression or the result of the second expression if the first expression results in a null result. Null result encompasses instances of undefined values or missing fields. Accepts two expressions as arguments. The result of the second expression can be null.

 

Accumulators (can be used in grouping operations)

Accumulators, available only for the $group stage, compute values by combining documents that share the same group key. Accumulators take as input a single expression, evaluating the expression once for each input document, and maintain their state for the group of documents.

Name

Description

$sum

Returns a sum for each group. Ignores non-numeric values.

$avg

Returns an average for each group. Ignores non-numeric values.

$first

Returns a value from the first document for each group. Order is only defined if the documents are in a defined order.

$last

Returns a value from the last document for each group. Order is only defined if the documents are in a defined order.

$max

Returns the highest expression value for each group.

$min

Returns the lowest expression value for each group.

$push

Returns an array of expression values for each group.

$addToSet

Returns an array of unique expression values for each group. Order of the array elements is undefined.

 

Yes No Suggest edit
Last updated on December 2, 2017

6.InSite Templates Menu

The Templates menu allows you to create, clone, edit and manage your written Templates.  Templates are documents that contain boilerplate language that is used as a starting point for different Campaigns (they are similar to a mail merge document in MS Word).  There are currently two different types of Templates that correspond to Campaign Types:  Email-Only Templates and Direct Message Templates.   When a campaign is started, InSite injects data into the template using merge fields, such as invitee name, email address, place name, etc, so that Campaign participants receive personalized messages regarding a specific action to take.

 

Yes No Suggest edit
Last updated on July 12, 2017

6.1.All Templates Screen

This screen displays all your existing templates, regardless of type, allowing you to review/edit, copy, and delete them using a single interface.  See the Action column in this screen for the icons that correspond to the above actions (for more information on how to use the filter/sort functionality found in this screen, see General Screen Navigation). Note: Once a Template has been attached to a Campaign – it can no longer be edited or deleted – only cloned.

 

Yes No Suggest edit
Last updated on July 12, 2017

6.2.Creating a New Template

The following templates can be created in InSite:

  • Email-Only Templates:  Email-Only Templates are used to communicate directly with Jive users via email.  When using these templates in an Email-Only Campaign, the emails are sent from the corporate email address that is set up in Jive’s System/Settings/Email configuration page.
  • Direct Message (DM) Templates:  Direct Message templates are used with Direct Message Campaigns to communicate directly with existing users on your site via DMs.
  • Place Invite Templates:  Coming Soon
  • Community (Jive Site) Invite Templates:  Coming Soon
  • Share Templates:  Coming Soon
Yes No Suggest edit
Last updated on July 12, 2017

6.2.1.Template Fields

In order to create a new template of any type, you will need to complete the following five fields (see the following section for a list of common commands/functions available in each field):

  • Type: This drop-down menu allows you to change the type of Template you are creating.  You can change the template type at a later date.
  • Name: Give the template a name to help remind you of its purpose and when/how often it will be used.  Tip:  Use a standard naming convention such to help you sort through dozens of Templates week or months after the: This is the Subject line of the Direct Message (DM), Invite or Email-Only Template that you want users or potential users to see in the subject field.  Please note the Insert button (described below) allows you to insert merge fields into the Subject.
  • Template Body: Use this field to compose the body of the message and insert merge fields where appropriate. NOTE:  DMs are limited within Jive to 255 characters, including HTML such as image links.  If you are using non-western languages such as Chinese or Japanese the character count is cut in half – to 127 characters.  To assist you with composing DMs within the limit, the New/Edit Template pop-up keeps a running count of characters in the lower right of the Subject and Body fields.  If you find that all or part of a Campaign fails when launched, check the character count in the template.  When the Merge Fields are replaced with live data, the combined character count for individual DMs in a Campaign may be over the threshold.
  • Description:  Use this field to describe the purpose, audience and intent of your Template.  Keep in mind that the description should clearly identify the Template so that someone could find it if you were not available, or if you had not looked at this Template for a year or more.  The Description does not appear in the message that is sent out in the Campaign

Yes No Suggest edit
Last updated on July 12, 2017

6.2.2.Template Commands and Functions

The section below describes the basic commands and functions available within template fields; however some commands may not be available depending on the specific template you are creating.

Yes No Suggest edit
Last updated on July 12, 2017

6.2.2.1.Subject Field Commands

In the Subject field of a Template the commands available are:

  Cut command
  Copy command
  Paste command
   Paste from Word command
  Insert Merge Field command (List of merge fields below)

Yes No Suggest edit
Last updated on July 12, 2017

6.2.2.2.Template Body Field Commands:

Note:  The HTML editor used by InSite is very similar to the TinyMCE editor that Jive uses for Jive documents and Discussions:

CUT, COPY & PASTE Commands
Cut command
Copy command
Paste command
Paste from Word command
 
FORMAT TEXT Commands
Bold command
Italics command
Underline command
Strikethrough command
Subscript command
Superscript command
 
BULLETS, INDENTING & QUOTING Commands

In the Template Body field of a Template the commands available are:

   Insert/Remove Numbered List command
  Insert/Remove Bulleted List command
  Decrease Indent command
  Increase Indent command
  Block Quote command
 
HYPERLINK Commands
Insert Hyperlink command
Remove Hyperlink command
 
IMAGE, TABLE & LINE Commands
   Insert Image command
  Insert Table command
   Insert Horizontal Line command
 
INSERT & SOURCE Commands
  Insert Merge Field command (List of merge fields below)
  View HTML Source command

 

Yes No Suggest edit
Last updated on July 12, 2017

6.2.2.3.Insert Menu Commands

In the   Menu the following merge fields are available for insertion into the Subject and the Template Body fields of the Template:

User Merge Fields Available:

Jive ID [[user.jive_id]]
Username [[user.username]]
Follower Count [[user.follower_count]]
Following Count [[user.following_count]]
Level Points [[user.level.points]]
Level Name [[user.level.name]]
Level Image [[user.level_uri]]
Given Name [[user.name.given]]
Family Name [[user.name.family]]
Full Name [[user.name.formatted]]
Manager’s Username [[user.manager.username]]
Manager’s Given Name [[user.manager.name.given]]
Manager’s Family Name [[user.manager.name.family]]
Manager’s Full Name [[user.manager.name.formatted]]
Manager’s Jive ID [[user.manager.jive_id]]
Location [[user.location]]
Timezone [[user.timezone]]

Campaign Merge Fields Available:

Name of the Campaign [[campaign.author.displayName]]
First Name of the Campaign Author [[campaign.author.firstName]]
Last Name of the Campaign Author [[campaign.author.lastName]]
Email of the Campaign Author [[campaign.author.email]]
Campaign Type [[campaign.type]]

New Direct

Yes No Suggest edit
Last updated on July 12, 2017

6.3.Cloning an Existing Template

Cloning an Existing Template is an easy way to create a new template if you plan modifying an existing template for your new Campaign.  To Clone a template, find the template you want to clone from the All Template Screen and select the Clone icon from the Action Column (the icon is two pages next to each other).  This will bring up the Clone Template pop-up which will allow you to view/change the Template Fields.

Yes No Suggest edit
Last updated on July 12, 2017

7.InSite User Sets Menu

The User Sets menu allows you to create, clone, edit, and manage your User Sets.  A User Set a collection of Jive Users or Prospective Users. Currently, only Dynamic Users Sets are available, however, future releases will include other types of User Sets, including Static and Prospective User Sets.  When used with a Campaign, a User Set provides the list of Participants to the Campaign while the Template provides the message to those participants.

 

Yes No Suggest edit
Last updated on July 12, 2017

7.1.Dynamic User Sets

A Dynamic User Set (DUS) is a pre-defined query or filter (or set of filters) that can be reused over and over again.  It is not a list of names, but a stored set of rules to generate a new list of Participants whenever the Dynamic User Set is executed.

A good example of how to use Dynamic User Sets is welcoming new users to your Jive site.  First, you would create a Dynamic User Set based on a filter that is applied to the field “Created” for a specific time frame, such as the previous week (Tip: Remember to use a clear naming convention when saving your User Sets, such as “New Users from DATE to DATE”).  Next, you would create both a Direct Message Template and a Direct Message Campaign that uses this template to send a welcome message to the User Set you just created (see Templates and Campaigns for more information).  In this way, you can continue to build and deploy new User Sets and Campaigns to welcome each cohort of users that join your sites.  For more information on how to create a new User Set, see below.

Yes No Suggest edit
Last updated on July 12, 2017

7.2.All User Sets Screen

The All User Sets screen displays a list of your User Sets that you have and saved in InSite.  You can sort and filter your User Sets, just as you can other screens with tabular data within InSite (for more information on how to use the filter/sort functionality, see General Screen Navigation).

The following columns are available in the All User Sets screen:

  • Name
  • Type
  • Description
  • Author
  • Created
  • Updated
  • # Members
  • Specification
  • Action
Yes No Suggest edit
Last updated on July 12, 2017

7.3.Creating a New User Set

Currently, only Dynamic User Sets are supported.  To create a new Dynamic User Set, select New Dynamic User Set from the User Set Menu.  Next, complete the Dynamic User Set Fields in the pop-up below using the guidance text below.

User Set Fields

The following fields should be completed when creating a new Dyanamic User Set:

  • Name: Give the User Set a name that will help remind you about its purpose and when/how often it will be used.  Tip:  Use a standard naming convention to help you quickly identify the User Set you are looking for at a later date.  
  • Type: This field defaults to the new User Set you selected from the User Set Menu.  Once additional User Sets become available, you will be able to change the type using the drop-down in this field.  
  • Description:  Use this field to clearly describe the purpose, audience, and intent of your User Set.   The description of the example Dynamic User Set described in the above section might read:  “User Set created to capture new users who have joined the site from [DATE] to [DATE].
  • Filter Definition:  The Filter Definition field is where you define the Filter (or Query) InSite should use to create your Dynamic User Set.  Please see the next section about how to create and apply filter criteria to your User Set. 
Username
Jive ID
Avatar
Display Name
Given Name
Family Name
Formatted Name
Points
Level
Emails
Manager
#Followers
#Following
Published
Updated
External
Visible
Enabled
Ext Contributor
Federated
Last Update
Locale
Sendable
Timezone
Thumbnail ID
Status
Tags
Addresses
Profile
Phones
Location
Approver*
Edit*

*InSite fields only – Not in Jive Database.

 

Yes No Suggest edit
Last updated on July 12, 2017

7.4.Adding/Defining Filters for a User Set

You can add one or more filters to your User Set by clicking on the “Add Filter” button at the bottom of the “New Dynamic User Set” pop-up screen.  You will notice that the list of Jive user fields available below to Filter a Dynamic User Set is the same as the list found in the Data Menu section of this document.

Username
Jive ID
Avatar
Display Name
Given Name
Family Name
Formatted Name
Points
Level
Emails
Manager
#Followers
#Following
Published
Updated
External
Visible
Enabled
Ext Contributor
Federated
Last Update
Locale
Sendable
Timezone
Thumbnail ID
Status
Tags
Addresses
Profile
Phones
Location
Approver*
Edit*

*InSite fields only – Not in Jive Database.

Defining a Filter

To define one or more filters for a Dynamic User Set, follow the instructions below:

  1. Under the Field heading, select a Filter Field from the dropdowns.
  2. Under the Filter heading, select a Filter Type from the dropdown. You will notice that InSite automatically displays the structure of the Filter for you.  For example, if you selected  “Given Name” from the Filter dropdown, you will have the following selections for the filter type: : Contains, Starts With, Ends With, or Matches Regular Expression.
  3. In the next box, enter a Filter Value that you would like to filter on.   For example, to create a filter for all users that have the last name “Smith,” you would need to select “Equals” as a Filter Type and “Smith” as a Filter Value.   
  4. You can continue to add additional Filters to the New Dynamic User Set until you are satisfied that you have captured the list of Users you would like to keep.  Click on the Preview Users in this Set button to view the results of your current Filter.  
  5. Click on the Create New User Set button to save your Dynamic User Set.

Note:  You can also create a new Dynamic User Set by going to the DATA → JIVE USERS table screen and setting up your Filter on that screen.   If you build your filter on that screen, simply click “Create from Filter” button in the upper right of the Jive Users Screen and select Dynamic User Set.

Yes No Suggest edit
Last updated on July 12, 2017

8.InSite Campaign Menu

  The Campaigns menu allows you to  create, clone and manage your InSite Campaigns. Campaigns are a coordinated set of communications to a specific group of Users or Potential Users that are designed to elicit an action by the recipient.  Actions can include anything from joining your Jive site, completing their Jive User profile, or interacting with content and/or other users. Currently, there are two different types of InSite Campaigns: Email-Only Campaigns and Direct Message Campaigns (additional campaigns are in development).  Both of these Campaigns are designed to utilize a different communication method and to reach a different type of User or Prospective User.

 

Yes No Suggest edit
Last updated on July 12, 2017

8.1.Components of a Campaign

All Campaigns consist of the following two inter-related components:

  • Template:  Templates are documents that contains boilerplate language and are used as a starting point for different Campaigns (they are similar to a mail merge document in MS Word).   When a campaign is started, InSite injects data into the template using merge fields, such as invitee name, email address, place name, etc, so that Campaign participants receive personalized messages regarding a specific action to take.
  • User Set:  A User Set is a list of Jive Users or Prospective Users that receive a customized message (created by injecting data into merge fields in the Template)  when the campaign is initiated.  
Yes No Suggest edit
Last updated on July 12, 2017

8.2.Types of Campaigns

 

Email Campaigns:   Email Campaigns use your corporate servers (or other configured email server) to send the selected templates directly via email to the User Set that you select for the Campaign. Email Only Campaigns are very useful in the following situations:

  • When you want to send a Jive link to a lot of people – even if they are not (yet) Users on your Jive site.  In effect, the email message acts as an invite to your Jive site since the recipient will not be able to view the link unless they register as a new user.  
  • When you want to communicate with people who have been invited, but haven’t yet registered as a new user either because they did not open the email, click on the link, or submit their profile.   Since these people are not yet Users on the Jive site, there is no easy way to communicate with them within Jive.
  • When you want to communicate with existing users who have not logged into Jive in a while.
  • When you want to communicate with Jive Users when your Jive instance is down.

Direct Message (DM) Campaigns: Direct Message Campaigns are designed to communicate with a specific User Set inside Jive.  These User Sets can be vertical (e.g.  all the members of a specific Social Group) or horizontal (e.g. all the Users who have been on your site for more than 6 months, or who all have a specific word in their Profile, or are the owners of certain content on your Jive instance).  DM Campaigns are part of the core functionality of InSite, giving you the ability to communicate with any set of your existing Jive Users – as long as they share a common characteristic in the User Profile.

Place Invite Campaigns:  Coming Soon

Community Invite CampaignComing Soon

Share CampaignComing Soon

 

Yes No Suggest edit
Last updated on July 12, 2017

8.3.All Campaigns Screen

The All Campaigns screen displays a list of your Campaigns that you have saved in InSite.  You can sort and filter your Campaigns, just as you can other screens of tabular data within InSite (for more information on how to use the filter/sort functionality, see General Screen Navigation).

The following columns are available in the All Campaigns screen:

  • Name
  • Type
  • State
  • Author
  • Template
  • User Set
  • Description
  • Campaign Approver
  • Disapproval Reason
  • Action
Yes No Suggest edit
Last updated on July 12, 2017

8.4.Cloning an Existing Campaign

Cloning an Existing Campaign

Cloning an Existing Campaign is an easy way to create a new campaign if you plan to use an existing Template and/or User Set for your new Campaign.  To Clone a campaign, find the campaign you want to clone from the All Campaigns Screen and select the Clone icon from the Action Column (the icon is two pages next to each other).  This will bring up the Clone Campaign pop-up which will allow you to view/change the Campaign Fields (see below) for your new Campaign.

Important Notes:  

  • You will need to change the name of the Cloned Campaign before saving.
  • If you Clone a campaign that has already been started, you will not be able to edit the Template of the newly-created campaign (this rule prevents Templates of completed campaigns from being altered).  In this case, you should Clone and rename the Template first, then Create a New Campaign, selecting the new template in the New Campaign pop-up (see below).
Yes No Suggest edit
Last updated on July 12, 2017

8.5.Creating a New Campaign

Creating a New Campaign

Currently, only Email and Direct Message Campaigns are supported.  To create a new Campaign, select the Campaign Type from the Campaign Menu.  Important Note:   When creating a new campaign, you should have also have your User Set and Template ready to go.  For more information, See Creating a New User Set and Creating a New Template / Cloning a New Template.

Yes No Suggest edit
Last updated on July 12, 2017

8.5.1.Campaign Fields

Campaign Fields

Complete the Campaign Fields in the pop-up below using the guidance text below.  Note:  The letters immediately after the field name correspond to the type of Campaign that the field appears on:  E=Email, DM=Direct Message.

  • Name (E, DM):  Just the name you give your Campaign.  Just make it something that is unique and will help you remember what the Campaign was about if you are looking it up a year from now.
  • Type (E, DM): Currently, there are two  different types of Campaigns in InSite: Email Campaigns and Direct Message Campaigns
  • Template (E, DM):  Use this drop-down to select the Template to use with this Campaign.  The Template must have already been created in order to be selected here.  See the TEMPLATES section of this document for more info on Templates.
  • User Set (E, DM):  Use this drop-down to select the User Set to use with this Campaign.  The User Set must have already been created in order to be selected here. Go to the USER SET section of this document for more information on the different types of User Sets and how to create or edit them.
  • Description (E, DM):  Use this field to clearly describe the purpose, audience, and intent of your Campaign..  The Description field is shown in the All Campaigns view, and can help you distinguish from among several similarly named Campaigns.
  • Send From (DM):  The Send From or Campaign Approver (CA) field in a Campaign was developed based on an understanding that the sender of a message is a major factor in determining whether that message is opened and/or read.   Many users will be more likely to open a message from someone in their community of practice/office/team than if it was sent by the Community Manager.  Therefore, this field allows you to specify a User’s name from whose account the direct message will be sent out (the message will only be sent after it is approved by that user).  When you click on the drop-down, you will notice that it does not list all Users – only some of them.  In order to allow a User to appear in the drop-down, they need to be designated as a Send From/Approver in InSite.  
    • Designating a Send From/Campaign Approver:  To designate someone as a Send From/Campaign Approver, go to the Data –>Jive Users screen and then make sure that the Edit column is displayed.  See the DATA MENU section for more info on displaying columns.Find the specific User you want to be the Send From/ Approver and then click the Edit icon (pencil) in the row for that User.  This will bring up a pop-up that only has one option currently – a check box next to Approver.  Check the box and click the Save button.  This User will now appear in the Send From/Approver drop-down in the New/Edit Campaign screen.

Once you have complete all of the fields, simply click the Create New Campaign or Update Campaign button.  This Campaign will now appear in the All Campaigns screen

Yes No Suggest edit
Last updated on July 12, 2017

8.5.2.Starting a Campaign

Running a Campaign

Once you have specified all the components of a Campaign ( Template, User Set and Send From/Campaign Approver User selected), you are ready to Start your Campaign.  To Start a Campaign, find the Campaign you wish to Start in the All Campaigns screen, scroll over to the Action column and click on the Start icon (play image).  

Yes No Suggest edit
Last updated on July 12, 2017

8.5.2.1.Starting an Email Campaign

Starting an Email Campaign

If you are starting an Email Campaign, InSite will prompt you to confirm your selection.  If you select, “Yes” the Campaign will be started and the recipients in your User Set will begin receiving emails based on your Email Template.

Yes No Suggest edit
Last updated on July 12, 2017

8.5.2.2.Starting a Direct Message Campaign

Starting a Direct Message Campaign

If you are Starting a Direct Message Campaign, InSite will send a DM to the Send From/Campaign Approver with a link this will send an InSite-specific DM to the Send From/Approver with an Approval Link in it.  When the Send From/Approver receives and opens the link in the DM, they will be taken a special InSite screen in which they can Review, Approve/Disapprove and Start the Campaign.  

From the Review/Approval screen, the Send From/Approver can review all of the components of the Campaign, including the Template and the list of participants in the User Set that the message will be sent to.  If the Send From/Approver is satisfied with the Template and the User Set, they can Approve the Campaign and execute it by entering their Jive credentials into the User ID (pre-filled) and Password fields provided at the bottom of the page, and then click the Approve button.  Important Note:  InSite only stores the Campaign Approver’s credentials long enough to send the messages to the participant list.  Once the Campaign has been completed, the credentials are deleted from InSite.  

Once a Campaign has been approved, InSite immediately begins to inject the message into your Jive instance and it will appear in the Jive inbox of the recipients.

Yes No Suggest edit
Last updated on July 12, 2017

9.InSite Reports Menu

The InSite Reports menu allows you to view your system Reports and Graphs.  Currently there are four Reports available in InSite (in addition to the Dashboard reports): Management, Content, Places and Influencer Reports.  Each of these reports, described below, shed light on different aspects of what is happening on your Jive instance.

 

Yes No Suggest edit
Last updated on July 12, 2017

9.1.Management Report

The Management Report displays the relationship between users who are managers and other users who are their direct reports.  It is another visual representation of the Organizational Chart contained in Jive.  Click on each of the nodes in the Management report to collapse the direct reports for that individual.  Clicking on the node again will expand the selection.

Yes No Suggest edit
Last updated on July 12, 2017

9.1.1.Managed User Graph

Below the Management Report is the Managed User Graph, which is a different visualization of the data contained in Management Report.   This outer ring of the graph displays the number of direct reports (regardless of level) each manager has.  The  inner ring displays the ratio of Jive users who have a manager recorded in the their profile to those who do not

Yes No Suggest edit
Last updated on July 12, 2017

9.2.Content Report

The Content Report displays a data visualization of Content Popularity by Views, Likes or Followers.  This visualization, called an area map, organizes Views/Likes/Followers categorically by color and size, allowing you to quickly gauge the most popular Jive objects.  Each content type is represented by a different color.  The size of each rectangle is in direct proportion to the number of Views/Likes/Followers the content items has relative to other content on your site.  To toggle between Views/Likes/Followers, click one of the radio buttons in the upper right of the screen.  To view the exact number of Views/Likes/Followers, simply click on an individual box within the chart and a popup will appear with the details.

Yes No Suggest edit
Last updated on July 12, 2017

9.3.Places Report

The Places Report is very similar to the Content report, except the visualization shows  the Views or Followers for Jive Places (Spaces, Social Groups, Projects, and Blogs).  The colors represent those four Place types.  To toggle between Views/Followers, click the appropriate radio button in the upper right of the screen.

Yes No Suggest edit
Last updated on July 12, 2017

10.InSite System Menu

The InSite System Menu allows you to change InSite parameters, pull interim data from your Jive instance and add or change your list of InSite Users.

 

Yes No Suggest edit
Last updated on July 12, 2017

10.1.Settings Submenu

The Settings Submenu contains the following screens:  Jive Settings, Email Settings, Campaign Approver, and Data Pull.

Yes No Suggest edit
Last updated on July 12, 2017

10.1.1.Jive Settings Screen

The Jive Settings Screen contains two sections:  Jive User Credentials and OAuth Credentials

Note: If you make any changes to this screen, please remember to scroll to the bottom of the entire page and click the Save button

Jive User Credentials Section

  • Login: Enter the Jive User ID of the API User you created for InSite.  This User must have permissions to view all Content and Places that you want to track and work with via InSite.
  • Password: The Jive Password of the above API Jive User.

OAuth Credentials Section

In order for InSite to be able to pull data from Jive’s Data Export Service (DES), you must generate an Advanced Analytics Add-on Client ID and Secret token, using the directions in the OAuth Credentials Section of the System/Settings/Jive Screen.  Once you have generated both items, simply copy them into the appropriate fields in the OAuth Credentials section of the Jive Settings Screen and click Save at the bottom of the screen.

Yes No Suggest edit
Last updated on July 12, 2017

10.1.2.Email Settings

NOTE: If you make any changes to this screen, please remember to scroll to the bottom of the entire page and click the Save button.

The Email Settings screen is where you define the parameters for the email server InSite will use for Email-Only Campaigns.  Typically, these parameters are associated with your corporate email server and can be obtained through your company’s IT department.  Tip:  Copy and paste the parameters below into an email that you can send to your IT department.  

  • Server: The outgoing address of the email server InSite will be using for Email Campaigns.
  • Port: The port on that email server that it will listen on.
  • Secure: Whether or not that connection to the email server needs to be secure (SSL) or not.
  • From: The email address that Email Campaigns will appear to be from.
  • Requires Authentication: If the email server you are connecting InSite to requires authentication via a User ID and password, checking this box will make those two fields appear below the checkbox.
  • User: The actual User ID of the email address on the email server that will send out the emails for an Email Campaign.  This is usually the same as the From field above.
  • Password: The password of the User ID on the email server.  Note: This is not a Jive User ID.
  • Test: Allows you to test if your InSite email settings are configured correctly without creating and sending a Campaign.  Enter the email address of the person you would like to receive a test email sent from InSite and click Test.  Once you confirm receipt of this email, make sure to click Save at the bottom of the screen to save your settings.

 

 

 

 

 

 

Yes No Suggest edit
Last updated on July 12, 2017

10.1.3.Campaign Approver Screen

NOTE: If you make any changes to this section, please remember to scroll to the bottom of the entire page and click the Save button.

The Campaign Approver Settings Screen allows you to define the settings of the Direct Message that  will be sent to a Campaign Approver when a CM launches a DM Campaign.

Send approval request by email: Check this box if you wish all approval requests for a DM Campaign to be sent to the Approver via Email (note:  Email-Only campaigns do not use Approvals Requests).  You can also send the request by DM – see below..

Send approval request as DM: Check this box if you wish all approval requests to be sent to the Approver via Direct Message (DM) inside your Jive instance.  Note:  If the Approver is a Jive User and has their Profile Preferences set to deliver DMs to their email inbox, the Approver will receive the approval request in both their Jive and email inboxes.

If both boxes are checked, the Approver will receive the Approval Request via both DM and email – regardless of how their Jive Profile Preferences are configured.  The Approver can use the link contained in either message to launch the campaign.

Campaign Approval Request Template (Subject and Body)

Below the checkboxes is the template for the Campaign Approval Request.  By default, InSite includes a template with boilerplate language, which,you can edit here if you choose.

The Campaign Approver Template area has two sections – the Subject line and the Body, just like other Templates in InSite.  Unlike other InSite templates, this template will only be sent to the Send From/Approver that you specified in your DM Campaign. Note:  Your DM Campaign will only be sent to it’s intended recipients after the Campaign Approver approves the Campaign.

Important Note:  The Approval Link field MUST be in the Template Body in order for the Campaign to be approved by the Approver.  .  The default Campaign Approver Template contains this field.  If this field gets deleted, you must add it back in by selecting INSERT menu in the Template Command Bar.  

If you make modifications to this menu, make sure to save your settings by clicking the Save button at the bottom of the screen.

 

 

Yes No Suggest edit
Last updated on July 12, 2017

10.1.4.Configure Data Pull Screen

NOTE: If you make any changes to the sections below, please remember to scroll to the bottom of the entire page and click the Save button.

Data Pull Schedule and Speed Section

Data Pull Speed: Select Slow Medium or High –  This drop down menu allows you to change the speed by which InSite pulls data from your Jive Instance.  Depending on the number of users who are logged into your Jive Instance and the size of your user base, there may be an impact to performance for the logged in users.  Tip:  Consider observing the potential performance impact directly by browsing the site during the data pull.  If there is a noticeable performance impact, try setting the Data Pull Speed to the next slowest setting.  You can choose between Ridiculous, Slower, Slow, Normal, Fast, and Faster.

Pull Data Every:  This field allows you to specify how often the Jive data is updated.  Use the first and second fields to specify the number of Hours/Days/Weeks/Months between data pulls.  Tip:    In general, we suggest specifying a time frame of no less than once a day, and no more than once an hour.

Start First Pull:  Specify the date/time (expressed as Coordinated Universal Time – UTC, which is usually the same as Greenwich Mean Time – GMT) that InSite pulls Jive data from your Jive Instance via the APIs.  Note:  Because the first data pull can be  an enormous amount of data, it make take  anywhere between 1 and 6 hours to complete..

Data Pull Scope Section

This section allows you to configure which data InSite should pull from your Jive instance. Potential selections under the Data Pull Scope include:

  • Google Analytics – Coming Soon
  • DES (Data Export Service) – Currently the only selection under the DES is DES Basic Data Set.  The Basic Data Set is a subset of the complete data available via the DES.  The entire DES data set is extremely large and the Basic Data Set will give you some useful data immediately without needing to pull the entire set.  The Basic Data Set includes fields such as Last Login Date – which is available via the Jive Users Screen in InSite.  Select this data set by checking the box directly to the left.  Note:  Ensure that you have configured the OAuth Configuration Section of the Jive Configuration settings screen.
  • Jive (Rest APIs) – This data set includes many fields associated with Jive Contents, Invites, Places and Users.  You can select these data subsets by individually checking the boxes next to the data item.
Yes No Suggest edit
Last updated on December 2, 2017

10.1.5.Security Screen

The Security screen is new in InSite 0.8.4.  It is where the InSite Administrator (IA) can configure the security settings for all InSite users.  To get to the Security screen click on the System menu icon> Then Settings> Then Security.

 

The Security screen is divided into two sections: Password Complexity and User Login and Session

Yes No Suggest edit
Last updated on December 2, 2017

10.1.5.1.Password Complexity Screen

Password Complexity Screen: The top half of the new security screen has to do with the rules InSite will enforce for creating passwords for users.

Check the boxes that you wish InSite to enforce when creating a password for a user:

  1. Require lowercase letter – If checked, will require that there be AT LEAST one lowercase letter in the final password construction.
  2. Require uppercase letter – If checked, will require that there be AT LEAST one uppercase letter in the final password construction.
  3. Require a number – If checked, will require that there be AT LEAST one number in the final password construction.
  4. Require a special character – If checked, will require that there be AT LEAST one special character (!@#$%, etc.) in the final password construction.
  5. Require to not be the same as the login ID – If checked, will require that the password cannot be the same as the user”s user ID on InSite.  So if my User ID was “btaub”  my password could not be “btaub”.  This option is checked by default.
  6. Minimum password complexity – There are five choices in the dropdown menu:
    Too guessable: risky password –
    Very guessable: protection from throttled online attacks
    Somewhat guessable: protection from unthrottled online attacks
    Safely unguessable: moderate protection from offline slowhash scenario
    Very unguessable: strong protection from offline slow hash scenario
    This setting bears some detailed explanation.  These selections represent a second set of password construction gates – over and above the other settings in this section.  The selection you choose here is completely independent of your other selections in this section.  Each pick from the drop-down menu enforces an increasing level of complexity on password that make them harder to crack in a brute-force attack.  A brute-force attack is one where the hacker has an automated tool that starts with “00000000” and then tries “00000001” and keeps going through “ZZZZZZZZZ” and then the special characters and so on.  Obviously, those tools try the easiest ones first (“password”, etc.)This section uses a library that uses a combination of a dictionary of known words (e.g. “password”, “Welcome1”) and a construction algorithm that analyzes the password for things like how close the key are together on the keyboard. So, while “qwerty” is not a real word, the keys are in a row next to each other on a keyboard and could be guessed in milliseconds during a brute-force attack.

    So each of the five selections represent passwords construction that will each take longer to crack than the selection before it.  If you pick “Too guessable” a hacker could brute-force this password in less than a second.  The highest selection would take years of machine time to crack and is by far, the best protection from a brute-force attack.  These passwords are usually VERY long, not real words and are essentially a string of random letters and characters.

    Pick Approx. # of Tries to Hack
    Too guessable: risky password < 1,000
    Very guessable: protection from throttled online attacks < 1,000,000
    Somewhat guessable: protection from unthrottled online attacks <100,000,000
    Safely unguessable: moderate protection from offline, slow-hash scenario < 10,000,000,000
    Very unguessable: strong protection from offline slow-hash scenario >= 10,000,000,000

    So, the intent with this selection is to slow a hacker running a brute-force attack down – giving us and you a better chance to detect the intrusion and shut it down.

    Again, this selection is independent of your picks on the other options above and below it.  So you may create a password that has no real words, is 18 characters long and is basically a string of random letters numbers and characters – and if you have chosen the highest level of this setting – you password may still not pass this gate and you will be alerted that the password needs to be even harder to crack.

    So we recommend a balance of security and practicality.  Depending on the sensitivity of your Jive data, you may want to choose one of the middle level for this pick.  Too little security and you are asking for trouble these days.  Too much and the system can become unusable.  Use common sense and your organizations overall posture and policies for these things and set it up accordingly.

  7. Minimum password length – If set to anything other than 0, will enforce the rule that passwords cannot be shorter than the entered number of characters.  Setting it to 0 will not enforce any minimum password length.  Realistically, this should never be less that 8, and 12 is much more secure.
  8. Save after any changes to the above section.
Yes No Suggest edit
Last updated on December 23, 2017

10.1.5.2.User Login and Session Screen

User Login and Session Section:  This section lets you control other aspects of security that are not related to Password Complexity.

  1. Locking user account after specified number of failed attempts to login (NOTE: Only the InSite Administrator (IA) can change or reset the password of a locked-out user and re-enable their account)
  2. Notify the specified InSite security administrator, via email, that a specific InSite user is locked out of their account due to exceeding the configured number of failed login attempts.
  3. Specify the email address of the InSite Security Administrator.
  4. User logout after specified period of inactivity – in minutes (NOTE: Once configured in the InSite Admin Console, the parameter only takes effect after new login by an InSite user)
  5. Save after any changes to the above section.
Yes No Suggest edit
Last updated on December 2, 2017

10.2.Pull Data Screen

The Pull Data Screen allows you to pull the most recent data from your Jive Instance – outside of your regularly scheduled pulls.  InSite regularly polls Jive for the most recent data based on the Pull Data Every field defined above, however sometimes you need the data updated immediately.  The Pull Data function allows you to force an immediate pull to update InSIte data regardless of  the normal pulling intervals specified in the Settings screen.

IMPORTANT NOTE:  The API calls that InSite uses to both extract and inject data into and out of Jive can impact system performance if run too frequently.  You should only use the Pull Data function when you have specific data that you need updated now and cannot wait until the next scheduled data pull.

IMPORTANT NOTE FOR JIVE-X CUSTOMERS: Under the terms of the license agreement for Jive-X, Jive license fee charges are based on the total number of monthly page views.  This is in contrast to Jive-N customers, in which Jive licence fees are calulated based on the number of registered Jive users.  For Jive-X Jive “charges” 1/6 of a Pageview for every API call.  Due to the way the APIs are architected the data pulls by InSite can add up to A LOT of pageviews – sometimes meeting or even exceeding user pageviews on a monthly basis.  Jive provides you as a customer with a monthly report of pageviews on your Jive installation.  This report issued monthly by jive shows the split between user-generated page views and API-generated page views so you will be able to see the effect of InSite API data calls on a monthly basis.

Yes No Suggest edit
Last updated on July 12, 2017

10.3.Users and Permissions

The Users and Permissions Submenu contains settings related to the InSite Users and Roles Screens.

Yes No Suggest edit
Last updated on July 12, 2017

10.3.1.InSite Users Screen

The InSite Users Screen allows you to add, remove or change Users to your InSite system.  Please note that the InSite Users added in this section are NOT Jive Users.

Create New System User – Click on the “Create New System User” button, which will bring up the New User pop-up.  Please note that all the fields are required, including a second field under Password in which you have to retype the password.  The last field is the Role drop-down.  For an explanation of the roles, please see the next section.

Changing an InSite User’s Role – To change the Role of an existing InSite User, click on the Edit icon (pencil) at the far right “Action” column for any users listed in the table.  Next, click on the Role field and select the new Role for the user.  Then click the “Update User” button in the lower right of the pop-up.

 

Yes No Suggest edit
Last updated on July 12, 2017

10.3.2.Roles Screen

This Screen allows you to view the specific functions that each InSIte User Role can fulfill within InSite.   

Each new InSite User must be assigned a Role.  By default, your initial InSite user is assigned the Role of Administrator.  Each InSite instance much have at least one user with the Role of Administrator.   For a complete description of the functions available for each role, see below.

Note:  At this time, the specific functions of each User Role are predefined and cannot be edited.  

Tip: While you are creating new InSite Users, open this matrix in another tab in your browser and use it as a quick reference when defining the Role for the new user.   

InSite Predefined User Roles

The following Roles are currently available in InSite:

  • Developer
  • Administrator
  • Campaign Launcher
  • Campaign Creator
  • Data Explorer
  • Report Viewer
  • User

Developer – This role is reserved for InSite Support staff and allows users with this Role to perform all of the functions of the Administrator Role plus the abilities to develop the product and manage Actions.

CAN CANNOT
Develop Product
Manage Users
Manage Settings
Launch Campaigns
Manage Campaigns
Access Raw Data
Manage Custom Views
View Reports
Manage Actions
Get Help
*None

Administrator – This Role allows a user at perform all of the day-to-day management tasks for the InSite instance – including managing InSite Users and System settings and configuration parameters.  The Administrator Role is the only one (other than Developer) that has access to the functions under the System menu (This menu will not display for users with any other permissions).

CAN

CANNOT
Manage Users
Manage Settings
Launch Campaigns
Manage Campaigns
Access Raw Data
Manage Custom Views
View Reports
Get Help

Develop Product

Manage Actions

Campaign Launcher – The Campaign Launcher Role is specifically designed to allow a user to perform all Campaign functions – including create, edit, delete and launch campaigns created by themselves or other users.  This Role allows for the separation of Campaign creation and setup functions (see Campaign Creator Role) from the ability to launch those campaigns.

CAN

CANNOT
Launch Campaigns
Manage Campaigns
Access Raw Data
Manage Custom Views
View Reports
Get Help

Develop Product

Manage Users

Manage Settings

Manage Actions

Campaign Creator – The Campaign Creator Role is designed to allow users with this Role to create and edit unlaunched Campaigns – but not to launch them.  Campaigns created by users with this Role must send a Campaign Approval Request to another user with the Role of Campaign Launcher or above to actually execute or launch the Campaign.  The roles of creating and editing a Campaign has been intentionally separated from the Role of launching the Campaign.  This separation acts as an additional review and approval step for Campaigns, especially ones that impact large numbers of users.

CAN

CANNOT
Manage Campaigns
Access Raw Data
Manage Custom Views
View Reports
Get Help

Develop Product
Manage Users
Manage Settings
Launch Campaigns
Manage Actions

Data Explorer – The Data Explorer Role is designed for an InSite User that is generally not involved in the Campaign creation or launch process, but is instead involved in the creation, edits or deletion of Custom Views, or the Reports, Charts, Graphs or Dashboards associated with the Custom Views.

Data Explorers can also view the raw Jive data available under the Data menu.

CAN

CANNOT

Access Raw Data

Manage Custom Views

View Reports

Get Help

Develop Product
Manage Users
Manage Settings
Launch Campaigns
Manage Campaigns
Manage Actions

 

Report Viewer– A user with the Report Viewer Role can only view Reports, Charts, Graphs, or Dashboards created via the Custom Views functionality available to users with the Data Explorer Role or above.  Report Viewers cannot see raw Jive data, nor create or edit the underlying Custom Views used to generate the Reports they have access to.  Managing access to individual Reports is handled within the Custom View used to generate the Report.

CAN

CANNOT

View Reports

Get Help

Develop Product
Manage Users
Manage Settings
Launch Campaigns
Manage Campaigns
Access Raw Data
Manage Custom Views
Manage Actions


User
– A user with the User Role in InSite cannot do anything except access functions under the Help menu within InSite.  The role is here primarily so that a user can read InSite documentation and report bugs.  

CAN

CANNOT
Get Help

Develop Product
Manage Users
Manage Settings
Launch Campaigns
Manage Campaigns
Access Raw Data
Manage Custom Views
View Reports
Manage Actions

 

Yes No Suggest edit
Last updated on July 12, 2017

10.4.Voice Command

Coming Soon!

Yes No Suggest edit
Last updated on July 12, 2017

10.5.Full Screen

Clicking on the Full Screen menu selection switches InSite into fullscreen mode.  Press “Esc” on your keyboard to exit Full Screen mode.

Yes No Suggest edit
Last updated on July 12, 2017

10.6.Logout

Use the Logout selection to log out of InSite.  You should always logout of InSite when ending a session for security reasons.

Yes No Suggest edit
Last updated on July 12, 2017

11.InSite Help Menu

The Help menu allows you to review the Current InSite Documentation (this document), report a bug discovered in InSite, and view the InSite Release History.

 

Yes No Suggest edit
Last updated on July 12, 2017

11.1.Help Documentation

Clicking on Help under the InSite Help Menu displays the Documentation for the current release.  To navigate in the Help menu displays this document.  Use the sidebar on the left to browse the different help topics.  Clicking on the small arrow next to a help topic will expand the subtopics available under that topic.  Use the search bar at the top of the screen to search for a particular topic or Control-F in your browser to search for specific terms throughout the text.  

Yes No Suggest edit
Last updated on July 12, 2017

11.2.Report a Bug

Clicking on the “Report a Bug” menu item will open a pop-up that will allow you to enter details about the bug you discovered or the issue you want to discuss with Support.  Give your problem or question a title/summary subject and a more detailed description of the issue, including when and how the problem arose.

Once you submit the Bug Report by clicking the button at the bottom of the form,  Insite Support will be in touch (usually within one business day) with either a solution or an acknowledgement that you have found a bug and our timeframe for fixing it.

Yes No Suggest edit
Last updated on July 12, 2017

11.3.Release History

New versions of InSite are released in Continuous Deployment – which means that we add features and release new versions on an ongoing basis. Please note that all InSite customers will always be on exactly the same version (or Build).

The Release History can be viewed by either going to the Help tab and then clicking on the Release History menu selection, or by clicking on the version number in the top left corner of the screen – next to the InSite logo from any screen in InSite.

Yes No Suggest edit
Last updated on December 23, 2017
Help Guide Powered by Documentor
Suggest Edit
*Begin insert of AgileCRM Analytics code script *End insert of AgileCRM Analytics code script