Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Find the user to change password. Locate the password input field and fill in the new password.
When all the verifications are met, press enter or click outside of the input field to submit, the password will be changed if no notifications are displaying otherwise.
When you have located a user, click it and the details will show in a panel (so called "drawer") on the right hand side. Details can be maintained directly in the fields.
By clicking the secondary actions icon additional actions may be possible.
Edit User Name
As of version Release 5.3 it is possible to introduce crew onboard to the VMS and create an efficient, "one time entry" work process in the system.
The functionality with establishing a master role involves giving them access to only their relevant port calls. In order to establish this filter for the user we need to link their credentials to their particular vessel.
Pre requisite for below is that vessel has been created, user for the vessel has been created with security role "Vessel" (only this security role) and internal data tab should be enabled.
Step 1: Access vessel master data screen and insert vessel user in the "Master User" field as indicated below. This action will link the vessel to the user so that Crew only see their relevant port calls in the VMS
For customers with OAuth 2.0 authentication, in Dataloy VMS, MFA can be set up with Auth0's Guardian app. This is an intuitive MFA solution that is easy to set up and use.
If you are uncertain if your VMS is set up with OAuth 2.0 authentication, please let us know, and we can check it for you. Send an email to support@dataloy.com
Dataloy will enable MFA on the installation/environment level forcing all users to log in using MFA in the environment it is configured for.
Once activated and configured, the users will be sent a "push-notification" that must be approved in the app. Simply click the "Allow" button, and you are securely logged in.
Setting up the Guardian app for the first time:
Log in using the system's "web" login screen.
(The URL for this will be provided in case you use the Java version of the VMS)
Follow the instructions on the screen to install and configure the app.
You will scan the QR code shown on the screen with the app, so camera permissions on the phone must be permitted.
When finishing the set-up, a "push-notification" will be sent to your phone.
Click "Allow" to securely complete the configuration.
Log in to the application:
The Java-based version of the VMS:
Log out of the web-based version, as the configuration is now complete.
Start the system and log into the application as you normally do.
Click "Allow" when asked on your phone, and you are securely logged in to the Java-based VMS.
The web-based version of the VMS:
You are already logged in and can continue your work.
Depending on your access permissions the list of users might not be visible.
The "User Administration" module can be located from the menu under System.
There are several sorting and filtering options available for you to narrow down what you include in the list view.
Find the user to disable.
Open the actions menuand click Disable User. This will prevent the user account from logging in.
The user can be found again by filtering on inactive users in the list.
Open the Roles module in the Setup section
Click Create Security Rolein the top right corner.
Fill in the security role name, and select the wanted permissions from the tree.
Click Create.
Filters can be used to locate permissions in the tree.
Within the modal you can find quick filters to easier navigate the tree.
DELETE - Permission to delete an object GET - Permission to retrieve an object POST - Permission to create an object PUT - Permission to update an object PAGE - Permission to access a page ACTION - Permission to execute actions
Depending on your access permissions the list of Security Groups might not be visible.
Open the Security Groups module in the Setup section.
There are several sorting and filtering options available to narrow down what you include in the list view.
1) Open the Security Groups module in the Setup section.
2) Click Create Security Group in the top right corner.
3) Fill in the security group name, and select the wanted roles from the tree.
4) Click Create.
Within the modal, you can find a quick filter to easier navigate the tree.
Depending on your access permissions the list of Security Roles might not be visible.
Open the Roles module in the Setup section
There are several sorting and filtering options available for you to narrow down what you include in the list view.
The System Settings module is available to all users with Administrator role under Setup -> System Settings, or directly through the gear icon in the top right corner of the screen.
You can then navigate to these tabs:
When you have located a Security Role, click it and the details will show in a drawer on the right hand side. Details can be maintained directly in the fields/tree.
By clicking the primary action icon it is possible to make a copy of the selected security role, a modal will open where you enter the name of the copy.
By clicking the secondary actions icon (icon = 3 dots) additional actions may be possible.
Edit Security Role Name
Delete Security Role
Filters can be used to locate permissions in the tree.
Dataloy offers two types of MFA for our customers.
MFA by integrating with the customer's Active Directory (AD) server.
When you have located a Security Group, click it and the details will appear in a drawer on the right hand side. Details can be maintained directly in the tree.
By clicking the icon , it is possible to create a copy of the selected security group, a modal will open where you enter the name of the copy.
By clicking the secondary actions icon , the following actions will be possible,
Edit Security Group Name
Delete Security Group
Filters can be used to locate security roles in the tree.
Widgets in the VMS are dynamic components that seamlessly integrate with the system drawers. They provide real-time or updated information without opening dedicated applications or navigating multiple screens. By leveraging external APIs or data from the VMS itself, widgets offer you quick access to relevant information at a glance.
One of the key features of widgets is their flexibility in terms of customisation and the possibility to perform complex data extractions. The appearance and behaviour of widgets are highly customisable, including adjusting parameters such as font size, colour, layout, and content display.
To create a widget, go to Setup -> Widgets, and at the top right, click Create -> Create Widget.
In the "Contexts" step, choose a primary object type, like "Vessel". This object will be the source when querying data later. Contexts determine where widgets can be used. A widget can't be shown in a drawer without the context that links the widget's object type to the object in that location.
If a widget displays information about a vessel in the "voyage-drawer" context, the "object path" linking the voyage to the vessel would be vessel
. This allows the widget to access vessel data in the voyage drawer.
Field names are displayed as column headers in a widget list, with values in rows. List field styles are fixed. In a widget card, field names act as labels followed by their values. Widget fields control how information is shown, either on a card or a list. You can customise the styles or use the defaults.
Ensuring that the "Value Data Type" matches the type of value in the data source is crucial for accurately displaying values.
Value Data Type | Display |
---|---|
To create a widget data source, go to Setup -> Widgets, and at the top right, click Create -> Create Widget Data Source.
A link to the "home page URL" address will be shown on the widget card. This is for reference only and doesn't affect data retrieval.
The "Widget" field connects the data source to a widget, and once selected cannot be changed unless the Widget is deleted.
The base URL and HTTP method form the starting point of the request's URL, with the parameterised URL template appended to it.
Widget data sources support various authentication methods, including username/password and token-based systems like OAuth 2.0.
After setting up the connection to the data source, you can customise data retrieval by adding parameters. These can be dynamically taken from the widget object or set as static values. Depending on your data source and request type, you can include these parameters in the URL path, request body, or HTTP headers. This flexibility allows for precise data fetching, fitting various scenarios and data source setups.
To create a dynamic filter value, enter a "Variable Name" and select an "Object Path". If the parameter type is set to "URL Parameter" or "Request Body", insert the variable placeholder into the template using the syntax {{variableName}}
. When the widget loads, the placeholder will be replaced with the real value from the main object.
To populate your widgets with data from your source, use a JSONPath expression for each field that matches the desired data. Separate multiple JSONPaths with a semicolon (;
) to combine results with a space.
To display multiple rows in a list widget, ensure the JSONPath result from your source is an array.
The JSONPath syntax supports powerful filtering and functions. For a more comprehensive understanding and examples of how JSONPath expressions are written, refer to the detailed examples in the official documentation.
In this page, you are able to completely decide both the Label and the Field (or 'Object Path') of choice, that will show up on the new Invoice Template (PDF). There are now two new sections on the PDF that gives you selectable options; Selectable Fields Below Header section and Selectable Fields Below Document Lines section (click for better view):
In both sections, you can choose a Label name of your choice and then pick its corresponding Object Path field. E.g. Vessel (or 'Vessel Name') as Label, combined with the Object Path that leads to where the Vessel Name field is stored (= documentLines.voyage.vessel.vesselName
).
In Selectable Fields Below Header section, can choose up to 8 pairs of labels and object paths, while up to 4 pairs in Selectable Fields Below Document Lines section. But it's completely up to you if you only want to display only the Label, or display only the Object Path. You can also choose the order, and on which row.
Remember that the order of your chosen fields will reflect on the invoice PDF as well!
E.g. giving values to Label 1 & Object Path 1, Label 4 & Object Path 4 and Label 7 & Object Path 7 will display accordingly on the PDF, while the other rows will show up as "whitespaces".
The last part, Object Path, needs to be selected in order for our API to register what field you have actually chosen to be shown on the invoice PDF. We can understand that the second part is a bit too technical for the average user, and it's not intended to remember the full path anyways, so we have added a pop-up (or modal) to help you navigate through the different fields to select from. Meanwhile, the Label field is a freetext field; you can write whatever you want, and erase with the Backspace key.
Non of these fields are required.
You can open this modal by clicking on the input field itself (which is non-editable), or click on this icon:
Both options will open up this modal:
Below the title, you can see the word document
, which represents the root object of the modal. Meaning, you can search for anything inside the document object, or select one of the fields when scrolling up and down. You will quickly see that each sub-object will open up a new list of new objects again, e.g. Account
will open up the possibility to choose Account Code
, Account Desc
, etc. You can also search on the objects within document > account
, or scroll. Most of the valuable data is likely under document > documentLines
.
You can also clear the the input field by clicking on this icon:
The icon is not visible until you have chosen a path first.
The blue area to the left of each sections illustrates ca. where on the PDF these fields will be shown. You can also read more about the invoice PDF itself here.
You can from the General tab now toggle between the new and the old Invoice Template (PDF). This can also be set up by Dataloy's developers internally:
Another part of VMS's new invoicing preferences settings can be found under Master Data -> Companies -> choose a company -> Invoicing Preferences: #invoicing-preferences-tab (from v.7.7 and up).
The settings on this page enable administrators to customize default behavior in VMS, e.g. Days extra in port controls the number of extra days automatically added to new port calls. Note that these system settings are applied globally to the environment, which means any change alters the functionality for all users (click for better view):
Share Voyage
When the setting is enabled, all estimate voyages may be edited by other users than the creator.
Use cost from service orders
Allows automating the process of filling in port costs. If the option is enabled, the port cost will match the total amount among service orders linked to a port call.
Use new invoice template
Allows you to choose between printing documents using the new invoice template, or the old one.
Use port currency
Automatically sets the port cost currency to the local value. For example, a port call in Bergen will have the currency NOK.
Auto post service orders - a group of settings
The system enforces automatic posting of documents that are created from a service order. For instance, if a service order contains multiple lines and the status of the service order changes to the specified status*, the related document lines will be combined into a posted document. This setting eliminates the need to manually select the service order document lines, assemble them into a document, and then post the document.
*Service order status - indicates the base status for enabling the auto-posting functionality. If a service order is changed to this status or higher, auto-posting will create documents for the existing linked document lines, and future lines.
Default payment term - specifies the default payment term used for auto-posted documents. Required for auto-posting to work.
Default baseline term - specifies the default baseline term used for auto-posted documents. Required for auto-posting to work.
Days extra in port
This setting is used to specify the default number of days extra in port for each new port call.
Percent extra at sea
Allows defining a value used to set percent extra at sea for each leg in the system.
Previous port call count
Identifies the number of previous port call shown on each TC out voyage.
JSONPath | Result |
---|---|
JSONPath | Result |
---|---|
JSONPath | Result |
---|---|
JSONPath | Result |
---|---|
date
Date-time formatted according to user locale
double
Decimal numbers
integer
Normal integers without decimals
link
URLs or email addresses become clickable links. Field name is used as label in card
string
Strings without formatting
$.fruit
"Apple"
$.color;$.fruit
"Red Apple"
$..fruit
"Apple", "Banana", "Grapes"
$..size
"Large", "Medium", "Small"
$..color
"Red", "Yellow", "Purple"
$.sizes.keys()
"Apple", "Banana", "Grapes"
$.sizes.*
"Large", "Medium", "Small"
$.colors.*
"Red", "Yellow", "Purple"
$..*[?(@.size=='Medium')].fruit
"Banana"
$..*[?(@.size=='Small' && @.color=='Red')].fruit
"Strawberry"
Open the Users module in the Setup section.
Click Create New Userin the top right corner.
Fill in all required fields listed below in the Create New User window.
Click Create.
Vessel Users
The security role "Vessel" is designed to grant access for users onboard vessels. See Create a Vessel Master user.
Permissions in the Java VMS
In order to perform actions in the Java VMS a user must also belong to a Security Group.
Groups, roles and their permissions are maintained in the Manage Permissions module in the Java VMS.
Field
Description
User Code
A short identifier used for logging in
User Name
The user's name that is displayed in the system
Password
Password used for logging in
Email address for notifications
Security Groups
Restricts access to modules and the API