Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
titleRequired Headers
  • Authorization: Token token="<your session token here>"
  • Content-Type: application/json
  • User-Agent: rest-api
  • X-ClientId: <the client id here>

...

Info
titleParagraph Descriptor Fields


FieldTypeOptionalDescription
StyleStringRequiredThe paragraph style  
ConditionStringOptionalAn expression that determines if the paragraph belongs in the report
Condition_CommentStringOptionalA free-form comment describing the Condition field
TextStringRequiredThe paragraph's text, which might contain %SUBSTITUTION_FIELD%s



Info
titleParagraph Descriptor Styles

The following table lists the various styles that can be used to apply common styling across the generated document.

ValueDescription
H1Heading #1
H1NBHeading #1, but not emphasized (bold)
H2Heading #2
H3Heading #3
IndentNormal paragraph, but shifted to the right
IntroNormal paragraph style, in the introduction. Can have alternate styling, if needed.
ListBullet list
WarnAdds emphasis to highlight something to the user
NormalNormal paragraph style



Info
titleCondition Grammar

The grammar for conditions is very trivial. It's simply: "expr op expr".

The Flex lexical description looks as follows:

 

[ \t\n]                          { /* skip spaces */ }
\%([a-zA-Z_][a-zA-Z0-9_]*)\%     { yylval.string = yytext; return IDENTIFIER; }
[0-9]*                           { yylval.string = yytext; return INTEGER_LITERAL; }
\<=                              { return LT; }
\<=                              { return LTE; }
==                               { return EQ; }
\>=                              { return GT; }
\>=                              { return GTE; }
.                                { yyerror("Unknown token: %s", yytext); yyterminate(); } 

A Bison grammar looks as follows:

binary_expr
    : /* empty */
    | value LT value
    | value LTE value
    | value EQ value
    | value GT value
    | value GTE value
;
 
value
    : IDENTIFIER
    | INTEGER_LITERAL
;

...