Release 8 Features (Proposed)

Coordinator
Apr 24, 2008 at 2:27 AM
Edited Apr 25, 2008 at 3:51 AM
Response Integration – Template Wizard
Problem Statement: The current templates in the Developer Portal do not match the CMS system, and they cannot preview the request from the Dev portal.
Desired Change: Allow users to go through a wizard to help select a template.
Need a template category.
Considerations:

Common questions:
  1. Is there a downloadable file that fixes this issue?
  2. Does this fix multiple versions of your application? (Bandicoot)
  3. Would you like to be notified when this response is published?

Response Integration – Workflow
Problem Statement: The current system used for responses is disconnected from the Developer Portal. The two systems independently manage responses.
Desired Change: Stream line the workflow including the approval process. Ensure that Data is traceable easily between the two systems.
Considerations:

current workflow has these steps:
  1. Customer creates a Response request on the Developer Portal website
  2. A report is generated showing all Response requests
  3. A person verifies that the Responses quality
  4. A Response is approved
  5. The response is entered into a separate system using copy/paste
  6. The Response content management system (CMS) system generates an Solution ID (SID)
  7. The Response is published.

The new workflow:
  1. Customer creates a Response request on the Developer Portal
  2. The Developer Portal sends the Request to an approval queue
  3. A notification email is sent to the specified approvers
  4. Approvers review for quality
  5. Approvers Approve
  6. Response is published to Response cms
  7. Response ID is stored in Developer Portal

Response Integration – Metrics/Feedback
Problem Statement: Currently all the Response metric information is not exposed to customers through the Developer Portal website
Desired Change: Expose the Satisfaction metrics for Responses on the Developer Portal, allow end-user comments to be view.

Response Integration – Dynamic Survey Creation
Problem Statement: Ability to have more than just simple Yes, No, Somewhat response.
Desired Change: Allow for response submitters to specify custom questions to ask their users.

Response Integration – Third Party Branding
Problem Statement: Responses don’t have a visual presence for third party vendors. A simple company name is displayed in responses but no logo’s.
Desired Change: Display a company logo within their response.

Data Subscriptions – AdHoc
Problem Statement: Users do not have a method where alerts are pushed to them. Currently they need to log into the Developer portal and search for issues.
Desired Change: Create an event driven data subscription that pushes information to Dev Portal Users.

Data Subscriptions – Scheduled
Problem Statement: Users do not have a method where alerts are pushed to them. Currently they need to log into the Developer portal and search for issues.
Desired Change: This subscription model needs to support set interval reporting, so users can setup reports to be sent out on a scheduled basis