-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Problem definition
If ServiceNow or JSON endpoint has a tag containing two or more values separated by a delimiter (e.g. comma), there is no way for Insight Import to split the values and associate / reference objects from those values. Example tag:
<u_services> d76n4789db472a5589d1vgdfkf71025Lo,c68b5162db472a0035d1bedfkf98764kk </u_services>
Overall, Insight should provide more control to manipulate and transform imported data, as the source systems often cannot be changed and they will give output as-is.
Suggested resolution
Improve Insight import so that it could separate more delimited values from a single XML tag; give Insight more power to manipulate / transform source data when importing.
Potential workaround
Use combination of Insight automation and Groovy scripting to separate the values. General idea:
- Map the value that needs to split in in a text custom field during the Insight import
- After the data is imported, that field value that needs to have its value split, will be stored in that custom field
- Create an Insight automation rule that would run on newly created objects, that would trigger a Groovy script to read the stored values from that text field, split them, and use that to create / associate Insight objects.
- links to
I had the support issue leading to this suggestion.
The more generalized problem is that I, as the importer, has no control over the export. I must take what the different systems will export and use Insight to transform that to something understandable in Insight context.
As I see it some preprocessing powers could eliminate the problem. If I could set up a transformation of the JSON object prior to the import I could define rules that would convert the above to something Insight understands.