Options
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 10 subscribers
  • Views 628 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Dynamically filter list of People

abdelbaset

Hello guys,

I’ve a requirement to filter People based on the Department, following is the detailed structure:

  1. A new class “Courier Request” been added
  2. A new workflow “Courier Request WF” been added and linked to “Courier Request”
  3. A new property “Employee” which is “Choose from List of People” been added to “Courier Request” class
  4. A new property “Employee Department” which is “Choose from List of Departments” been added to “Courier Request” class
  5. A new property “Department Employees” which is “Choose from List of Users (multi-select)” been added to the built-in “Department” class
  6. A new property “Department Secretary” which is “Choose from List of People)” been added to the built-in “Department” class

Now through Metadata Card configuration for “Courier Request” class I was able to populate the “Employee” and “Employee Department” properties using Custom Placeholder based on “Current User“ built-in variable.

The business requirement is to allow only the “Department Secretary” to submit the requests on behalf of anyone employee in her department; therefore, I need to filter the list of the employees according to the current logged in secretary department. also, I need to disable the “Employee” property for employees other than the department secretary.

Hopefully was able to explain the case.

 

Looking forward,

Parents
  • +1

    Hi there,

    First of all, I would recommend you to use object hierarchies so you get links/navigations between employees and departments where they work (perhaps you have it already). When you have that, then you have filtering already in place: when someone select department then employees are automatically pre-filtered; so basically employee object should be owned by department object. You can read more here: https://www.m-files.com/user-guide/latest/eng/advanced_object_type_properties.html?hl=owner.

    Regarding creation of that document, the easiest would be to provide creation rights for specific class (attach object permission) for specific user (better specific group). With that way, no one else could create documents.

    Best,

    Dejan

Reply
  • +1

    Hi there,

    First of all, I would recommend you to use object hierarchies so you get links/navigations between employees and departments where they work (perhaps you have it already). When you have that, then you have filtering already in place: when someone select department then employees are automatically pre-filtered; so basically employee object should be owned by department object. You can read more here: https://www.m-files.com/user-guide/latest/eng/advanced_object_type_properties.html?hl=owner.

    Regarding creation of that document, the easiest would be to provide creation rights for specific class (attach object permission) for specific user (better specific group). With that way, no one else could create documents.

    Best,

    Dejan

Children




              

© M-Files Corporation 2024 | Privacy Policy