Dear Rick, We had initially planned to load the data feed via EIE through RLO, however our EIE got all messed up and then we had to shift to using the staging form on a view form. Our staging form does all the validations before we submit data to any of the actual ITSM forms. The Stages we go through are mentioned below
1. Get the GUID using the CTM:CFGPeopleTagNumgenerator form 2. Submit the entry to the CTM:People Form 3. Receive the person Id 4. Create the permission entries for the default user depending on the company the user belongs to using the CTM:People Permission Groups form (We have multitenancy turned ON) 5. Submit the permission changes to the User form. There were some particular filters on the CTM:People form that checked for the access rights for the user AR ESCALATOR which had to be modified. Hope this helps. Regards, Roney Samuel Varghese On 5/8/07, Jarl Grøneng <[EMAIL PROTECTED]> wrote:
I would go for your second solution; EIE to populate a staging table in ARS, and then update CTM:People Looking into a smilar solution, but the staging form will be a display-only form. We will import from a csv file. (EIE is not an option, so we using our own generic import-program) -- Jarl On 5/8/07, strauss <[EMAIL PROTECTED]> wrote: > ** > > I am busy trying to figure out how to do this from EIE against a SQL Server > table that is being updated by Novell eDir LDAP data. The "quality" of the > EIE documentation isn't making this any easier. Right now I am trying to > push it directly into CTM:People, but I suspect that I will either have to > pre-populate required data for CTM:People fields in a second SQL Server > table and use that with EIE, or use EIE to populate a staging table in ARS > from which to populate CTM:People. Still looking for the solution that will > be the easiest to implement/understand/troubleshoot. In > our case, it will involve over 116,000 records for our active LDAP entries. > All suggestions are welcome. > > Christopher Strauss, Ph.D. > Remedy Database Administrator > University of North Texas Computing Center > http://remedy.unt.edu/helpdesk/ > > ________________________________ > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook > Sent: Monday, May 07, 2007 5:02 PM > To: arslist@ARSLIST.ORG > Subject: ITSM 7 People import methodology > > > ** > I am attempting to create ITSM 7 people records from LDAP information, and > want to run this scenario by you more experienced few who may already have > done this: > > I have the LDAP connection to the people data already, have stored that > information in a holding form (about 700 records), and have culled that > "get" down to only the 15 or so fields that appear to have useful data in > them. > > I know I need to push the phone #s into the Phone Detail form first, and > will string parse that value as part of that push. There will be no Wallet, > Travel, Education, Attachments, Home Address, or Benefit, etc. info > imported. > > I also need to perform some string manipulation on the LDAP formatting > (culling out the "CN=" type strings), after which I want to push the data > into the ITSM 7 People form, along with various local string/selection field > settings (i.e. Status, Client Type, $NULL$, etc.). > > Once I have the import Filter built, I will create an Escalation to refresh > the data from LDAP to the holding form, which will cause the Filter to push > that data to the People form on Modify. > > I will add the group memberships/roles/permissions later, as that's a much > smaller task that can be done manually. > > Is there anything else I haven't thought of at all? Is there a > better/easier way? > > Rick Cook__20060125_______________________This posting was > submitted with HTML in it___ > __20060125_______________________This posting was > submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
