Hi,
This is a different between Demo kit 910-4 I am evaluating and "pre-recorded Webcast" I saw in Aras web site.
In 'pre-recorded Webcast' when admin edit (PP-001055) and click Char[...], Sev & Occ[...] in Process FMEA tab, Innovator will pop-up a list for user to pick-up proper one. That pop-up list have identier with creteria predefined in TOC--> Library.
But when I use admin to login 910-4 demo, I also edit process planner (PP-001055), click Occ[...] and Det[...], I only get a simple selection list as below, and 'Sev' even no response.
How to setup the permission or privilege that I can get the list as that shows in 'pre-recorded Webcast'?
Thanks,
SS Hsu
Normal 0 MicrosoftInternetExplorer4
Blogs are always a main source of getting accurate information and provide you the handy results; you can get instant and reliable information which surely helps you in any field of your concern. I am post graduate in IT and HR. These days I am doing preparation of different online certifications and I found mcitp exams guide is the best helping source which is providing 100% authentic material. I also spend my extra time in surfing internet, listening music and playing games. After my exams I would like to join your group.
Regards
Marry Davidson
The most important security concept to be aware of is that workflows run as part of the system account in SharePoint Server 2010, through the identity application pool settings on the server computer and domain. This means that within SharePoint Server 2010, workflows have administrator permissions. On the server, workflows have the same permissions as the application 646-223 pool, which frequently has administrator permissions. These permissions enable workflows to perform actions that ordinary users cannot perform, such as routing a document to a specific location or records center, or adding a user account to the system. This setting, that workflows have administrator permissions, cannot be changed. It is up to the workflow schedule (that is, the workflow code) to detect user actions and, based on those actions, continue or roll back changes, or impersonate a user in order to mimic that user’s permissions.