Headings

Article content goes here.

Emphasis Styles

Below are emphasis styles:

This is bold.

This is monospace.

This is italics.

This is underline.

This is monospace-italic.

Subscript, Superscript and Special Characters

Below are subscript, superscript and special characters. Trade mark should display "TM", copyright "C", Registered Mark "R", and Service Mark "SM"

This is_subscript.

This is^superscript.

This is trademark.^™

This is registered.^®

This is service.^(SM)

This is copyright.^©

Symbols

Oxygen Supports a selected few symbols as listed below:

✓ =Check mark
✗ =Ballot mark
® =Registered trademark
© =Copyright symbol
™ =Trade mark
℠ =Service mark
Use the HTML entity decimal values

If you need support for other symbols – please℠ raise a Jira ticket. If you simplay ass the symbol without using the Insert Symbol tool (CTRL + SHIFT + Z), then most likely your symbol will be removed during the build, or be displayed as a "Hash" symbol.

Testing Para Indents

Each paragraph should appear indented to the right of the para above it.

Para indent 1: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Para indent 2: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Para indent 3: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Testing Bridgeheads

Below are bridgeheads, each bridgehead should have a different size going from largest to smallest.

Bridgehead h1

Bridgehead h2

Bridgehead h3

Bridgehead h4

Bridgehead h5

Bridgehead h6

dyn_help_taskpath

Below is a dynamic taskpath which should point to Company Information.

Setup > Company > Company Information

Testing Images

Below is a PNG image saying "this is a test image". The image type is set to "screenshot" and has a gray border in Help Center.

Here is an icon which looks like a scaled down image. this is test icon

Below is a PNG image with type set to "composite". It should look like "screenshot" but without the border.

Below is a PNG image with type set to "diagram". It should look like a "screenshot" but without a border.

Below is an SVG, test functionality.

Itemizedlist, Orderlist, Minitoc

Item 2
Item 1
Item 3

Sublists

Full circle 1x shifted right

Empty circle 2x shifted right

Full square 3x shifted right

Empty circle 4x shifted right

Empty circle 5x shifted right

Full square 3x shifted right

Minitoc

Displays the list left-aligned, based on the indent level. Each line in the list is preceded by one space and is shaded gray. Preserves paragraph tags between a list item and any following paragraph.

this is a minitoc 1
this is a minitoc 2

Orderedlist

Below is an orderedlist with an itemizedlist inside of it.

item 1, 1x shifed right
item 2, 1x shifed right
1. Item a. 2x shifed right
2. Item b. 2x shifed right
  - Item 2.2.1 should appear as full square, 3x shifed right
  - Item 2.2.2 should appear as full square, 3x shifed right
item 3

Procedure

Below is a procedure with a title and numbered steps.

Test procedure

step 1 of the procedure
step 2 of the procedure
step 3 of the procedure

Programlisting

Javascript

Testing code sample — without setting the line-numbers parameter. Default behavior should be to include line numbering. The colors should correspond to prism highlighting.

                            if(!$PdfSet->{_Collection}->[$x]->verifyFileExists("_OutputFoFilePath"))
                {
                    $Error .= "Failed to generate $FoBookFile\n";
                }
                if($FoError)
                {
                   $PdfSet->{_Collection}->[$x]->updateErrors($FoError);
                }
                $Parallels->finish(0,[$x,$FoResult,$FoSummary,$FoError]);

Now testing the same code sample — but without line numbering! (line-numbers=”no”)

                if(!$PdfSet->{_Collection}->[$x]->verifyFileExists("_OutputFoFilePath"))
                {
                    $Error .= "Failed to generate $FoBookFile\n";
                }
                if($FoError)
                {
                   $PdfSet->{_Collection}->[$x]->updateErrors($FoError);
                }
                $Parallels->finish(0,[$x,$FoResult,$FoSummary,$FoError]);

Now testing the same code sample — but with line numbering explicitly switched on! (line-numbers=”yes”)

                            if(!$PdfSet->{_Collection}->[$x]->verifyFileExists("_OutputFoFilePath"))
                {
                    $Error .= "Failed to generate $FoBookFile\n";
                }
                if($FoError)
                {
                   $PdfSet->{_Collection}->[$x]->updateErrors($FoError);
                }
                $Parallels->finish(0,[$x,$FoResult,$FoSummary,$FoError]);

Java

            private void setPreferences() throws SOAPException
{
   stub = (NetSuiteBindingStub) _port;
   stub.clearHeaders();
   SOAPHeaderElement prefHeader =
   new SOAPHeaderElement("urn:messages_2017_1.platform.webservices.netsuite.com", "preferences");
   Preferences prefs = new Preferences();
   prefs.setWarningAsError(new Boolean(false));
   prefs.setUseConditionalDefaultsOnAdd(new Boolean(false));
   prefs.setUseConditionalDefaultsOnUpdate(new Boolean(false));
   prefs.setDisableMandatoryCustomFieldValidation(new Boolean(true));
   prefs.setDisableSystemNotesForCustomFields(new Boolean(true));
   prefs.setIgnoreReadOnlyFields(new Boolean(true));
   prefHeader.setObjectValue(prefs);

   stub.setHeader(prefHeader);
}

C#

            // Set up request-level preferences as a SOAP header

Preferences prefs = new Preferences();
_service.preferences = prefs;

// Set preference to specify that warnings should be treated as errors

prefs.warningAsErrorSpecified = true;
prefs.warningAsError = false;

            /**
 * @NApiVersion 2.x
 */

require(['N/file'], function(file) {
    function createAndSaveFile() {
        var fileObj = file.create({
            name: 'test.txt',
            fileType: file.Type.PLAINTEXT,
            contents: 'Hello World\nHello World'
        });
        fileObj.folder = -15;

        var id = fileObj.save();
        fileObj = file.load({
            id: id
        });
    }

    createAndSaveFile();
});

Q&A

This is a Q&A. There should be a question title with a bigger fond and bold and below an answer as a regular text

Question

Answer

Answer 2

Question 2

Another answer

Sidebar

This is a related topics sidebar. Check if the text and links appear in a box.

Note, Tip, Warning, Important, Example, Informal Example, Dynamic Messages

Below is a tip, text should appear in a green box.

Tip:

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Below is a note, text should appear in a blue box. Check if it does and if the para indents inside of it work as expected.

Note:

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Para in note indent 1

Para in note indent 2

Para in note indent 3

Below is a warning, text should appear in a red box. Check if it does and if the itemized list and orderedlist inside of it work as expected. Items 1,2,3 should have full circle.

Warning:

Warning

item 1
item 2
item 3

ordereditem 1
ordereditem 2
ordereditem 3

Below is an important, text should appear in a yellow box. Check if it does and if the itemized list and sublists inside of it work as expected.

Important:

Full circle 1x shifted right

Empty circle 2x shifted right

Full square 3x shifted right

Empty circle 4x shifted right

Empty circle 5x shifted right

Full square 3x shifted right

Below is an example, text should appear in a gray box with a title.

Example

Below is an <informalexample>, the text should appear in a gray box.

Test informalexample text

Below are dynamic messages

Dynamic message for a feature should show as a warning

Out of date message

SS1 banner

SS2 banner

Applies to with text following

This is even more of a testing text to see if it appears correctly

Applies to with banner following

Test linking to a ReUsed Article

Here is a link to the Article for Testing Reuse and here is a link to the Subsection inside a Reused Component. Do the links work?