0 votes

Good Afternoon,

Here's what we are trying to accomplish. In our current new user form we have fields for a technician to select company and job title.

An example would be that Company A has the following Job Titles: Sales User, Service User

Whereas Company B has the following: Admin User, Technical User

I have currently configured both the Company and Job Title Property's in my property pattern to have only the specified values I provide, however I'd like to know if when a user selects company A, can they then only have access to that companies job titles. If so how would one implement that?

I appreciate any response as thus far support has been excellent!

Regards,

by (700 points)

1 Answer

0 votes
by (216k points)
selected by
Best answer

Hello,

Thank you for your good words, we really appreciate it.

Currently, this is not possible, but we have such a request in our product backlog. As a workaround until such functionality is available, you can create Business Rules that would not allow creating or updating a user if a user's Job Title doesn't match the Company.

To create such Business Rules:

  1. Create a new Business Rule.

  2. On the 2nd step of the Create Business Rule wizard, select:

    • User and Before Creating a User - for a Business Rule that will cancel creation of new users with mismatching departments,
    • User and Before Updating a User - for a Business Rule that will cancel modification of a user if a mismatching department and/or company was assigned.
  3. On the 3rd step, add the Cancel this operation action. If necessary, you can also specify a reason for canceling.

  4. Now, you need to add conditions when the action must be canceled. Right-click the action that you've just added and click Add Condition.

  5. Select the If <property> <relation> <value> condition type.

  6. Specify Job Title equals Sales User.

  7. Click OK.

  8. Right-click the action that you've added and click Add Condition again.

  9. Select the If <property> <relation> <value> condition type.

  10. Specify Company does not equal Company A.

  11. Click OK.

  12. Click the Add action to a new set link.

  13. Repeat steps 3-12 for as many Job Titles as you have. You'll get something like this:

  14. Finish creation of the Business Rule.

Related questions

0 votes
1 answer

The use case we are looking for is providing a list of titles for users to choose from when initiating a re-hire. We already have a title property pattern established and would ... that we can manage the list in one place. Let me know and as always, thanks.

asked 2 days ago by msheppard (470 points)
0 votes
1 answer

Is there a way I can bypass a property pattern for a set of users? For example we have an AP team that creates an account and want to restrict Job Title and Department to a ... we would like to be able to override that list. Is there an easy way to do that?

asked Sep 5 by curtisa (290 points)
0 votes
1 answer

I have a specific computer property pattern for three different types of computers, which live in three different OUs and are in three different business units. I will have ... How do I enforce a property pattern for a specific business unit at creation time?

asked Jul 17, 2023 by bennett.blodinger (60 points)
0 votes
1 answer

My webform is not picking info based off the property pattern template specifically the logon name and the UPN

asked Mar 8, 2022 by Keonip (180 points)
0 votes
1 answer

We have several domains in use. A users default email reply to address is based on brand employee is working for. Default value in the property ... Save changes $Context.TargetObject.Put("userPrincipalName", $userPrincipalName) $Context.TargetObject.SetInfo()

asked May 5, 2021 by juhota (210 points)
3,549 questions
3,240 answers
8,232 comments
547,815 users