Importing records like that is problematic, because the ITSM workflow is set to fire on Submit (and perhaps Modify), but not Merge, and, IIRC, records imported using the Import tool trigger Merge actions rather than Submit actions (if I can say it that way). We had imported a bunch of people and their permissions this way only to find out that the updates to the User table didn't happen correctly. I ended up created some escalations that triggered the workflow necessary. If the Import utility can be configured to always do a Submit action, then it might work fine.
Otherwise, another simply workaround (if you're ok adding a form and a filter) could be to create another form that you will import the records to and that has one filter that fires on Submit and Merge and that simply does a push fields from the current form to the CTM:People Permission Groups form. That way, you're guaranteed for the new records to be created in the permission groups form by a Submit instead of a Merge. Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, February 26, 2010 11:23 AM To: [email protected] Subject: Ideas on Procedure for mass update for user licenses .... ** Due to an automated provisioning process our licenses got out of synch and we need to go back and mass change several itsm users to read-only and give some users more licenses. We have thought through a process and are wondering if anyone has any input/thoughts or has had to do this before. Based on our testing - removing an entry from the "CTM:People Permission Groups" form removes all relevant information in the user form. To resolve people that got a license and shouldn't we are going to simply remove the entry from " CTM:People Permission Groups". To resolve the issue with adding licenses we simply will create a .csv and import into the " CTM:People Permission Groups". We haven't tested that piece yet but are hoping that the workflow kicks in to update the User table. Anybody tried this or have any other ideas? Thanks, Sean _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
