Restrict metadata field during an update to a specific user group

Hello everyone,
I am having some trouble figuring out the best way to restrict permissions to change some metadata fields for 2 different groups of users.
I have two user groups, A and B. Group A will be checking in documents that the B group will then review for accuracy and quality. Group B will then update an optionlist field called "Status" with either "Recommended" or "Not Recommended".
This is not a workflow situation as the scope requires that all documents are immediately available for searching. I currently have a CheckIn and Search profile for the content permitting read write access to groups A and B. The "Status" field is hidden on the CheckIn page. Can anyone please suggest a good way to restrict the field "Status" on an Update page to just "B" users? Groups A and B should be able to update all fields with the exception of the B restricted "Status" field.
Thanks!
Edited by: user6750815 on Jun 2, 2010 4:11 PM

Hey rMac,
I understand it this way you have one profile for A and B user groups. On this profile Status field is hidden.
If this is your problem you can approach it from two places, while making the rule for hiding the Status field, use rule activation condition. Make it active only for users with Role A . This way even with single profile some of the user with Role B will be able to see the Status field.
otherwise you can put similar code in Restrict Personalization Link where in you make this hidden field editable and compulsory for Users in B.
cheers,
sapan

Similar Messages

User Defined Fields are read-only for a specific user

I have a user that has lost her ability to edit user defined fields. They are all grayed-out for all UDFs, all document types. Other users have access to these fields. I've even copied the authorizations from a user not experiencing the problem, but with no positive results. Anyone have any thoughts on this?
We are on SBO 8.8 PL 16

Hi Randy......
This might be the Authorisation issue......
Please check properly whether you have given Full authorisation for Form Setting to such user or not and check by enabling it through Form Setting
Regards,
Rahul

[Solved] wine: restricting execution to specific user/group safe?

From what I understand, the way of exploiting a bug in a browser and launching malware in the background won't work with wine as the malware injector calls "some.exe", not "wine some.exe". So using wine is safe unless the person is "dumb" enough to execute a windows executable from an untrusted source, right?
I have the following situation: there are two users, one should be able to execute windows programs, the other one (who recently got mislead by a "you need to update flash player" malware link -_-) should be unable to.
What I thought I'd do was to create a group, let's say, called "wine" and change the permissions on the wine executable(s) so that only users of this group get the executable right. Then add users to this group.
Is this safe? Is changing permissions on wine/wine64 enough, or should I also modify them for wine(64)-preloader? Or is there maybe a better way to do that?
edit: also, will the permissions be reset when pacman updates wine?
Last edited by Soukyuu (2014-05-28 15:20:23)

Ideally, I'd want the user to be able to only execute whitelisted wine programs, but from what I know it's not possible. It's mainly to guard against accidental execution of mal/adware, which happened a few times while this computer was running windows. My parents lack the technical knowledge to try and circumvent those measures, nor do they have a reason. This means they are only using the GUI and call me if something doesn't work. Would using an alias guard against double-clicking on a windows binary?
The reason I have wine at all is that I still need some windows programs on that PC, and the reason I switched to linux was to free up resources used up by the antivirus. So theoretically I could just launch the programs I need in a VM, but that would just negate any resource gains I got by installing linux...

Defining Custom XMP Metadata Fields

Is it possible (possibly through the export SDK?) to define a custom metadata field that Aperture can access?
Specifically, Adobe allows Photoshop users to create custom metadata panels to define new XMP namespaces allowing new metadata standards to be entered. This information is saved with the image file, just like the IPTC XMP fields.
However I am curious if there is any way Aperture can be customized to allow these custom fields to be read and set up as options in the metadata viewer.
I'm currently involved with a NASA/ESA project to bring more complete metadata annotations to astronomy images, but so far Photoshop/Bridge seem to be the only packages with defined support for custom metadata. It would be fantastic if such fields could be accessed from Aperture too!
PowerMac G5 2.3GHz Mac OS X (10.4)

Hi Robert,
Talk about timing! I just finished coding an export plugin for Aperture to do XMP metadata (beyond the built-in support that Aperture provides) that I'll be releasing as donation-ware in the next week and know all about this right now
What you could do is add custom keys within Aperture, define your own XMP namespace, and then, in the plugin, map from your custom keys to the XMP namespace. If you want, drop me an email (joshanon at mac dot com), and I might be able to send you the source to my plugin as a starting point.
Josh

TMG2010 - Exhcange 2010 - Restrict User Groups

Hey Guys,
We have TMG2010 currently reverse publishing OWA however no Pre-Auth is being used, the Exchange 2010 Auth Form is being used.
The TMG box is not Domain Joined, however if we joined it to the domain would we be able to use AD Security Groups to restrict access to certain services such as OWA? Without enabling the "Pre-Auth" Functions of TMG?
Thanks,
Robert
Robert

Hi,
yes it is possible to restrict access to specific services like OWA/EAS/OA on the TMG Server for specific user/groups if the TMG Server is a member of the domain. You can also use pre-auth if the TMG Server is a member of a workgroup if you use LDAP
on the TMG Server:
TMG publishing:
http://www.microsoft.com/en-us/download/details.aspx?id=8946
TMG and LDAP:
http://www.isaserver.org/articles-tutorials/configuration-general/Microsoft-Forefront-TMG-Using-LDAP-RADIUS-Authentication.html
regards Marc Grote aka Jens Baier - www.it-training-grote.de - www.forefront-tmg.de - www.galileocomputing.de/3570

No provisioning of User Group for authorization field in user master

We are implementing CUP 5.3 workflows. Both in manual proviosing and automated provisioning based on User Defaults the user group gets only provisioned to the Groups tab in SU01. The field User Group for authorization on the Logon data tab remains empty (field CLASS from system table USLOGOND, filling CLASS field in table USR02).
In User defaults both under user default as on the user group tab the user groups have been defined. In manual provisioning the correct list of user groups get displayed for selection.
Under field mapping in the Application field I only find User Group in user master maintenance, but not User group for authorization. However I would assume I do not need to use field mapping, as I want to automate this provisioning based on user defaults.
Am I missing a configuration setting here? If so, where can I set it?
I would assume the provisioning of this field is possible. RAR reports the user group also based on the User group for auhtorization and not from the Groups tab.

S.Pados,
I can assure you that what I said in my last response does provision the User Group For Authorization Check on the Logon Data tab; in fact, I was having the opposite issue where the Group tab was not being provisioned; however, I am ruunning AE 5.2 and you said you are running 5.3; maybe something did change or got lost in the releases; it probably is good to see what SAP has to say about this; I would hate to lose this capapbility when I upgrade to AE 5.3
As far as using the custom field for multiple applications, would that field not be usable for any of the applications you would select in the request form?; if you are using the same table names in the different SAP systems (selectable by the application field on the request) would the drop down selections be whatever the table has defined for that system? I may not be understanding something here so I am just asking;
It would be great to have a Group field automatically filled in by another selection to avoid the user involvement; I agree with you there; because of our concerns on users entering the AE request, our shop has decided to continue with the users submitting the request through normal email and the security administrators perform the AE entering; this way we have a better idea on something like the GROUP field; we have an option to include the original email as an attachment for justification of the request
Sorry I could not be of more help
Jerry
Ryerson,Inc.

Restricting access to metadata field for some people

Hey
Our users have suggested that they would like to restrict the rights to a specific metadata field so that only a few people can do the update. In playing around with this idea, I can see how I might be able to do it through a criteria workflow, but it would be complicated and clunky. Does anyone have any suggestions for other ways of doing this?
Regards,
A

> I was afraid that it might be a customisation.
This one should be quite simple
If I were you I would not bother with metadata editing here. Simply add a new Content Action that will call a service modifying the value for you. Note that you will need two actions: Replicate / Discard replication and those options will display only to those users that are authorized to use them. If you want, you might also perform a security check when the service is called (e.g. if somebody tries to call the service directly, not just use the menu action). However, be aware that since you defined your check as metadata, users without authorization still can modify it, if they switch to Full information during Update.

Is it possible to limit what fields can CUP update during Auto-provisioning

I have configured CUP to do Auto-provisioning after all the stages have been approved. However, our client requirement is to not to update some fields in user master e.g: User Valid Start date and End Dates. Is it possible to restrict CUP to update only the required fields and not all fields during auto provisioning process?
Can you please let me know if this possible in CUP?
Thanks
Anand

Alpesh,
Currently my User details source is pointing to SAPHR . I have made the valid start date and end date hidden in the request form. However, CUP pulls the info anyway and updates SU01 record during the auto provisioning. I guess hiding the fields may not work.
Please let me know if you have find any solution from your sources.
Thanks
Anand

Update Managed Metadata field in SharePoint 2013 Designer Workflow for O365

Hi Guys,
I need to update the managed metadata field in SharePoint Custom List using Workflow but its not working. I have also tried to use the HTTP WebService POST Operation but no luck.
Am doing this for a SharePoint Online (O365) Site.
Has anyone worked on something similar and was able to get it running ?
I saw a post to create a custom Workflow Activity but I don't have a choice to go with the custom code option.
http://patrickboom.wordpress.com/2013/07/23/workflow-activity-set-managed-metadata-column/
I was able to achieve this by creating a SP 2010 based Workflow for O365. Which means that it worked well with SP 2010.
Is there a different way to do it in 2013 ? I tried almost all options apart from creating custom Activity but nothing worked out.
Any help would be great.
Thanks,
Nutan
Nutan Sharma

Hi Nutan,
According to your description, my understanding is that you want to update Managed Metadata field with SharePoint 2013 Designer for SharePoint Online.
As far as I know, there is not an OOB action to achieve your requirement with SharePoint 2013 Designer for SharePoint 2013. Customizing a workflow action is a better option to achieve it. Why didn’t you customize a workflow action as Patrick’s blog?
In addition, please take a look at the article about Nintex workflow, check whether it is useful for you:
http://habaneroconsulting.com/insights/setting-managed-metadata-fields-in-a-nintex-workflow#.UykBSf6KDHo
As this issue is about SharePoint Online, I suggest you create a new thread on SharePoint Online forum:
http://social.technet.microsoft.com/Forums/en-US/home?forum=onlineservicessharepoint . More experts will assist you.
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

DateFormat for updating the metadata field through RIDC

Could you please tell me what will be the valid date time format for updating metadata field value through RIDC.?
I am using ADF technology to connect with webcenter UCM and using all services to check-in,update, search generic screens using UCM services. I am able to update other text type metadata field through ADF screen BUT when i update date field then i am getting date parsing error..
xSubmitDate DATE type in UCM.
xSubmitDate value = 05/08/2013 05:36 PM
oracle.stellent.ridc.protocol.ServiceException: Unable to update the content item information for '0804'. The field 'xSubmitDate' does not contain a valid date. Unable to parse date '05/08/2013 05:36 PM'.
Thanks in Advance.

This blog post I wrote may be of some help: http://www.redstonecontentsolutions.com/5/post/2011/10/parse-date-usingridc.html
Jonathan
http://jonathanhult.com

Updating Content Type from other metadata field

Hi.
In the process of creation of metadata fields a customer use a custom metadata field called 'class' to define what type the content are. The field Content Type was leave untouchble. Now they have tons of content in the same folder inside vault cause content server uses the metadata content type to create vault subfolders. What is the best way to eliminate the field class, transporting the metadata to the correct field content type and mantain the correlation of the links to the native files and weblayout files of the content? If I just update the column content type with the data in column class I believe that willl be a mess of broken links. Can anyone suggest anything?
Thank you!

Hi there,
Thought i could not comprehend all that you want, I could get that you have problem with a meta data filed.
Instead of using "Content Type" earlier contributors used "class" and now you want to chagne the "class" field with appropriate value of "Content Type".
This can be done provided the original "class" type was used intellegently by using following steps
1) depending on various values of class(e.g. all document for which class=A) created exports using archiver, also deleted them same time.
2) Import the archiver created in step one and prove an input map for the "class" field to appropriate value as "Content Type"(content type =B)
In this way all content items with class=A would be converted into content type=B.
Hope that helps you.
regards,
sapan

Can Release Date metadata field be made editable on updates ?

Hi,
When we check in a new content Release date metadata field appears as an editable field. But on subsequent metadata updates it appears as a non editable field. Is it possible to make the release date field as editable ?
Regards,
Bhaskar

Hi Tim,
Whenever my customer makes changes to the Contribution Site through site studio, he wants to have hold on the Release date also. But currently release date becomes non editable when we do any metadata update. Is it possible to make this Release Date column editable or is there any option in Site Studio so that when the customer makes changes to the contribution site, before he saves the data there should be a pop up of update document information page with the release date column being editable ?
Regards,
Bhaskar

What is the easy way to update Managed Metadata field multi select values using client object model C#?

The below mentioned code works sometimes and doesn't most of the time. What is the real best way to update multi select managed metadata fields?
Microsoft.SharePoint.Client.File file = site.GetFileByServerRelativeUrl("/sites/myspsite/Documents/Presentation2.pptx");
clientContext.Load(file);
clientContext.ExecuteQuery();
ListItem currentItem = file.ListItemAllFields;
clientContext.Load(currentItem);
clientContext.ExecuteQuery();
currentItem["Country"] = "-1;#India|1d13cfe9-d6f4-4bd3-a6c7-4b46a81f2a96;#-1;#China|9c1dff73-82db-44b1-8d70-f4258dd24e47;#-1;#USA|b9295c0b-67d4-4dc5-99d4-e88af888de48";
currentItem["Title"] = "Demo Doc";
currentItem.Update();
clientContext.ExecuteQuery();
file.CheckIn("test check-in", CheckinType.MajorCheckIn);
clientContext.ExecuteQuery();
Anuradha!!

Hi,
Here are two blog for your reference:
How to Work with Managed Metadata Columns by Using the SharePoint Client Object Model
http://blogs.msdn.com/b/sharepointdev/archive/2011/11/18/how-to-work-with-managed-metadata-columns-by-using-the-sharepoint-client-object-model-kaushalendra-kumar.aspx
SharePoint 2010 Code Tips – Setting a Managed Metadata Field with the Client Object Model
http://sharepointfieldnotes.blogspot.com/2011/08/sharepoint-2010-code-tips-setting.html
Best Regards
Dennis Guo
TechNet Community Support

Update list item with managed metadata field returns The security validation for this page is invalid

Using SharePoint 2010 Server
I'm attempting to programtically update a managed metadata field in a document library. I'm able to do it without issue on all other non-managed metadata fields. When I attempt it on a MM field I get the error message
"The security validation for this page is invalid. Click Back in your Web browser, refresh the page, and try your operation again."
After some digging I realised that this error was being caused because SharePoint was trying to write to the TaxonomyHiddenList list (../sites/mysite/Lists/TaxonomyHiddenList/AllItems.aspx)
When I update a document through the browser with a term (Term01), it shows up in this TaxonomyHiddenList . I can then run my application, apply Term01 to my new document and it works fine. But if I apply Term02 to my new document it gives me the error above.
Summary
My app can read the TaxonomyHiddenList fine but it can not perform an operation that would write to it, resulting in not being able to update the MM field.
Question
Is there any advice on how I can further debug this issue?

Hi,
According to your post, my understanding is that you want to update managed metadata field in document library programmatically.
I have made a simple code demo below to updata managed metadata field in document library, it works like a charm, you can refer to it.
public static void UpdateMSField()
using (SPSite site = new SPSite("http://YourSiteURL"))
using (SPWeb web = site.OpenWeb())
//SPList list = web.Lists.TryGetList("Libs_1");
SPDocumentLibrary lib = (SPDocumentLibrary)web.Lists["Libs_1"];
// No point in proceeding if we can't find the list
if (lib != null)
// add a new item
// SPListItem item = list.AddItem();
SPListItem item = lib.GetItemById(1);
//Console.WriteLine(item.Name);
// get the current taxonomy session, which wraps up all of the
// associated TermStore objects for this SPSite object
TaxonomySession metadataService = new TaxonomySession(site);
// get the taxonomy field
TaxonomyField taxField = item.Fields["MMS_1"] as TaxonomyField;
// get the term store associated with the taxonomy field
TermStore termStore = metadataService.TermStores[taxField.SspId];
// get the actual term set associated with the taxonomy field
TermSet termSet = termStore.GetTermSet(taxField.TermSetId);
// search for the terms we wish to set the field to
var terms = termSet.GetTerms("term_1", true, StringMatchOption.ExactMatch, 1, false);
// if we have found a term populate the field
if (terms.Count > 0)
// set the field to the term(s) we have found
taxField.SetFieldValue(item, terms.First());
// Update the item
item.Update();
Console.WriteLine("success...");
More reference:
http://www.3guysonsharepoint.com/?p=1052
http://vineet-winit.blogspot.com/2013/04/how-to-update-managed-metadata-field-in.html
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

PPCO0007 User Exit for Changing Header Fields During Order (CO40)

.. Hi !!!!
I need your help or suggestions,
I need to change the standar order before to save, i found the user exit PPCO0007,
i assign the new value for the order, but when finish the fuction, EXIT_SAPLCOZV_001, the new values are
lost, and finally the system set the standard order.
Someona know how can change the order and the the batch.
Thanks
Noemí Huerta

Hi Noemi
You can use the enchancement PPCO0007 (exit when the production order is saved).
Use the function module EXIT_SAPLCOZV_001 (User Exit for Checking or Changing Header Fields During Order Save) to update the field priority starting the information in the material-customer info record.

Restrict metadata field during an update to a specific user group

Similar Messages

Maybe you are looking for