"Transactional Data" can be loaded using Data Management Tool. For missing information such as Person ID, I would recommend creating a generic People record and use that to load the incidents.
Thanks Mahesh On Wed, Jun 6, 2012 at 3:05 PM, Longwing, LJ CTR MDA/IC < lj.longwing....@mda.mil> wrote: > Yea....the Incidents I'm creating are going to be already in closed > status, and won't be having things like person id populated because this is > data being migrated from a non-remedy system. Was planning on getting all > of my data ready and importing a csv file through the data import tool. > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Sabyson Fernandes > Sent: Wednesday, June 06, 2012 1:45 PM > To: arslist@ARSLIST.ORG > Subject: Re: IncidentInterface_Create > > ** > LJ, > > I have worked with loading incidents directly on the incident form via AIE > and bypassing the IncidentInterface_create form. This was for an ITSM 7.0 > go-live and moving data from ITSM 6 to ITSM 7 on a different server (a long > time ago). > > > > Some of the things I had to take into consideration when doing this > directly: > - Any hidden fields that need to be populated for workflow tied to active > links were populated. (Person ID comes to mind!) > - Check the foundation data and make sure you use valid values when > creating the incident > - Check the hidden flag fields (create service request flag comes to mind) > and make sure that the value you use is valid. > - Ensure data integrity for relationships. (may not apply to what your > doing) > - Ensure that you populate all fields for the status/stage the incident is > going to be created in. > > The incident interface create helps you to pre-populate values from a > template if a template id is provided. It also validates the location info, > op and prod cats, assignments etc. I take it you are still going via the > API? > > > Hope this helps. > > Saby > > ________________________________ > > From: "Longwing, LJ CTR MDA/IC" <lj.longwing....@mda.mil> > To: arslist@ARSLIST.ORG > Sent: Wednesday, June 6, 2012 12:23 PM > Subject: Re: IncidentInterface_Create > > > So what you are saying is that I may be assuming competence where none > exists? :) > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of ravi rai > Sent: Wednesday, June 06, 2012 10:19 AM > To: arslist@ARSLIST.ORG > Subject: Re: IncidentInterface_Create > > ** > LJ > i dont think it does all validation we have written lot of filter and > filter guides to do validation which we needed > > > > > Date: Wed, 6 Jun 2012 10:12:56 -0600 > > From: lj.longwing....@mda.mil > > Subject: Re: IncidentInterface_Create > > To: arslist@ARSLIST.ORG > > > > Hey Ravi, > > Yes, I'm familiar with the function of the form, but what I'm not aware > of is WHY it's needed. Basic information that I have picked up over the > years tells me that because of the fact that HD is VERY active link based, > there are various business rules that are written and enforced when > creating things through the GUI that aren't enforced when creating them > through a push to the form itself. This apparently lead to the creation of > the interface form to enforce the same business rules at the Filter level, > and push it to the incident form when everything is copasetic....the > question I'm raising is really 'what does it do'...what sort of validations > does it perform that I won't get if I push directly to the incident form > itself? > > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of ravi rai > > Sent: Wednesday, June 06, 2012 10:01 AM > > To: arslist@ARSLIST.ORG > > Subject: Re: IncidentInterface_Create > > > > ** > > LJ , > > Greetings .... > > IncidentInterface_Create act as intermidiate form for landing request to > create incident SRM also use this form. > > webservice "HPD_IncidentInterface_Create_WS" > > It works fine in 7604 not sure about 7.57 or previous version > > > > Ravi > > > > > > > Date: Wed, 6 Jun 2012 11:24:52 -0400 > > > From: jdso...@shyle.net > > > Subject: Re: IncidentInterface_Create > > > To: arslist@ARSLIST.ORG > > > > > > For whatever it may be worth, I recall problems with this form and the > > > WS associated with it in its OTB state - I do not recall which version > > > but it wasn't any of the most recent ones.. One of the required fields > > > was missing.. I had to create that field both on the form as well as > > > modify the WS to include that.. I do not recall much beyond that.. > > > > > > Maybe its been fixed and your problem is something else - but I just > > > thought I'd throw this there.. > > > > > > Joe > > > > > > -----Original Message----- > > > From: Longwing, LJ CTR MDA/IC > > > Sent: Wednesday, June 06, 2012 11:18 AM Newsgroups: > > > public.remedy.arsystem.general > > > To: arslist@ARSLIST.ORG > > > Subject: IncidentInterface_Create > > > > > > I'm getting thrown into the deep end of ITSM and trying not to splash > > > too much trying to stay afloat and would love some assistance from the > > > more experienced swimmers in these waters. > > > > > > I'm in a situation where I'm creating incidents through a non 'gui' > method. > > > From discussions on the list I know that you don't want to do it > > > directly into the incident form directly, and that I 'should' do it > > > through the IncidentInterface_Create form...but in this situation I > > > can't. I'm looking for either guidance to documentation that discusses > > > the interface form, and what it does for me, or either straight from > > > the horses mouth information about the things I need to look out for > > > when loading these directly in the table. One thing that may be > > > important...the records that I'm creating don't need to 'flow' > > > anywhere....they are being created strictly from a historical > perspective and will be created already in the 'Closed' status. > > > > > > Remedy 7.5 Patch 7 > > > ITSM 7.5 > > > > > > ______________________________________________________________________ > > > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
