Skip to content
Nextera DigitalLearn

Getting started with Bright

This page is for people new to the team — how to get access, which environment is which, and the habits that save time from day one.

Environments

Section titled “Environments”
Environment API
Development https://broker-api-dev.tigana.co.id
SIT https://broker-api-sit.tigana.co.id
Production https://broker-api.tigana.co.id

The frontend is built separately per environment from the files in src/environments/. Each file sets apiUrl, websocketUrl, merchantCode and apiKey.

Getting access

Section titled “Getting access”

Access is managed inside the application:

  1. Someone with User Management rights creates your user at /system/user.
  2. The user is granted one or more Accesses at /system/access-right, or inherits them through a group.

The access-rights model is explained in User & access right.

Reading the navigation

Section titled “Reading the navigation”

The left-hand menu is built from the tobject table, filtered by the Accesses you hold. Its five main areas:

Area What it holds
Contracts Party and contract data
Operation The risk placement chain
Finance Billing, payment, journals
Report Reports and analytics
System Parameters, users, queue, batch

When a menu does not appear, the cause is almost always Access — not menu configuration.

Reading document codes

Section titled “Reading document codes”

Document numbers carry information. Take BL26030226:

BL      document type (Billing)
2603    period year and month
0226    sequence number within that period

The format is configurable per document type — see Autonumber.

Reading status

Section titled “Reading status”

Status codes recur across the whole system: DR draft, TV validated, TW waiting approval, PA partially approved, TA approved, CM completed, TX cancelled.

The first four things to check

Section titled “The first four things to check”

This order resolves most complaints.

1. Check the system date

Section titled “1. Check the system date”

Bright does not use today’s date. It uses fSystemDate(), which reads the SYSTEM / SYS_DATE property.

SELECT dbo.fSystemDate();

If the value lags, new documents get a stale date and a stale period number. This is the single most common cause of “the date is wrong”.

2. Check Access, not the menu

Section titled “2. Check Access, not the menu”

A missing menu, a button that does not appear, an action that is refused — almost always Access. Remember that the granularity is per screen and per action, so somebody can list billings but be unable to approve one.

3. Check who is in the approval chain

Section titled “3. Check who is in the approval chain”

Approvers are pruned by limit when the document is validated, not when it is approved. Changing a limit does not affect a document already in flight. If somebody has “disappeared” from the approval list, their amount was most likely outside the limit when the document was validated.

4. Check the parameters, not the code

Section titled “4. Check the parameters, not the code”

Most accounting behaviour is configured in data: posting rules, account rules, dimensions, tax, scaling. Before suspecting a bug, check the relevant rules engine.

Things that are commonly misunderstood

Section titled “Things that are commonly misunderstood”

Next

Section titled “Next”