The M-Files Community will be updated on Tuesday, April 2, 2024 at 10:00 AM EST / 2:00 PM GMT and the update is expected to last for several hours. The site will be unavailable during this time.

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

Limiting M-Files Assignments

Hi All,

I have a bit of an interesting challenge that I'd like to automate a solution for, but not sure if there's a great solution.

M-Files (unfortunately) has a very limited user base in my organization though I occasionally need to pass through M-Files assignments to non-frequent M-Files users. This means that these non-users do have M-Files user accounts.

One individual in particular (at the corporate level) has said that he will only use M-Files for a specific project for specific tasks (workflow tasks for for reviewing/approving Contract Documents), and that all other M-Files notifications, assignments, etc. will be ignored. Is there a way to only allow assignments to be generated for that individual for the Contract Documents workflow but not for other workflows (e.g., a meeting document approval workflow)?

One (inelegant) idea I have is to create a separate person object that is only visible to the person who initiates the Contract Document approval workflow (that Person object would be labeled such that it's obvious what it's for). The user account for that particular User would be tied to that person object. The person object that everyone else can see would not be tied to a user account (and thus wouldn't receive automatically-generated M-Files assignments.

Any other suggestions would be appreciated!

Thanks in advance

Thoughts?

Parents
  • Hi AKmarsh,

    I am not sure if it is possible to halt the creation of assignments entirely.
    One way that I thought of would be to maintain an additional property that would programmatically fill out the ones that want assignments.
    Kind of like a conditional user list, if you will, that is updated based on an objects properties.

    If State == x -> Find users with property y (Could indicate what layer of notifications he/she wants to receive) -> Populate user list -> Assign to people on the list
Reply
  • Hi AKmarsh,

    I am not sure if it is possible to halt the creation of assignments entirely.
    One way that I thought of would be to maintain an additional property that would programmatically fill out the ones that want assignments.
    Kind of like a conditional user list, if you will, that is updated based on an objects properties.

    If State == x -> Find users with property y (Could indicate what layer of notifications he/she wants to receive) -> Populate user list -> Assign to people on the list
Children
No Data