1. Launch the SharePoint Designer application (this is typically installed as a separate application, but grouped with Microsoft Office).
2. Open the SharePoint site where you want to create the custom workflow. 3. Click File > New > Workflow.
4. Decide whether your workflow is going to be associated to a single SharePoint document library, or whether it can be reused and associated to multiple document libraries or a content type. The sections below describe each option.
• Creating a Workflow that is Associated to a Single SharePoint Document Library
a. Click List Workflow, then choose a document library in your site to associate your
workflow to the document library.
b. Under Add a new workflow to your list, enter the name for the workflow. You can optionally enter a description.
c. Build the workflow with as many steps as you like. In one step, add the Copy Document to Jive Action.
1. Click Action > Copy Document to Jive.
2. Specify the action properties. You will need to change the Jive Instance Name to what is defined in central administration (an administrator may need to help you or you can use one of the web parts to show you the instance name in the web part properties). You also must select the Jive Place Type (space, project, group) and type the name of the Jive place to copy the document.
d. Click Publish to save your workflow and publish it to the chosen SharePoint document library.
• Creating a Reusable Workflow a. Click Reusable Workflow.
b. In the Create Reusable Workflow dialog box, under Add a new reusable workflow to your site, enter a name for your workflow and choose a content type (you can optionally add a description). The content type should be Document or some content type that inherits from Document (the Copy to Jive action does not work for list items). c. Build the workflow with as many steps as you like. In one step, add the Copy Document
to Jive Action.
1. Click Action > Copy Document to Jive.
2. Specify the action properties. You will need to change the Jive Instance Name to what is defined in central administration (an administrator may need to help you or you can use one of the web parts to show you the instance name in the web part properties). You also must select the Jive Place Type (space, project, group) and type the name of the Jive place to copy the document.
d. Click Publish to save your workflow and publish it to SharePoint.
e. Associate your workflow to a content type or a list. This will take you into the SharePoint UI and let you perform the association.
Working Around Browser Caching
Jive for SharePoint uses the following file types: XSL, XML, HTM, and CSS. Files of these types are cached by client browsers unless browser caching is disabled (see Farm Configuration for Jive (page 49) ). Browser caching generally improves performance because the client need not submit a request or download files which do not frequently change. However, it can be a nuisance when you're changing files on the SharePoint file system such as CSS, XSL, or XML files. In this case it will be necessary to clear the browser cache and issue a full refresh (CTRL-F5).
Steps required to successfully clear the browser cache sufficient to force download of these files varies by browser and version.
Enabling and Viewing SharePoint Tracing
Enabling Tracing on the Client Browser
Some basic client browser level tracing is available from the SharePoint application. To enable, append the following to your current browser location (URL) query string.
?JiveDebug=true
Example: http://sharepointurl?JiveDebug=true
Note: Please note the uppercase "J" and "D" in JiveDebug. The value for JiveDebug is case sensitive. The following screen shot shows a sample of the client tracing output.
Note: You will not immediately see the trace output on the screen. Make sure to scroll beyond the normal screen presentation and you will see the trace output.
Enabling Tracing on the SharePoint Server
To enable tracing on the SharePoint server see the Farm Configuration for Jive (page 49) . You must perform an IISRESET on SharePoint after changing this setting for the setting to take effect. In addition, this must be done on every SharePoint web front end to enable tracing for all SharePoint activity within the connector.
Viewing Trace Output
There are two techniques to view tracing output: • Looking in the SharePoint ULS logs
• Using DebugView
Viewing Output in the SharePoint ULS Logs
The SharePoint ULS logs are, by default, in a directory such as "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\LOGS" on the SharePoint server, but this is defined in Central
Administration (Operations -> Diagnostics Logging). Go to that directory and find the file with the latest update timestamp. You may need to wait a few seconds for the latest updates to show up.
Open the file with the latest changes, go to the bottom, and start looking for anything with "[Jive.SharePoint.Tracing]" in it.
Viewing Output with DebugView
DebugView is a tool that will let you watch real-time tracing. You can download DebugView, run it on the SharePoint server, and simply watch for trace messages to appear. You may want to set a filter (Edit -> Filter/Highlight) to "[Jive.SharePoint.Tracing]" to only get Jive SharePoint trace messages. You may also need to capture Win32 message (Capture -> Win32 and/or Capture -> Global Win32).
Note: DebugView has been known to not work in Windows Server 2008 under some configurations.
Setting up Jive
Jive Connects for Microsoft SharePoint provides tight integration between SharePoint and Jive. It takes SharePoint’s strengths as a content repository with complex workflows and document management and
This section covers the features within Jive and is intended for Jive IT administrators. It begins with the technical installation and configuration of the Jive features, followed by more technical concepts around the Jive features.
To learn more about the features within SharePoint, see Managing the SharePoint Features (page 36) . > Important: Before you begin, refer to the Read Me (page 3) , which helps you prepare for
configuring Jive and SharePoint. Authentication Scenarios (page 84) describes two authentication scenarios used to demonstrate the integration between SharePoint and Jive. These scenarios provide some extra guidance and may help relate to your requirements.