Dynamic notifications (based on specific metadata)

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 

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 

Also you can develop a VAF to comply to your needs 

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%  

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

Well in object metadata all placeholders look like %Property_Smth%  

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

Cheers!