Asking for Advice : Where to import legacy history?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
Here's the setup:
- Legacy app (non-ServiceNow)
- New shiny (ServiceNow scoped app)
Legacy app tracks Projects. The app stores activities : comments, state changes {Design, Design Approved, etc.}, Sign-offs, in separate tables. There are a large number of currently active legacy app projects. The legacy app uses Oracle, the client is moving away from Oracle.
Legacy app data has been properly exported and kept safe. Legacy app project data has been imported into New shiny. Historical data {comments, state changes, sign-offs} has not. Client desires to import historical data and have it visible in the usual ServiceNow Activity stream on the record form.
Thought 1:
Do we somehow import this data to Record History [sys_history_set], History [sys_history_line], Journal Entries [sys_journal_field] and work through getting this data to display on New shiny's Activity stream?
OR
Thought 2:
- Do we add an indicator/flag field to New shiny's Project table to ID legacy (before ServiceNow) projects
- Build out another custom table, with proper structure to handle all the various types of history entries (Legacy History) they desire?
- Based on New shiny Project's "legacy" field, we make a Related List visible that points to Legacy History so the peeps can view, filter, export to their heart's content.
Additional challenge:
Client would like active legacy projects to be associated with New shiny's Project Flow so these legacy projects can continue those process activities in New shiny. I think this is possible, I've just never had to do it up to this point with ServiceNow.
Thoughts? Any good strategies on this would be greatly appreciated.
ver. Yokohama
