how to add members to the group while creating user in camunda platform - wildfly-10

I'm new to camunda platform.can you guys give a hint to do this.
While creating a new user in camunda,i have created a text field to mention the group name that the user wants to join.my query is How can i add this user under the group members list.

You have to run a PUT request on /group/{groupId}/members/{userId}
to add an member to a group. The groupId should identify the group and
the userId the user which should be added.
See for more information the documentation.

Related

Active Directory Group Members don't match member attribute

I'm working with a vendor who needs to use LDAP queries to pull information on our Active Directory. The query pulls from the 'members' attribute of the AD Group directly. However it only pulls 8 of the 20+ users in this group. If I look at the group's Members tab, I can see all of the users, and they work without an issue. I switch to the Attributes tab and scroll to the members entry view the values which shows only 8 of the users. The LDAP query only pulls these 8 and not the rest of the users.
How do I fix this so the attribute and members list match without deleting/recreating the group? If I delete and recreate it would take down our production environment.
I've tried removing and re-adding users to the group and it does not fix the issue.
I'm going to guess that this group is the primary group for the users that you don't see in the member attribute. Members don't appear in the member attribute if the group is the primary group. I don't know why this is... blame Microsoft.
To find those users, look at the primaryGroupToken of the group. It will be a number. Then search for users that have that value in their primaryGroupId attribute.
Usually, the primary group is the built-in Domain Users group, which always has a primaryGroupToken of 513. So to find users of that, you would use this LDAP query:
(primaryGroupId=513)
According to the documentation, the primaryGroupId attribute is indexed, so you don't need any other criteria.
If you want to learn more about how memberships work, I wrote an article a while ago about What makes a member a member?

Salesforce validations

I'm new in Salesforce and I have to create an app for gym owner.
I made 3 objects, Member, Membership and Booking. My member object has data about gym members like address, date of birth etc.
Membership object has fields like MEMBER(lookup relationship with Member object), START DATA, END DATE and ACTIVE (checkbox to see if membership is stil active).
If membership of that member is still active, I have to prevent customer to create another membership for that member until current expires. How can I do that?
You could pull something like that with validation rule using VLOOKUP function (but then you need to always put something fairly unique & predictable in the Name field on your membership object). I'm thinking something along the lines of "if there exists membership 'Member #1234 active' then VLOOKUP should prevent creating another one like that".
A nasty user could then delete the membership, create new one and restore it from recycle bin :P
So I have better idea for you (still without using any code). Convert membership->member lookup to master-detail relation. This would let you create rollup summary fields, read up about them. Create a rollup field that would be COUNT() of active memberships for the guy. Make validation rule that throws tantrum when you insert new membership and the count is already > 0.

Auto Populate the Opportunity Owner name into custom text field

I am trying to auto populate the Opportunity Owner name in to custom field(Manger) on the same page. But when i am trying it's getting only Id but not Owner Name. This logic i am implementing using Flow in the process builder. Can some one help on this.
In the flow i am using 'Record Lookup'(getting OwnerId and passing to Temp variable), Record Update(Assigning the temp variable to Custom field). But not luck.
Not sure why you would not want the Id. I personally would use the Owner field as a basis and just create a formula field called Manager with this formula: Owner.Name
If you still insist on getting the Owner Name from the flow, you would have to do a SOQL Select in the flow to search and save the Name first.

how can I restrict access to records that are owned by a user

Is it possible to restrict access to records that are owned by a user by filtering out recors with a certain criteria?
For example, I have Contacts set to private and I want to hide certain contact records that have a specific field value (criteria based sharing rule). This works fine for other sales users that don't own the record, but I need to remove visibility to these records from the actual owner of the record. Is that possible or a way to accomplish that?
Thanks for any help.
You could change the owner of the Contact record to a placeholder user. Then the same mechanism the prevents other users from seeing the Contact will hide the record as well.
If required, you could also create a lookup field to track the relationship to the user who can no longer access the record.
Separately, there is a dedicated salesforce.stackexchange.com site for asking Salesforce related questions.

Granting access of specific user to specific (multiple) docs

I'm building a small project with database. I have a user table which has two columns, user_id and name, The second table stores the id and name of some documents: it also has two columns doc_id and doc_name. I want to grant access of specific user to specific (multiple) docs.
For example:
user1 can access doc_2 and doc_3 Only.
user2 can access doc_1 and doc_2 Only and so on.
Users and forms keep changing (eg. after some time i need to add a new doc, and add access to existing or new user to that new doc).
Do i need to change database design? (for example add a column in docs to store name of each user who can access it? ) If this is so, can you tell me what changes i should do?
OR
Is it possible to do by creating views? In this case, do i still need to change the database design? If this is the case, can you tell me an example view please? In this case, will i need to create view for each user? For example if there are 100 users, i will need to create 100 views?
You need a third table (I'll call it user_doc). You need 2 main columns; user_id and doc_id.
You then insert one row for each document and user combo that has access permissions.
If their user_id doesn't appear in the user_doc table with the relvelant doc_id, they don't have permission.
A sample query to get a list of all docs a specific user has access to:
SELECT doc_id FROM user_doc WHERE user_id = #UserId
or to find all users with access to a specific doc:
SELECT user_id FROM user_doc WHERE doc_id = #DocId
You need to have a PERMISSIONS table with relationship between Users & Documents. The columns could be PERMISSIONS_ID,USER_ID (Refer User), DOC_ID (Refer Document). Every time access has to be given to a user for a document this table needs to be populated.

Resources