• ctrl-8 is referred to by SITS users as "gold star", is used as a wildcard in codes etc and looks like -*
  • F5 Retrieve records
  • F12 Clear current form
  • Ctrl-s Save
  • Ctrl-z Zoom (for text fields that aren't big enough)

Main SITS Menu System

  • Enter code (eg DTO) and press <tab>
  • MUA for evision and USR for client

DTO - Data Transfer Out

cf SITS column

SITSWODSInterface Repository
CAM_MAVPaperOccurrence / PaperResultPAPER_OUTCOME
Link Dictionary = CAMS
Link Entity = MAV
Program_code = CAM+MAV

Enter one or more, press F5 to retrieve.

No DTO records? - Make a change to the data and retry.

Get new json output

Scroll records, check Process Statuses, make user first record is Ready for Generation, the rest, not like %Generation%. To change all to Under construction, Change the first record do Menu > Edit > Global Update, Click OK, click Update All, Save (ctrl-s). (Then change the first to Ready for Generation and save again)

Generate DTO with command: (Change parameter to match Event Out Rule)

\\\USG-share\program\SITS\siapp\vision\dev\uniface\bin\uniface.exe /asn=\\\USG-share\program\SITS\siapp\vision\dev\adm\uclisi.asn stutalkmon SYINT05MAV

Re-retrieve(F5) or refresh(ctrl-r) record. Open Data (click arrow) to see JSON.

Changing Data

Enter Link Entity code into SITS Menu System

Change something.

WODS Subscriber

Stored in mulesoft/workspace/MdataSubscriberWODS of


Template: src\main\app\MSubscribersWods.xml.template has usage as comments.

Get SITS JSON as above.

Stutalk Publisher

Creating New Publishers

Copy'n'edit method (one publisher)

TUP (trigger)
Entity code=SYR (for example)
  1. retrieve(ctrl-r) an existing entity (twice if delete is needed)
  2. Menu > File > Release (copy)
    • Make new codes in the same style (TUP/SMG/MCG codes are slightly different)
  3. edit/fix all details, save
  4. Menu > Misc > Projects > Add record, Project=SYINT04
  1. (SYINT04SYR) retrieve, release
  2. edit, save, add to project
  3. reuse new DTC code for new EOR, XET, WRF, FMU, DTS, & HTM codes
  1. (SYINT04SYR) retrieve, release
  2. edit, save, add to project
SMG (Message group)
  1. release, edit, save, add to project
There are two of these, one to send the DTOs and one to clean up the old DTOs based on expiry date.
  1. (SYINT04SYR-*) retrieve, release each
  2. edit, save, add to project
XET: see SITS#XET/XSL Patterns/examples
  1. (SYINT04SYR) retrieve, release
  2. edit,
    default values (any 4 spare feilds) and XSL usage mappings
    (values passed from DTO)
    <xsl:variable name="SYR" select="EXCHANGE/SYR/SYR.SRS"/>
    <xsl:when test="<<DTO_CHGT>> = 'D'">DELETE</xsl:when>
    <xsl:when test="$SYR/SYR_DSYN.SYR.SRS = 'D'">DELETE</xsl:when>
  3. save
  4. (Entity window) Menu > File > Export ...
    Data format: XET
    Template:(XET code)
    Check 'input' XML
  5. add to project
XSL & XSD Options, WRF
  1. (SYINT04SYR) retrieve, release
  2. edit, save, add to (project OR SEED)
  3. XSL Files :gitlink (files may differ from those in SITS)
  4. copy, edit, commit, push
FMU: see also SITS#XSL maintenance
  1. Resource Code (SYINT04SYR) retrieve, release
  2. edit, save,
  3. export entity, check JSON
  4. add to (project OR SEED)
  1. (SYINT04SYR) retrieve, release
  2. edit, save, add to project
    edit, save, add to project, don't forget password

Promote to (UAT)

In Dev, XPRB (project only)
Project Code (SYINT04)
Project Group: BAU
Build Name, Description (SYINT04)
NameVersion = sysdate
Y Include Project
Y Build & Export
Filename (SYINT04)
  1. Build & Export
  2. Menu > Help > eVision Login
  3. System Tools > Release Form
  4. Pick project, next, wait,next, yay.
  5. System Tools > Release on demand
  6. Pick environment (UAT), release type:Projects
  7. Pick project, Run Release, wait, yay.

Basic outline
  1. TUP triggers on changes
  2. XET generates XML and
  3. transforms with XSL Web Resource File (WRF)
  4. EOR sends it out

Input XML to the XSL comes from XET

The XET Code is typically the same as the XSL filename.

Once retrieved, the Overview tab shows the XML tree of data from the SITS tables

e.g. SYINT02ADD has STU.SRS under ADD.MENSYS because the student record is linked through the address record (to get the right student data obviously)

Double-clicking exchange feilds under the relevant node lets you:

(Fields tab) add/remove/edit the fields to the xml
(Export Format/Value) format the feild data and set default values. See #XET/XSL Patterns/examples
(Export Profile) is the joining conditions between tables. e.g. on NMO.SRS under MOD.CAMS, Key-code NMO_CODE has Value ##MOD_CODE.MOD.CAMS##

Apply. Save(Ctrl-s)

The Exchange Text(plain text) and Exchange View(styled text) tabs have the input XML structure (albeit not necessarily with matching case...)

To see a sample XML input with data values
  1. make the XSL inactive by editing on the XSL & XSD Options tab.
  2. Save twice.
  3. Load up the data record (e.g. ADD) and choose Menu-File-Export
    Data format
    double click Template to choose the XET
    Select file and click OK
    make the XSL ACTIVE by editing on the XSL & XSD Options tab.
    Save twice.

Basic Maintain XSL transform files sequence

FMU - File Maintenance Utilities can export all the XSL files

  1. FileType
    Resource Code
  2. F5 - Fetch (no visual indicator)
    Export / Import Directory
  3. 3. Export selected WRF records...
    edit files
  4. 4. Review and Import Files into WRF records...
  5. 5. Publish
  6. DURING SITS PROJECT ONLY Repeat 1,2,4,5 for SITS:DMSeed \\\USG-share\program\SITS\siapp\Shortcuts\DMSeed

XET/XSL Patterns/examples

Examples of XET code patterns used in publishers

Export Profile Values

On NMO.SRS under MOD.CAMS, Key-code NMO_CODE has Value ##MOD_CODE.MOD.CAMS##

Combined Code#Name Export Formats

This is effectively just a case statement. &S"W"="W#Withdrawn";"E"="E#Enrolled"
Lookup from code table PSL.SRS &G[PSL.SRS:·<·<PSL_CODE.PSL.SRS·>·>#·<·<PSL_NAME.PSL.SRS·>·>] Note the use of middot character.
To find the right code table and field names:
The example is from the SYINT04NSM XET, NSM_PSLC (Period slot code) Export format.
  1. Open NSM and find the Period form field
  2. select it and press F1 to confirm it and view the field's code(column name) and details:
    Period Slot (PSL) code. This field is validated by an entry in the Period Slot Table (PSL) table. (6 characters)

    Double-clicking on this code field will display a selection list of all codes matching the specified pattern."
  3. double-click the field to open the code table and press F1 again to view the field codes and details.

Misc Export Formats


These functions/formats are in the manual

  • [file:// Special Registers and Functions]
  • [file:// SRL Formatting Reference]

to experiment with them:

  1. Open PRA
  2. Retrieve Program Code TEST_BUILD_TEXT
  3. double-click the Program Code field
  4. edit the text area on RHS
  5. double-click the text area to see results in the lower area.

Header data values

Unused fields(which fields vary) are given default Export Values of: <<DTO_CHGT>> <<DTO_GUID>> <<DTO_CRET>> and <<DTO_CRED>> to supply the data for the JSON Message.Header .Event, .MessageId, & .DateTime respectively.

If these fields start being used later, this will break as these default values will be overridden by their use values.