Skip to content

Commit 06f1cac

Browse files
Martin Sjogrenjenkins
authored andcommitted
Docs: Specified that FxDigitalBarrierOption is single barrier
1 parent 796fc32 commit 06f1cac

1 file changed

Lines changed: 6 additions & 1 deletion

File tree

Docs/UserGuide/tradedata/fx_digitalbarrieroption.tex

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,9 +67,14 @@ \subsubsection{FX Digital Barrier Option}
6767

6868
\end{itemize}
6969

70-
\item BarrierData: This is a trade component sub-node outlined in section \ref{ss:barrier_data}.
70+
\item BarrierData: This is a trade component sub-node outlined in section \ref{ss:barrier_data}.
71+
72+
Note that the \emph{FxDigitalBarrierOption} is a single barrier instrument, and can have only one BarrierData node with one barrier level.
73+
7174
Level specified in BarrierData should be quoted as the amount in DomesticCurrency per one unit of ForeignCurrency, with both currencies as defined in FxDigitalBarrierOptionData node.
7275

76+
Type specified in BarrierData can be one of: \emph{UpAndIn, DownAndIn, UpAndOut, DownAndOut}
77+
7378
\item StartDate[Optional]: The start date for checking if a barrier has been breached prior to today's date. If omitted or left blank no check is made and it is assumed no barrier has been breached in the past. Has no impact if set to today's date or a date in the future. If`StartDate' is provided then the fixings for dates between this date and the asof date are checked to see if the option was triggered. If no fixing is available then we skip that date. This is to allow for backwards compatibility.
7479

7580
Allowable values: See \lstinline!Date! in Table \ref{tab:allow_stand_data}.

0 commit comments

Comments
 (0)