Summary
There has been a lot of movement surrounding Perceptive Experience/Evolution/Everywhere. Questions still remain as to how the documentation will ultimately be delivered/accessed by users. However, those are decisions that are not fully under the control of the PK department as they involve development work. The purpose of this project plan is to ensure that customers can access the documentation in a logical way that alleviates (dare I say eliminates??) confusion.
Problem
Initially, I looked at Evolution/Experience in a different way. The implementation is far more expansive that I feel our current TFS structure allows. I think there is a need to differentiate between the different “parts” of Experience...like the back end, the Content modules, and the apps.
This organization will impact our documentation website as well as our source control.
Current TFS structure
Evolution
Annotations_Library
1.0.x_enUS
AP Approvals
1.0.x_enUS
AP Approvals Connector
1.0.x_enUS
BatchCapture Module
1.0.x_en_US
Checklist Capture Module
1.0.x_en_US
Common Modules
1.0.x_en_US
Documents Module
1.0.x_en_US
File Conversion Service
1.0.x_en_US
Forms Library
1.0.x_en_US
Framework Admin
1.0.x_en_US
Framework API
1.0.x_en_US
Identity Management
x.x.x_en_US
Interact Salesforce
2.0.x_en_US
2.1.x_en_US
Organizer Module
1.0.x_en_US
Process Designer
1.0.x_en_US
Process Manager
1.0.x_en_US
Process Runtime Module
1.0.x_en_US
Scan Module
1.0.x_en_US
Search Library
1.0.x_en_US
Shells
Desktop
1.0.x_en_US
Installation
Mobile
1.0.x_en_US
Web
1.0.x_en_US
Tasks Module
1.0.x_en_US
Tech Specs
Update Module
1.0.x_en_US
Viewer Library
1.0.x_en_US
Workflow Module
1.0.x_en_US
Workplace
x.x.x_en_US
Proposed restructuring:
Experience_Admin
Framework
x.x.x_en_US
API
Admin
Installation
x.x.x_en_US
Shell_Mobile
x.x.x_en_US
Shell_Desktop
x.x.x_en_US
Shell_Web
x.x.x_en_US
Tech Specs
Experience_Content (Experience_Core)?
Annotations
x.x.x_en_US
Batch Capture
x.x.x_en_US
Common
x.x.x_en_US
Documents
x.x.x_en_US
Forms
x.x.x_en_US
Organizer
x.x.x_en_US
Scan
x.x.x_en_US
Search
x.x.x_en_US
Tasks
x.x.x_en_US
Update
x.x.x_en_US
Viewer
x.x.x_en_US
AP Approvals
AP Approvals Connector
Checklist Capture
File Conversion Service
Identity Management
Interact Salesforce
Process Designer
Process Manager
Process Runtime
Workplace
Impact
With this restructuring, it would affect the different product URLs in the following ways.
- The stand alone products would be listed in the Product Index on our website.
- The stand alone products would have their own product pages in the portal.
- The Experience_Content modules would eventually be listed on an Work with Experience landing page
- The Experience_Admin information would be accessed from a Manage Experience landing page
- The Experience product page in the portal would link to:
- Tech Specs
- Manage Experience -> this points to a Manage Experience landing page (similar to the Manage Content landing page)
- Work with Experience -> this points to the Work with Experience landing page (similar to the Work with Content landing page)
Next steps
- Communicate the restructuring to the PK team - email and post on Innovate (Sarah - 1 day)
- Move folders in TFS - (Sarah - 1 day)
- Move/update Flare projects - (Sarah, Sam*, Tam* - 1 week)
- Create landing pages: Manage Experience, Work with Experience (Sam)
- Product pages in the portal to be created as they are launched (Sam, Tam)
https://lh5.googleusercontent.com/p5-zIbW5Iup7Wq_wprsxuXG8RXFgYchIVkbG53GSg9RY-1yWlvGtqkxn9C5Za37gK72mX8V_PKUj7hvT2Bs6TGleCC563sbaf-eC0C-62bfhpf2iAJicaG3APIEjx_fXhTafzsg
