How does this project fit with the strategy?
NOT STARTED / IN PROGRESS / COMPLETED
Why are we doing this?
The publications demographic information currently stored in iMIS linked to Kentico for the Knowledge Base via the iMIS SQL query "CII_Pubs_for_Kentico".
Impact of this problem
Knowledge Base will break unless pub info is imported into Salesforce and query is tweaked and reconnected.
How do we judge success?
|The publication info continues to be feed properly into Knowledge Base.|
What are the steps?
What do we already know?
We have to clean up the publications demographic info from iMIS and the Pub Portal.
Currently, the SQL query is pulling the following 18 data fields: ItemID, Title, Description, PRODUCT_CODE, PRODUCT_CODE_E, PubDate, ProductType, Status, PageCount, ShortDescription, Member_Price, NonMember_Price, TeamCode, Location, HardCopyAvailable, ECopyAvailable, KnowledgeArea, Pub_Author as CopyAvailable.
What do we need to answer?
Are there any publications that we can purge?
What pub info do we need to keep and what can we purge?
Ready to make it
What are we doing?
Why will a customer want this?
The customer will enjoy that KB continues to work.
Visualize the solution
Scale and scope
- Erika S Corbell Confirm fields to be added to Price book, map fields to CII_Pubs_for_Kentico
Copyright © 2016 Atlassian
This work is licensed under a Creative Commons Attribution-Non Commercial-Share Alike 4.0 International License.