Re: AD and CTM:People
Hi Kristina My 2 cents for Profile Status Error on CTM: People Firstly, when you are trying to push a record into CTM:People, pass a value of "X" into the field "z1D Action". And On CTM:People, there is a filter named CTM:PPL:GetStatusRulesRead_031 Please disable that and copy to a new one and change the run if ( 'Profile Status' != 'DB.Profile Status') AND ( 'z1D Action' != "X" ) , then you should be good to go. We had a similar problem on our ITSP and then now on ITSM. Thanks Mahesh On Thu, Oct 23, 2008 at 7:01 AM, Kristina Hartman < [EMAIL PROTECTED]> wrote: > Hi. > > Pushing data to CTM:People from AD has turned out to be more complicated > than we thought, too. We are using filters to listen to our staging > form, look up some things and replace values, then push to CTM:People as > needed. We discovered that there are some things AR ESCALATOR can't do > because it's got a 'General Access' role--particularly the Profile > Status. I dunno if it's recommended, but I had to go into the Sys:Status > Transition Rules form to disable a couple of rules to allow General > Access to change the status as we needed it to be changed. You'll know > this is your problem if your logs complain about not having permission.. > There may be another way to accomplish this without changing the rules, > but I'm pretty wet behind the ears myself. > > Anyway, we are pushing all the required fields plus site information > (including street address, etc.), the notification language (so it will > create an AR System User Preference for each individual), the manager's > information, default notification method (alert if no email address), > Access Restrictions, and some other stuff. > > It really came down to watching the logs and chasing each error one by > one, especially the filter logs of the push and what happens on the > people form after you've sent the data. We are still working on getting > our account list in Remedy to accurately reflect AD--I've got the > profile status figured out, now I have to figure out how to delete the > accounts that have been deleted in AD (we're not live yet, so these > accounts are just baggage at the moment--after go live we'll keep them > for some duration before purging them). > > > Kristina > > > -Original Message- > From: SPrasad [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 22, 2008 11:01 PM > Subject: Re: AD and CTM:People > > Hi Kathy, > > My name is SPrasad and i an new to this forum. I really need some help. > Now > I got a requirement from my client. The requirement is we need to send > the > people data from a staging form into V7 CTM:People form. We are getting > this > data into staging form from a View form. And from there I wrote > Escalations > to push that data into the staging form. > > After that I wrote one more Escalation on Push fields action to push > data > into CTM:People from staging form. In the Escalation I have included all > the > required fields. But still nothing is happenning. When I talked to BMC > Customer support they are saying we need to updated something else but > they > are not telling what I need updated or Include in the Escalations. > > Environment: > > ARServer: 7.1.0 Patch 002 > ITSM : V7 > > Could plese somebody help me how to populate the data in the CTM:People > form > from a staging form. And any help would be really appreciated. Thanks. > > Thanks > SPrasad > > > > > -- > View this message in context: > http://www.nabble.com/AD-and-CTM%3APeople-tp17235513p20123594.html > Sent from the ARS (Action Request System) mailing list archive at > Nabble.com. > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
In our environment, we have an Oracle DB that stores info from AD as well as SAP. We can't point to AD because the info is not fully updated for each user. SO we have a view form that has escalation that pushes to a staging form. >From there, we use filters to push the data (one for adding new users, and one for updates) We did have to create 2 custom fields on the people form though to flag for updates. Tauf Chowdhury | Forest Laboratories, Inc. Sr. Analyst Office: 631.858.7765 -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza Sent: Thursday, October 23, 2008 9:33 AM To: arslist@ARSLIST.ORG Subject: Re: AD and CTM:People I can't answer for if its supported or not but I had to do very much the same thing too when I had an integration between SAP and CTM:People to update records which included Status update when the employee was on vacation, terminated etc. The data in the Sys Status Transition Rules did not allow for this update and I had to tweak it accordingly to make it work. Like Kristin did I had to chase through errors too one by one and got it right after several runs.. I had to filter data, phone number formats, match city names and state names to the cfg data as some of it was all upper cased in the SAP data - little things like that before I got it to exactly the format it would have been like if it was keyed in from the data configuration interface.. Joe - Original Message From: Kristina Hartman <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Thursday, October 23, 2008 8:01:35 AM Subject: Re: AD and CTM:People Hi. Pushing data to CTM:People from AD has turned out to be more complicated than we thought, too. We are using filters to listen to our staging form, look up some things and replace values, then push to CTM:People as needed. We discovered that there are some things AR ESCALATOR can't do because it's got a 'General Access' role--particularly the Profile Status. I dunno if it's recommended, but I had to go into the Sys:Status Transition Rules form to disable a couple of rules to allow General Access to change the status as we needed it to be changed. You'll know this is your problem if your logs complain about not having permission.. There may be another way to accomplish this without changing the rules, but I'm pretty wet behind the ears myself. Anyway, we are pushing all the required fields plus site information (including street address, etc.), the notification language (so it will create an AR System User Preference for each individual), the manager's information, default notification method (alert if no email address), Access Restrictions, and some other stuff. It really came down to watching the logs and chasing each error one byone, especially the filter logs of the push and what happens on the people form after you've sent the data. We are still working on getting our account list in Remedy to accurately reflect AD--I've got the profile status figured out, now I have to figure out how to delete the accounts that have been deleted in AD (we're not live yet, so these accounts are just baggage at the moment--after go live we'll keep them for some duration before purging them). Kristina -Original Message- From: SPrasad [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2008 11:01 PM Subject: Re: AD and CTM:People Hi Kathy, My name is SPrasad and i an new to this forum. I really need some help. Now I got a requirement from my client. The requirement is we need to sendthe people data from a staging form into V7 CTM:People form. We are getting this data into staging form from a View form. And from there I wrote Escalations to push that data into the staging form. After that I wrote one more Escalation on Push fields action to pushdata into CTM:People from staging form. In the Escalation I have included all the required fields. But still nothing is happenning. When I talked to BMC Customer support they are saying we need to updated something else but they are not telling what I need updated or Include in the Escalations. Environment: ARServer: 7.1.0 Patch 002 ITSM : V7 Could plese somebody help me how to populate the data in the CTM:Peopleform from a staging form. And any help would be really appreciated. Thanks. Thanks SPrasad ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ** This e-mail and its attachments may contain Forest Laboratories, Inc. proprietary information that is privileged, confidential or subject to copyright belonging to Forest Laboratories, Inc. This e-mail is intended solely for the use of the individual or entit
Re: AD and CTM:People
I can't answer for if its supported or not but I had to do very much the same thing too when I had an integration between SAP and CTM:People to update records which included Status update when the employee was on vacation, terminated etc. The data in the Sys Status Transition Rules did not allow for this update and I had to tweak it accordingly to make it work. Like Kristin did I had to chase through errors too one by one and got it right after several runs.. I had to filter data, phone number formats, match city names and state names to the cfg data as some of it was all upper cased in the SAP data - little things like that before I got it to exactly the format it would have been like if it was keyed in from the data configuration interface.. Joe - Original Message From: Kristina Hartman <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Thursday, October 23, 2008 8:01:35 AM Subject: Re: AD and CTM:People Hi. Pushing data to CTM:People from AD has turned out to be more complicated than we thought, too. We are using filters to listen to our staging form, look up some things and replace values, then push to CTM:People as needed. We discovered that there are some things AR ESCALATOR can't do because it's got a 'General Access' role--particularly the Profile Status. I dunno if it's recommended, but I had to go into the Sys:Status Transition Rules form to disable a couple of rules to allow General Access to change the status as we needed it to be changed. You'll know this is your problem if your logs complain about not having permission.. There may be another way to accomplish this without changing the rules, but I'm pretty wet behind the ears myself. Anyway, we are pushing all the required fields plus site information (including street address, etc.), the notification language (so it will create an AR System User Preference for each individual), the manager's information, default notification method (alert if no email address), Access Restrictions, and some other stuff. It really came down to watching the logs and chasing each error one byone, especially the filter logs of the push and what happens on the people form after you've sent the data. We are still working on getting our account list in Remedy to accurately reflect AD--I've got the profile status figured out, now I have to figure out how to delete the accounts that have been deleted in AD (we're not live yet, so these accounts are just baggage at the moment--after go live we'll keep them for some duration before purging them). Kristina -Original Message- From: SPrasad [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2008 11:01 PM Subject: Re: AD and CTM:People Hi Kathy, My name is SPrasad and i an new to this forum. I really need some help. Now I got a requirement from my client. The requirement is we need to sendthe people data from a staging form into V7 CTM:People form. We are getting this data into staging form from a View form. And from there I wrote Escalations to push that data into the staging form. After that I wrote one more Escalation on Push fields action to pushdata into CTM:People from staging form. In the Escalation I have included all the required fields. But still nothing is happenning. When I talked to BMC Customer support they are saying we need to updated something else but they are not telling what I need updated or Include in the Escalations. Environment: ARServer: 7.1.0 Patch 002 ITSM : V7 Could plese somebody help me how to populate the data in the CTM:Peopleform from a staging form. And any help would be really appreciated. Thanks. Thanks SPrasad ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
Hi. Pushing data to CTM:People from AD has turned out to be more complicated than we thought, too. We are using filters to listen to our staging form, look up some things and replace values, then push to CTM:People as needed. We discovered that there are some things AR ESCALATOR can't do because it's got a 'General Access' role--particularly the Profile Status. I dunno if it's recommended, but I had to go into the Sys:Status Transition Rules form to disable a couple of rules to allow General Access to change the status as we needed it to be changed. You'll know this is your problem if your logs complain about not having permission.. There may be another way to accomplish this without changing the rules, but I'm pretty wet behind the ears myself. Anyway, we are pushing all the required fields plus site information (including street address, etc.), the notification language (so it will create an AR System User Preference for each individual), the manager's information, default notification method (alert if no email address), Access Restrictions, and some other stuff. It really came down to watching the logs and chasing each error one by one, especially the filter logs of the push and what happens on the people form after you've sent the data. We are still working on getting our account list in Remedy to accurately reflect AD--I've got the profile status figured out, now I have to figure out how to delete the accounts that have been deleted in AD (we're not live yet, so these accounts are just baggage at the moment--after go live we'll keep them for some duration before purging them). Kristina -Original Message- From: SPrasad [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2008 11:01 PM Subject: Re: AD and CTM:People Hi Kathy, My name is SPrasad and i an new to this forum. I really need some help. Now I got a requirement from my client. The requirement is we need to send the people data from a staging form into V7 CTM:People form. We are getting this data into staging form from a View form. And from there I wrote Escalations to push that data into the staging form. After that I wrote one more Escalation on Push fields action to push data into CTM:People from staging form. In the Escalation I have included all the required fields. But still nothing is happenning. When I talked to BMC Customer support they are saying we need to updated something else but they are not telling what I need updated or Include in the Escalations. Environment: ARServer: 7.1.0 Patch 002 ITSM : V7 Could plese somebody help me how to populate the data in the CTM:People form from a staging form. And any help would be really appreciated. Thanks. Thanks SPrasad -- View this message in context: http://www.nabble.com/AD-and-CTM%3APeople-tp17235513p20123594.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
SPrasad, If you upgrade to ITSM 7 patch 6 or later you can download and install the ITSM data management tool. The purpose of the tool is to populate included spreadsheets, import them into a staging form and then push everything to the correct areas. You could use the mappings from the data load tables to map out your AD integration. Jason Bess Operation Iraqi Freedom Victory Base, Baghdad, Iraq Remedy Enterprise Engineer From: SPrasad <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Thursday, October 23, 2008 6:01:23 AM Subject: Re: AD and CTM:People Hi Kathy, My name is SPrasad and i an new to this forum. I really need some help. Now I got a requirement from my client. The requirement is we need to send the people data from a staging form into V7 CTM:People form. We are getting this data into staging form from a View form. And from there I wrote Escalations to push that data into the staging form. After that I wrote one more Escalation on Push fields action to push data into CTM:People from staging form. In the Escalation I have included all the required fields. But still nothing is happenning. When I talked to BMC Customer support they are saying we need to updated something else but they are not telling what I need updated or Include in the Escalations. Environment: ARServer: 7.1.0 Patch 002 ITSM : V7 Could plese somebody help me how to populate the data in the CTM:People form from a staging form. And any help would be really appreciated. Thanks. Thanks SPrasad -- View this message in context: http://www.nabble.com/AD-and-CTM%3APeople-tp17235513p20123594.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
Hi Kathy, My name is SPrasad and i an new to this forum. I really need some help. Now I got a requirement from my client. The requirement is we need to send the people data from a staging form into V7 CTM:People form. We are getting this data into staging form from a View form. And from there I wrote Escalations to push that data into the staging form. After that I wrote one more Escalation on Push fields action to push data into CTM:People from staging form. In the Escalation I have included all the required fields. But still nothing is happenning. When I talked to BMC Customer support they are saying we need to updated something else but they are not telling what I need updated or Include in the Escalations. Environment: ARServer: 7.1.0 Patch 002 ITSM : V7 Could plese somebody help me how to populate the data in the CTM:People form from a staging form. And any help would be really appreciated. Thanks. Thanks SPrasad -- View this message in context: http://www.nabble.com/AD-and-CTM%3APeople-tp17235513p20123594.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
In my implementation, I do lookups on my staging table to see if the Company, Site, and Organization exist already in Remedy. If they do, I directly create the People record and push that data. If not, I first do some pushes into the Site and Organization forms, and if a Company doesn't exist I just mark it as an error and leave it for the security people to fix, as we don't have legitimate new companies appear randomly. It should be a pretty straightforward process, and I modeled my filters to check the validity of those items after the workflow the People form does. Shawn Pierson -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Charles Sent: Tuesday, July 08, 2008 9:17 AM To: arslist@ARSLIST.ORG Subject: Re: AD and CTM:People hi, I have not actually started this yet, just researching how others have tackled this integration. I'm curious how you are handling Site and Company information? Are you able to import that directly from your staging table into People? On Jul 1, 3:23 pm, Joe DeSouza <[EMAIL PROTECTED]> wrote: > I've done it between PS and AD.. What difficulties are you facing? Have you > created a staging table that contains the data from the AD - preferablu a > ARDBC vendor form? > If you have that ready, an escalation could be used to update existing > records, and create a new one if no match is found.. You will need to update > the CTM:PeoplePermission groups form too in case you are looking to add this > user to a default group. > Joe > > > > - Original Message > From: Charles <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Sent: Tuesday, July 1, 2008 2:50:55 PM > Subject: Re: AD and CTM:People > > Hi Kathy, Shawn, > > I'm getting ready to tackle this integration challenge. Would either of you > mind sharing which forms specifically you need to send data to automatically > create a plain read license account. > > ___ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > Platinum Sponsor:www.rmsportal.comARSlist: "Where the Answers Are"- Hide > quoted text - > > - Show quoted text - ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" Private and confidential as detailed here: http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the link, please e-mail sender. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
hi, I have not actually started this yet, just researching how others have tackled this integration. I'm curious how you are handling Site and Company information? Are you able to import that directly from your staging table into People? On Jul 1, 3:23 pm, Joe DeSouza <[EMAIL PROTECTED]> wrote: > I've done it between PS and AD.. What difficulties are you facing? Have you > created a staging table that contains the data from the AD - preferablu a > ARDBC vendor form? > If you have that ready, an escalation could be used to update existing > records, and create a new one if no match is found.. You will need to update > the CTM:PeoplePermission groups form too in case you are looking to add this > user to a default group. > Joe > > > > - Original Message > From: Charles <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Sent: Tuesday, July 1, 2008 2:50:55 PM > Subject: Re: AD and CTM:People > > Hi Kathy, Shawn, > > I'm getting ready to tackle this integration challenge. Would either of you > mind sharing which forms specifically you need to send data to automatically > create a plain read license account. > > ___ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > Platinum Sponsor:www.rmsportal.comARSlist: "Where the Answers Are"- Hide > quoted text - > > - Show quoted text - ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
I've done it between PS and AD.. What difficulties are you facing? Have you created a staging table that contains the data from the AD - preferablu a ARDBC vendor form? If you have that ready, an escalation could be used to update existing records, and create a new one if no match is found.. You will need to update the CTM:PeoplePermission groups form too in case you are looking to add this user to a default group. Joe - Original Message From: Charles <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Tuesday, July 1, 2008 2:50:55 PM Subject: Re: AD and CTM:People Hi Kathy, Shawn, I'm getting ready to tackle this integration challenge. Would either of you mind sharing which forms specifically you need to send data to automatically create a plain read license account. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
Hi Kathy, Shawn, I'm getting ready to tackle this integration challenge. Would either of you mind sharing which forms specifically you need to send data to automatically create a plain read license account. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
Hi, When the AR Escalation tries to update the record - there is an error that says the Login ID can only be deleted by members of the Contact Organization Admin or Contact Support Admin group - which is preventing this from modifying the record to LOWERCASE. AR Escalator is Admin. Did you experience this error - perhaps this can be fixed by changing the permission on the login field?. In a message dated 5/14/2008 10:58:03 A.M. Pacific Daylight Time, [EMAIL PROTECTED] writes: ** That is the way I did it, including defaulting some NULL fields that Remedy requires. I have an escalation that pulls the AD data (via a vendor form) into a staging table, which then uses filters to do validations and auto-population of some data, then if it passes all the validations, passes it into the CTM:People form and all the related forms that need populated. It sounds like you already have that, but need to use a LOWER() function in your Push Fields that passes the Remedy Login Name field. Something else that will be useful for you is to set up another filter to find users to automatically disable too. In my filter to do that, I have: (( 'userAccountControl' = 514) OR ( 'userAccountControl' = 546) OR ( 'userAccountControl' = 65538) OR ( 'userAccountControl' = 66050)) The userAccountControl field are set to those values when a person is de-activated, so you can create a filter to set them to “Obsolete” in CTM:People as well as set Support Staff? To No and remove all their permissions. This helps quite a bit in keeping license costs down because you’re not wasting licenses by maintaining them for people that are no longer with the company. Shawn Pierson From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kathy Morris Sent: Wednesday, May 14, 2008 11:37 AM To: arslist@ARSLIST.ORG Subject: AD and CTM:People ** Hi, AR System: 7.0.1 Thru workflow, data is passed from Active Directory into Remedy vendor tables then thru escalations into Remedy CTM:People. We have users that sometimes enter the field values in upper/lower case. Whenever they enter uppercase/lower case or leave certain fields BLANK, the record does not get into the CTM:People form. I would like to build workflow that changes the case to LOWERCASE and does error-checking on records that come from AD that don't make it into the CTM:People form. Am I approaching this correctly, or is there a better way? Wondering what's for Dinner Tonight? _Get new twists on family favorites at AOL Food_ (http://food.aol.com/dinner-tonight?NCID=aolfod000301) . __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Private and confidential as detailed _here_ (http://www.sug.com/disclaimers/default.htm#Mail) . If you cannot access hyperlink, please e-mail sender. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ **Wondering what's for Dinner Tonight? Get new twists on family favorites at AOL Food. (http://food.aol.com/dinner-tonight?NCID=aolfod000301) ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
Yes my PeopleSoft database is on Oracle... I used the AIE engine to do the data interchange on a staging form.. On this staging form I created filters to validate the data that has to go into the CTM:People form and the User form.. As a part of the validations I also manupulated data such as the full name to be in the format that the ITSM configuration tool puts it -> Firstname + Middle Initial if it exists + Last name. I also created filters to manupulate phone numbers and extensions like Remedy ITSM does.. You will need to create workflow for inserting data into the CTM:PeoplePermissions group form for default groups that you want new users to be in.. This is just the gist of it.. If you want any other specific details feel free to write to me.. Joe - Original Message From: SUBSCRIBE arslist Melissa <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Wednesday, May 14, 2008 4:48:41 PM Subject: Re: AD and CTM:People ** Joe - Can you share how are you did the PeopleSoft integration? We are working on that here too. Is your PeopleSoft in Oracle or SQL? Joe DeSouza <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" 05/14/2008 03:47 PM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: AD and CTM:People ** A staging form with data checks for everything including duplicate login ID's is what I did when I had to integrate Remedy with the PeopleSoft database recently.. works like a charm.. Creates new users from Peoplesoft with all the necessary permissions they require, and updates existing users.. Joe - Original Message From: Kathy Morris <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Wednesday, May 14, 2008 4:34:55 PM Subject: Re: AD and CTM:People ** I am concerned about error-checking - perhaps I should build workflow to send out notifications when there records make it to the staging table and do not merge into the CTM:People In a message dated 5/14/2008 10:58:03 A.M. Pacific Daylight Time, [EMAIL PROTECTED] writes: ** That is the way I did it, including defaulting some NULL fields that Remedy requires. I have an escalation that pulls the AD data (via a vendor form) into a staging table, which then uses filters to do validations and auto-population of some data, then if it passes all the validations, passes it into the CTM:People form and all the related forms that need populated. It sounds like you already have that, but need to use a LOWER() function in your Push Fields that passes the Remedy Login Name field. Something else that will be useful for you is to set up another filter to find users to automatically disable too. In my filter to do that, I have: (( 'userAccountControl' = 514) OR ( 'userAccountControl' = 546) OR ( 'userAccountControl' = 65538) OR ( 'userAccountControl' = 66050)) The userAccountControl field are set to those values when a person is de-activated, so you can create a filter to set them to “Obsolete” in CTM:People as well as set Support Staff? To No and remove all their permissions. This helps quite a bit in keeping license costs down because you’re not wasting licenses by maintaining them for people that are no longer with the company. Shawn Pierson From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kathy Morris Sent: Wednesday, May 14, 2008 11:37 AM To: arslist@ARSLIST.ORG Subject: AD and CTM:People ** Hi, AR System: 7.0.1 Thru workflow, data is passed from Active Directory into Remedy vendor tables then thru escalations into Remedy CTM:People. We have users that sometimes enter the field values in upper/lower case. Whenever they enter uppercase/lower case or leave certain fields BLANK, the record does not get into the CTM:People form. I would like to build workflow that changes the case to LOWERCASE and does error-checking on records that come from AD that don't make it into the CTM:People form. Am I approaching this correctly, or is there a better way? Wondering what's for Dinner Tonight? Get new twists on family favorites at AOL Food. __Platinum Sponsor: www.rmsportal.comARSlist: "Where the Answers Are" html___ Private and confidential as detailed here. If you cannot access hyperlink, please e-mail sender. __Platinum Sponsor: www.rmsportal.comARSlist: "Where the Answers Are" html___ Wondering what's for Dinner Tonight? Get new twists on family favorites at AOL Food. __Platinum Sponsor: www.rmsportal.comARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___
Re: AD and CTM:People
Joe - Can you share how are you did the PeopleSoft integration? We are working on that here too. Is your PeopleSoft in Oracle or SQL? Joe DeSouza <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" 05/14/2008 03:47 PM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Re: AD and CTM:People ** A staging form with data checks for everything including duplicate login ID's is what I did when I had to integrate Remedy with the PeopleSoft database recently.. works like a charm.. Creates new users from Peoplesoft with all the necessary permissions they require, and updates existing users.. Joe - Original Message From: Kathy Morris <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Wednesday, May 14, 2008 4:34:55 PM Subject: Re: AD and CTM:People ** I am concerned about error-checking - perhaps I should build workflow to send out notifications when there records make it to the staging table and do not merge into the CTM:People In a message dated 5/14/2008 10:58:03 A.M. Pacific Daylight Time, [EMAIL PROTECTED] writes: ** That is the way I did it, including defaulting some NULL fields that Remedy requires. I have an escalation that pulls the AD data (via a vendor form) into a staging table, which then uses filters to do validations and auto-population of some data, then if it passes all the validations, passes it into the CTM:People form and all the related forms that need populated. It sounds like you already have that, but need to use a LOWER() function in your Push Fields that passes the Remedy Login Name field. Something else that will be useful for you is to set up another filter to find users to automatically disable too. In my filter to do that, I have: (( 'userAccountControl' = 514) OR ( 'userAccountControl' = 546) OR ( 'userAccountControl' = 65538) OR ( 'userAccountControl' = 66050)) The userAccountControl field are set to those values when a person is de-activated, so you can create a filter to set them to ?Obsolete? in CTM:People as well as set Support Staff? To No and remove all their permissions. This helps quite a bit in keeping license costs down because you?re not wasting licenses by maintaining them for people that are no longer with the company. Shawn Pierson From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kathy Morris Sent: Wednesday, May 14, 2008 11:37 AM To: arslist@ARSLIST.ORG Subject: AD and CTM:People ** Hi, AR System: 7.0.1 Thru workflow, data is passed from Active Directory into Remedy vendor tables then thru escalations into Remedy CTM:People. We have users that sometimes enter the field values in upper/lower case. Whenever they enter uppercase/lower case or leave certain fields BLANK, the record does not get into the CTM:People form. I would like to build workflow that changes the case to LOWERCASE and does error-checking on records that come from AD that don't make it into the CTM:People form. Am I approaching this correctly, or is there a better way? Wondering what's for Dinner Tonight? Get new twists on family favorites at AOL Food. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Private and confidential as detailed here. If you cannot access hyperlink, please e-mail sender. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Wondering what's for Dinner Tonight? Get new twists on family favorites at AOL Food. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
A staging form with data checks for everything including duplicate login ID's is what I did when I had to integrate Remedy with the PeopleSoft database recently.. works like a charm.. Creates new users from Peoplesoft with all the necessary permissions they require, and updates existing users.. Joe - Original Message From: Kathy Morris <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Wednesday, May 14, 2008 4:34:55 PM Subject: Re: AD and CTM:People ** I am concerned about error-checking - perhaps I should build workflow to send out notifications when there records make it to the staging table and do not merge into the CTM:People In a message dated 5/14/2008 10:58:03 A.M. Pacific Daylight Time, [EMAIL PROTECTED] writes: ** That is the way I did it, including defaulting some NULL fields that Remedy requires. I have an escalation that pulls the AD data (via a vendor form) into a staging table, which then uses filters to do validations and auto-population of some data, then if it passes all the validations, passes it into the CTM:People form and all the related forms that need populated. It sounds like you already have that, but need to use a LOWER() function in your Push Fields that passes the Remedy Login Name field. Something else that will be useful for you is to set up another filter to find users to automatically disable too. In my filter to do that, I have: (( 'userAccountControl' = 514) OR ( 'userAccountControl' = 546) OR ( 'userAccountControl' = 65538) OR ( 'userAccountControl' = 66050)) The userAccountControl field are set to those values when a person is de-activated, so you can create a filter to set them to “Obsolete” in CTM:People as well as set Support Staff? To No and remove all their permissions. This helps quite a bit in keeping license costs down because you’re not wasting licenses by maintaining them for people that are no longer with the company. Shawn Pierson From:Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kathy Morris Sent: Wednesday, May 14, 2008 11:37 AM To: arslist@ARSLIST.ORG Subject: AD and CTM:People ** Hi, AR System: 7.0.1 Thru workflow, data is passed from Active Directory into Remedy vendor tables then thru escalations into Remedy CTM:People. We have users that sometimes enter the field values in upper/lower case. Whenever they enter uppercase/lower case or leave certain fields BLANK, the record does not get into the CTM:People form. I would like to build workflow that changes the case to LOWERCASE and does error-checking on records that come from AD that don't make it into the CTM:People form. Am I approaching this correctly, or is there a better way? Wondering what's for Dinner Tonight? Get new twists on family favorites at AOL Food. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Private and confidential as detailed here. If you cannot access hyperlink, please e-mail sender. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Wondering what's for Dinner Tonight? Get new twists on family favorites at AOL Food.__Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
I am concerned about error-checking - perhaps I should build workflow to send out notifications when there records make it to the staging table and do not merge into the CTM:People In a message dated 5/14/2008 10:58:03 A.M. Pacific Daylight Time, [EMAIL PROTECTED] writes: ** That is the way I did it, including defaulting some NULL fields that Remedy requires. I have an escalation that pulls the AD data (via a vendor form) into a staging table, which then uses filters to do validations and auto-population of some data, then if it passes all the validations, passes it into the CTM:People form and all the related forms that need populated. It sounds like you already have that, but need to use a LOWER() function in your Push Fields that passes the Remedy Login Name field. Something else that will be useful for you is to set up another filter to find users to automatically disable too. In my filter to do that, I have: (( 'userAccountControl' = 514) OR ( 'userAccountControl' = 546) OR ( 'userAccountControl' = 65538) OR ( 'userAccountControl' = 66050)) The userAccountControl field are set to those values when a person is de-activated, so you can create a filter to set them to “Obsolete” in CTM:People as well as set Support Staff? To No and remove all their permissions. This helps quite a bit in keeping license costs down because you’re not wasting licenses by maintaining them for people that are no longer with the company. Shawn Pierson From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kathy Morris Sent: Wednesday, May 14, 2008 11:37 AM To: arslist@ARSLIST.ORG Subject: AD and CTM:People ** Hi, AR System: 7.0.1 Thru workflow, data is passed from Active Directory into Remedy vendor tables then thru escalations into Remedy CTM:People. We have users that sometimes enter the field values in upper/lower case. Whenever they enter uppercase/lower case or leave certain fields BLANK, the record does not get into the CTM:People form. I would like to build workflow that changes the case to LOWERCASE and does error-checking on records that come from AD that don't make it into the CTM:People form. Am I approaching this correctly, or is there a better way? Wondering what's for Dinner Tonight? _Get new twists on family favorites at AOL Food_ (http://food.aol.com/dinner-tonight?NCID=aolfod000301) . __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Private and confidential as detailed _here_ (http://www.sug.com/disclaimers/default.htm#Mail) . If you cannot access hyperlink, please e-mail sender. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ **Wondering what's for Dinner Tonight? Get new twists on family favorites at AOL Food. (http://food.aol.com/dinner-tonight?NCID=aolfod000301) ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
Shawn's approach is a very sound one; I've used it myself. Having that staging form means that you can do whatever you want/need to the data there, and then just push the records that really need updating to CTM:People. Makes a big difference when you're dealing with thousands of people. Rick On Wed, May 14, 2008 at 10:53 AM, Pierson, Shawn <[EMAIL PROTECTED]> wrote: > ** > > That is the way I did it, including defaulting some NULL fields that Remedy > requires. I have an escalation that pulls the AD data (via a vendor form) > into a staging table, which then uses filters to do validations and > auto-population of some data, then if it passes all the validations, passes > it into the CTM:People form and all the related forms that need populated. > It sounds like you already have that, but need to use a LOWER() function in > your Push Fields that passes the Remedy Login Name field. > > > > Something else that will be useful for you is to set up another filter to > find users to automatically disable too. In my filter to do that, I have: > > (( 'userAccountControl' = 514) OR ( 'userAccountControl' = 546) OR ( > 'userAccountControl' = 65538) OR ( 'userAccountControl' = 66050)) > > The userAccountControl field are set to those values when a person is > de-activated, so you can create a filter to set them to "Obsolete" in > CTM:People as well as set Support Staff? To No and remove all their > permissions. This helps quite a bit in keeping license costs down because > you're not wasting licenses by maintaining them for people that are no > longer with the company. > > > > Shawn Pierson > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Kathy Morris > *Sent:* Wednesday, May 14, 2008 11:37 AM > *To:* arslist@ARSLIST.ORG > *Subject:* AD and CTM:People > > > > ** > > Hi, > > > > > > AR System: 7.0.1 > > Thru workflow, data is passed from Active Directory into Remedy vendor > tables then thru escalations into Remedy CTM:People. We have users that > sometimes enter the field values in upper/lower case. Whenever they enter > uppercase/lower case or leave certain fields BLANK, the record does not get > into the CTM:People form. I would like to build workflow that changes the > case to LOWERCASE and does error-checking on records that come from AD that > don't make it into the CTM:People form. Am I approaching this correctly, or > is there a better way? > > > > -- > > Wondering what's for Dinner Tonight? Get new twists on family favorites at > AOL Food <http://food.aol.com/dinner-tonight?NCID=aolfod000301>. > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > Private and confidential as detailed > here<http://www.sug.com/disclaimers/default.htm#Mail>. > If you cannot access hyperlink, please e-mail sender. > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
Re: AD and CTM:People
That is the way I did it, including defaulting some NULL fields that Remedy requires. I have an escalation that pulls the AD data (via a vendor form) into a staging table, which then uses filters to do validations and auto-population of some data, then if it passes all the validations, passes it into the CTM:People form and all the related forms that need populated. It sounds like you already have that, but need to use a LOWER() function in your Push Fields that passes the Remedy Login Name field. Something else that will be useful for you is to set up another filter to find users to automatically disable too. In my filter to do that, I have: (( 'userAccountControl' = 514) OR ( 'userAccountControl' = 546) OR ( 'userAccountControl' = 65538) OR ( 'userAccountControl' = 66050)) The userAccountControl field are set to those values when a person is de-activated, so you can create a filter to set them to "Obsolete" in CTM:People as well as set Support Staff? To No and remove all their permissions. This helps quite a bit in keeping license costs down because you're not wasting licenses by maintaining them for people that are no longer with the company. Shawn Pierson From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kathy Morris Sent: Wednesday, May 14, 2008 11:37 AM To: arslist@ARSLIST.ORG Subject: AD and CTM:People ** Hi, AR System: 7.0.1 Thru workflow, data is passed from Active Directory into Remedy vendor tables then thru escalations into Remedy CTM:People. We have users that sometimes enter the field values in upper/lower case. Whenever they enter uppercase/lower case or leave certain fields BLANK, the record does not get into the CTM:People form. I would like to build workflow that changes the case to LOWERCASE and does error-checking on records that come from AD that don't make it into the CTM:People form. Am I approaching this correctly, or is there a better way? Wondering what's for Dinner Tonight? Get new twists on family favorites at AOL Food <http://food.aol.com/dinner-tonight?NCID=aolfod000301> . __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Private and confidential as detailed here: http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the link, please e-mail sender. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
AD and CTM:People
Hi, AR System: 7.0.1 Thru workflow, data is passed from Active Directory into Remedy vendor tables then thru escalations into Remedy CTM:People. We have users that sometimes enter the field values in upper/lower case. Whenever they enter uppercase/lower case or leave certain fields BLANK, the record does not get into the CTM:People form. I would like to build workflow that changes the case to LOWERCASE and does error-checking on records that come from AD that don't make it into the CTM:People form. Am I approaching this correctly, or is there a better way? **Wondering what's for Dinner Tonight? Get new twists on family favorites at AOL Food. (http://food.aol.com/dinner-tonight?NCID=aolfod000301) ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
