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 Reply Children
  • 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.

  • Thanks Radu. Will have a try tomorrow and let you know. Somehow "Created by" is properly rendered in notification editor. Will post it here.

  • Also, you can try this for initial creation notification - State: Created and Version =1 

  • Well in object metadata all placeholders look like %Property_Smth% Slight smile 

    In the VAF of Advanced notifications there a command to expand these %Property_Smth% into text.

  • Hi Radu, 

    This is the problem I am facing:

    When it is sent, it looks like this:

    This happens only with some properties.

    When I start adding property, it looks good on beginning, I can also see that it matches to correct alias in References:

    When I save, it is represented with %% (others properties are fine). Really strange. 

  • The reason is that you have spaces in your alias.

    You have 2 options:

    1) Either update the alias to have no space (you might need to logout from vault to update the references in the dashboard)

    2) In the placeholder editor go to references, and change the metadata from using alias, to using the ID:

  • Thanks Radu! This is exactly the problem. Somehow we have chosen aliases with spaces, now it bites us back. Will need to be careful with ID (hope is the same on all environments).

    This would work for initial creation:

    We would have version 1 only once and then it would increase actually.

  • Glad you got it to work as intended Slight smile

    Cheers!