July 6th 2016

StoryPulsePlanned Scope for Server Version 3.2.0

Disclaimer....................................................................................................................3

Purpose........................................................................................................................4

Planned Scope..............................................................................................................4

Consent Forms.............................................................................................................5Ability to upload consent forms using the Administrator User Interface...............................5

Notes...........................................................................................................................6

Disclaimer

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of FocalCXM. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside without prior written consent of FocalCXM. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of FocalCXM. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.

Purpose

This document provides an overview of the strategic product plans for StoryPulse and related options from FocalCXM. It is intended solely to help StoryPulse customers understand the value proposition in upcoming releases.

Planned Scope

As of June 2016, the version of StoryPulse available in the market is 3.1.0. This document highlights the key areas of innovation planned for StoryPulse server and iPad version 3.2.0 as described below.

Consent Forms

Consent Forms

Ability to upload consent forms using the Administrator User Interface

With 3.2.0, StoryPulse administrator can upload consent forms, push them to the client, capture input, signatures and synchronize the information into the CRM platform. While 3.2.0 is in QA, this version does not require any client side changes. Hence version 3.1.0 of the StoryPulse client (iPad) will work seamlessly with version 3.2.0 of the server. The following are the key stories in Development/QA.

Server 3.2.0

Id Title12072355

1 Consent Form: Ability to push attachment to CRMOD

120963091

Consent Form: If the assessment is of type form, then, the server should create a pdf document with the merge fields, signature and add the attachment to the contact in CRMOD.

121339989

Consent Form: Whenever the consent form is uploaded at the contact level, then an Activity has to be created.

122969591

Consent form - Admin should have ability to set a flag on the console to upload consent form to CRMOD as a PDF attachment.

122619201 Server - Add language files in the application.

12134941 Server should send the extension of the form type of

9 assessment to the client {HTML,ZIP}. This will help the client in rendering the form properly

124106891

Server - If a consent form PDF could not be generated because of any exceptions in PDF generation, activity object in the SP should have that logged in the PDF generation status.

121340107

The server should create an activity every-time the consent form is updated.

123742411 Consent from is not creating, when upload a zip file.

124728851

Server - Add likert with number, range, percentages in the basic assessment.

118424235 Ensure that SP Admin is 508 compliant.

115583423

If enter 150 characters for option it is going out of question window

Notes

Version 3.1.0 of the client (iPad) has all consent related functionality included. Consent form in iPad build # 3.1 – – If any existing user wants to get the consent forms the app has to be installed again. Reloading assessments is not downloading the attachments in the # 3.1 version. This was identified in recent testing.