Being ethical in a sometimes unethical world...- Branson SharePointalooza September 13th, 2014

Thomas DuffCambia Health SolutionsSeptember 12th – 13th, 2014

Tracking Ethical Conflicts in a Sometimes Unethical World

2 | SharePointalooza – Branson, MO 2014

Who am I?

Thomas Duff, aka “Duffbert” Technologist, blogger, writer,

speaker, SharePoint developer 20+ years with Microsoft and

IBM collaboration technologies Email: [email protected] Twitter: @duffbert Blog: sharepointduffbert.com


Rock Star Sponsors

Performer Sponsors

Giveaway Sponsors

Soloist Sponsors

Thank you, sponsors!


Download the attendee packet at http://bit.ly/SPAloozaAttendee

Attend the “Rock Star” Sessions at the end of each day for fun, raffle prizes, wrist bands for concert access, and your chance to win a Surface Pro 3

Attend Nintex’s Brown Bag lunch Friday and Saturday (lunch provided for first 100 people)

Tweet about the event using #SharePointalooza

Thank our sponsors Have a great time!

A Few Reminders

http://bit.ly/SPAloozaAttendee


What better way to unwind after a long day of working out your brain than with some great live music at the amazing outdoor stage at Branson Landing! The bands will be playing both Friday and Saturday night from 6:30 pm to 10 pm.

The Bands


Outline

Why use SharePoint to track this information? Why are Ethics programs necessary – my story How we got from there to here Under the Conflict of Interest form covers Questions?


Why use SharePoint to track this information?

No-code solution – easy to maintain Easy to build forms – Customize Form with

InfoPath Easy to administer – for both SharePoint

Support and the customer/site owner Workflows can trigger notices and set

permissions These are techniques you can use to build any

type of electronic form and workflow solutions


Why are Ethics programs necessary? My story…


How we got from there to here… from Notes…

• Started Conflict of Interest tracking application in 2002

• Tracking for 5000+ people (employees and contractors)

• Used Lotus Notes (our main collaboration tool through 2009)

• Surprisingly, many of the benefits of this type of form existed both then in Notes and now in SharePoint


How we got from there to here… to InfoPath…

• Switched to SharePoint using InfoPath forms in 2010

• It worked, but we were learning as we went along

• There were… issues

• InfoPath client support

• Submissions would disappear

• Workflows couldn’t update information in the XML document

• Cumbersome to work with administratively


How we got from there to here… to Customized Lists

• Made some major changes for 2014, so decided to go with a SharePoint Customized List

• Major improvements in stability and support

• Browser support

• No reliance on InfoPath client

• Full access to update fields via SPD workflows

• “It just works”


The Form…

Customizing the list item form using Customize Form With InfoPath


A series of 14 questions to flag conflicts

• Covers areas such as:

• Connections with providers, vendors, other plans, or customers

• Received gifts/gratuities (you and/or family) or honorariums

• Other employment

• Family members employed at the company

• Other relationships

• Convictions, disbarments, and license revocations


Behind the scenes… for the Ethics officers

Using hidden sections, information gathered by the Ethics officer is stored


Behind the scenes… for the form data

To track changes that a person makes on the form in a specific session, we store the current information on Form Load


The employee number triggers the profile load

When a person creates or edits a COI, we run a routine to update information based on their user profile


The profile load – how it’s done…

To accomplish the profile load, we set up a rule that will call the GetUserProfileByName web service and fill in the form fields with the values from that call



Start by clicking the Manage Data Connections under the list of fields, and then click Add to create a new data connection:



The data connection will be one that receives data (in this case, from the SharePoint profile for the employee)



We’ll be using one of the SOAP web services that is built into SharePoint



To find the list of web services, enter the URL for the WSDL file

http://<yourSite>/_vti_bin/userprofileservice.asmx?wsdl



For this particular form, we want to use GetUserProfileByName as we have the account name (the employee number) as the key to the profile.



On this screen, we leave the value blank, as we will provide the value at the time we call the web service with the data connection



These are the two final screens, which can be taken with default values. Once that’s done, the new data connection for the web service is finished



Once we have the data connection in place, we have to set the fields in the form based on values in the profiles



We start by adding an action to our rule – “Set a field’s value”



Choose the form field name, click on the fx for the field value, click on Insert Field or Group, and then use the Advanced View to show the GetUserProfileByName data connection fields



Within the data connection, click on Value. To filter the data returned in Value, use the Filter Data box to select a filter condition…



Since we’re looking for a single property in the data connection record, we filter on the name of the property (in this case, Title)



Once that’s done, you now have the value of the Title field in the SharePoint profile loaded into the Employee Title field in the form:



Side note… if you want to “code that directly instead of working through all the panels, you can select the Edit XPath (advanced) option and do the following:


The questions start next… looking for “Yes” or “No”

In the case of a “No” answer, not much changes


“Yes” answers trigger more questions

If a “Yes” answer is given, then a hidden section reveals two required fields asking for detail and how that is different than last year’s disclosure


This is done via a formatting rule…

If a “Yes” answer is given, then a hidden section reveals two required fields asking for detail and how that is different than last year’s disclosure:


The rules for when the form loads

The Form Load rules set up the new data for the user, as well as storing existing data for comparison purposes on Form Submit


We grab all the existing comments on the form

The critical part is storing the existing comments on the form so we can change for changes on Form Submit


When the form submits, more rules

If there’s at least one “Yes” answer on the form, we set a flag so that the Ethics officer can follow up for investigation


Clean up of detail fields if the answers were “No”

Housekeeping – make sure that if an answer was set to “No”, that there are no residual comments on the question from prior “Yes” answer


If a Yes/No answer changes, get that information

For each Yes/No answer change, track what it was changed to, as well as what the comment was on Form Load:


The Changed Entries field gathers those changes

The Changed Entries field is stored on the form so the Ethics officer can review what was changed


The Changed Entries field gathers those changes

This is an example of what would be loaded into the Changed Entries field for changes I made:


SharePoint Designer And Workflows


Workflow Impersonation – a WONDERFUL thing


Workflow Impersonation – a WONDERFUL thing

Because people should only be able to see their own COI, it’s important to give each COI unique permissions. This is done via an impersonation step in a workflow built in SharePoint Designer:


Drilling down to add and/or remove permissionsA drill-down into removing/adding permissions:


An alternative way to set the permissions

We could have also done permissions this way, but the prior method allows us flexibility if we ever wanted to make specific items visible to supervisors or managers:


Emails triggered after saves…Letting the user know there will be a review due to one “Yes” answer:


Emails triggered after saves…

Letting the user know a more thorough review is needed after preliminary review:


Emails triggered after saves…Initial notice to let people know they need to complete the conflict statement:


Emails triggered after saves…Initial notice to let people know everything is fine and no further action is required:


Adding icons on the workflow dropdowns…

Cool Tip… you can add workflows (and icons) to the list item dropdown menus:

These are added to the list in SharePoint Designer under Custom Actions:


Adding icons on the workflow dropdowns…

Adding a custom action allows you to assign a workflow to the action, as well as an icon to the custom action menu entry


Bonus Tip! Sending ad-hoc emails on an item…

This is a nice ad-hoc email workflow you can attach to any list:



It uses the Initiation Form (and parameters) as well as local variables:



The Initiation Form parameters supply the To/CC/email body fields. The local variables supply some of the standard email body text:


Bonus Tip! Sending ad-hoc emails on an item…Very simple Initiation Form design… almost the default:



The Send Email action in the workflow:



When the workflow is initiated, this is what the user sees:



This is what the email looks like when it arrives:


Questions?

Thank you, and enjoy the conference!

Date post:	20-Aug-2015
Category:	Data & Analytics
Upload:	thomas-duff
View:	221 times
Download:	0 times

Being ethical in a sometimes unethical world...- Branson SharePointalooza September 13th, 2014

Data & Analytics