> For the complete documentation index, see [llms.txt](https://ieg4.gitbook.io/onevu-digital-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ieg4.gitbook.io/onevu-digital-platform/openprocess-cases-and-workflow/openprocess-flex/notification-placeholders.md).

# Dynamic Notifications

One of the key elements of OpenProcess is the ability to notify someone when a process moves from step a to step b. Even with OpenProcess core it is possible to send text/facebook messenger messages containing content specific to the step that's just started or completed.

![Various OpenProcess Action Types](/files/k3GOwI10NDYIsgkjkihT)

With OpenProcess Flex you can have branches in processes meaning the level of contextualisation in these messages can be taken even further. E.g. if it's a high priority issue send standard message a. If it is medium priority send standard message b when the step completes. 

In OpenProcess Flex, you have the means to use the case details present on a process to dynamically personalise these notifications. 

By way of a recap - by case details on a process - we mean the data that is held in the form of 'Fields'. Fields are data items that have been mapped automatically by:

* a form (built in eDesigner) or
* the [**Create Process API**](/onevu-digital-platform/openprocess-api/methods.md) by an external application or
* manually as a part of a process.

The following are fields associated with a process in its set up:

![Fields on a process that can be used in notifications](/files/6y2kp0c4axx0xKeEVI0R)

Using a new template field function, you are able to personalise the messages that are sent using data held on the case as well as the form reference for the form that they completed if relevant.

To add fields to notifications you need to add the following where the field's code is Field1:

**{% FieldValue Code="Field1" %}**

So, if the Field's Code was as follows for a person's mobile number:

![Field Code to use in the dynamic notification placeholder](/files/DG2GI28fR7htijowvtpt)

The format would be:

**{% FieldValue Code="MOBILENO" %}**

 

This is the format for all fields except for the following two exceptions:

**1) Form Reference**

Where a process was triggered by an IEG4 form, it is possible to use this in the notifications you send. This is not a field per se, it is a process attribute.

So to add the form reference to a notification use the following:

**{% ProcessAttribute name="ExternalReference" %}**

**2) Today's date** 

If you want a notification to show today's date in it - particularly relevant if you want to tell someone to do something within say 7 days from today's date, you use the following:

*{% DateTime FormatString="dd/MM/yyyy" %}*

The format above is the default and will show it as 19/11/2021.\
However, all of the variations found [**here**](https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings) are supported. E.g.

"MMMM dd, yyyy" will give November 19, 2021

"dddd, MMMM dd, yyyy" will give Friday, November 19, 2021

###


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ieg4.gitbook.io/onevu-digital-platform/openprocess-cases-and-workflow/openprocess-flex/notification-placeholders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.