Configuration of the product in Higson is composed of:

• Domain configuration
• Decision tables
• Functions

Operators make changes in configuration in work session. Open session (by this we understand every change made in range of configuration) is visible only to operator, who is making changes. In the moment of publication that session changes are seen by all the users and are applied to structure.

There are two basic ways to publish your session: by Main toolbar > Tools > Sessions or shortcut session button in the top right corner of the application Higson.

1. When a user chooses to go through the main toolbar (A):

   

   the screen will show with a list of all sessions:

   

   While looking for specified session may filter possible matches by:

   • All sessions, Open, Published, Rejected (A)

   • Session id, Start date, End date, User (B)

   Your guidelines will be applied automatically. There is no need to fill all search cells or filter decision tables at once. Input only those which you find necessary. Sessions view is in the form of a table with columns (C):

   Id.	Column name	Description
   1.	Status	Status of session: Published, Open, Rejected
   2.	User	The user who owns the session
   3.	Start date	Date of creation of session
   4.	End date	Date of publishing or rejecting session
   5.	Remote	Flag informing if the session created by higson runtime rest
   6.	Description	Description of a session after publishing or rejecting

   When a session from the list is selected (by clicking on it) detail information will show:

   

   In this view, we can see a summary of the selected session: elements number, the start date of the session, and user owner (A).We can publish or reject changes in (B) (only if the Session in (A) is marked as Open). This view also contains three sections: Decision table, Domain, and Function with assigned table containing columns (C):

   Id.	Column name	Description
   1.	Operation	Operation on the element: Create, Update, or Delete
   2.	ID	ID number of element
   3.	Element	Element name
   4.	Created/Modified	Date of operation executed at the element
   5.	Actions	Column for reverting changes on one separate element on this session

2. When the user chooses to go through the shortcut session button (B) in the top right corner of the application Higson**:**

   

   very similar session details to the previous one view will appear:

   

   After clicking on (A) Reject or Publish changes view will pop up:

   

   After confirmation, changes will be PUBLISH or REJECT with no message or a message in the description field filled.

   When two users edit the same object, they will overwrite their changes during publishing. It is recommended to organize configuration work in a way that prevents overlapping edits between different users. To check another user’s changes, go to the main toolbar and Main toolbar > Tools > Sessions (like in 1.). From the list of sessions, choose the one whose author is the other user. Then when detailed information about the session occurs, click on the change made on your object. Then you will see how that element looks after (that user) changes and may make a comparison with your current version, then apply any changes in your version by clicking on your session on the session list.

   The session mechanism in Higson Studio is the foundation of safe and structured configuration management in a shared environment. It enables users to independently introduce, test, and modify changes without risking interference with others’ work. Awareness of which actions are session-based and which are applied immediately in the environment helps maintain consistency and reduces the risk of configuration errors. By properly managing sessions — for example, by establishing standards for session descriptions or dividing work to avoid unnecessary conflicts — teams can retain full control over ongoing modifications and ensure high-quality collaboration within Higson Studio.