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

Dynamic notifications (based on specific metadata)

Hi community and M-Files, 

We currently have quite a few e-mails sent through notifications bound to workflow steps. In the most cases, this works well for us but slowly we have cases where this is not enough anymore.

Here couple of requirements and scenarios:

  1. X days before review date (metadata on document), specific users should start getting an e-mail
  2. If document is in particular workflow state for more than X months, we should notify an author
  3. When we have multiple transitions into the same workflow state, we should send different e-mail notification (we have tried to mitigate it through more general messages)

How would you approach this? I've tried advanced notifications (see this post) but it does not seem to be suitable for scenario 3). Would advanced notifications cover scenarios 1) and 2)?

Thanks.

Dejan

Parents
  • Hello,

    Advanced Notification should cover all scenarios.

    For case 3, maybe you can create a metadata to hold previous state, and create the rules based on that :).

    You can also select which state transision will trigger a notification.

  • Thought about that :). If I have some metadata I can calculate and take with me, that would help.

    Hm, but I am not quite sure we could use state transitions. I could use workflow state but transition? How would it work?

    Thanks for example

  • Like this Slight smile

    And toggle the require state change between Yes and No. Did not test it, just added the condition to show you :)

  • Thanks :). That would actually help, than I don't need separate property (I think)

  • well it needs testing Slight smile

    Also you can develop a VAF to comply to your needs Slight smile

  • Hi Radu, 

    Thanks for hints. 

    One notification rule would work (Review -> Draft):

    However, initial creation notification rule does not seem to work (don't have a chance to create snapshot), basically where "State transition = Created" (This is the name of transition, I have also verified that it maps correctly with alias in editor). 

    Could it be there is some limitation with initial creation transition in editor? Or perhaps I miss something?

    I also have a trouble with some properties which are not mapped in editor at all (our own document id and CreatedBy property). These properties just stay in the editor in form %PROPERTY_Document ID% or %PROPERTY_CreatedBy% or similar and are not replaced in email sent.

    Have you experienced anything similar?

  • Well, for initial creation maybe you can try to add an intermediate state? so No State -> Saved -> Created, and try to add the transision rule for notification to "Saved -> Created".

    Regarding the placeholders, this is how one of my notificare rule looks like and have no issue with expanding the information in the notification.

Reply
  • Well, for initial creation maybe you can try to add an intermediate state? so No State -> Saved -> Created, and try to add the transision rule for notification to "Saved -> Created".

    Regarding the placeholders, this is how one of my notificare rule looks like and have no issue with expanding the information in the notification.

Children