Options
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Subscribers 8 subscribers
  • Views 685 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

M-Files evaluates the state transition trigger every 60 minutes?

PJ @ DOC

I have only two files with state transition that is code based, so these it should evaluate.

Does it go thru those property based too that are not automatic, but are caused user input? Like when Company = "not empty" ->  cause transition.

That company would never change without new version.

If that is the case it will go thru all files and therefore takes ages to complete.

Can someone explain how that really works?

Cheers

PJ

Parents Reply Children
  • 0 in reply to Joonas Linkola

    Hi ,
    can this Evaluation of trigger criteria for state transition be decreased?
    We have a time sensitive workflow so this is of huge importance to us.
    Is there an implementation ID for this already?
    Thank you.

  • 0 in reply to jakov.bozic

    There is a server-wide registry setting that can be used for this but I would advise against using it. It would affect all workflow transitions on the server and can add significant overhead to your M-Files vaults if the evaluations are run too often, depending on the number of workflows and transitions you have.

    For a time-sensitive workflow I would recommend building a solution based on recurring tasks in the VAF. This would enable you to manage this single workflow only which shouldn't affect the system performance that much.





              

© M-Files Corporation 2024 | Privacy Policy