The customer sites will be updated during week 27 (starting June 29th)
Procurement
In Procurement it is now possible to create Requisitions directly from Component, Job and Item screens.
Service Requisitions could get stuck in draft mode. Is corrected.
When Approval Setup was configured to "Require all levels", sometimes the user would not get any feedback on why Approve button didn't do anything. Is corrected.
Userrights for Evaluation Question and Answer was misplaced under Procurement node. Moved to Address.
If an email address was entered in the "method" step, while sending a Purchase Order, it will not be carried on to next step. Is corrected.
When selecting an item on a free text position on Request For Quote, and then change it to lookup an item, the name of the position remains as the free-text entered. Is updated to now use Item Name when an Item is selected.
On Requisition the Punchout button could sometimes appear even though the customer didn't have punchout in license. Is corrected.
A new UpdateExternalPaymentInfo API endpoint has been added to Invoice controller to let integrations report that an invoice has been paid.
Maintenance
On User, User Group and Resource, it is now possible to set if they are available as Resource on Job and Job History, Responsible and if you can assign jobs to them.
The purpose is to be able to reduce the lists to choose from when selecting in the various scenarios.
On Component overview screen it is now possible to show a map with all components mapped.
Job list grid view occasionally displaying incorrect data on refresh.
Document Management
It is now possible to create email notifications so you can be advised by email before a document reaches expire date.
Vessel Reporting (VRS)
Approving a Vessel Report has been simplified if Approval flow allows it to avoid unnecessary clicks.
Integrations
Added support for mapping Microsoft Entra service principals to SERTICA/INEXTIA users, enabling API integrations without requiring a licensed Azure AD user.
Customers using Azure AD login can now register a service principal and exchange a Microsoft token (via client credentials flow) for an internal API access token.
This simplifies API setup and removes the need to create and maintain a dedicated UPN-based user for service-to-service integrations.
Other corrections
If the customer was using their own mail server, it could be experienced that e-mails for Purchase Orders was sent without attachments. Is corrected.
Problems sending mails with Job Notifications. Is corrected.
Improved flow at login when you are using Azure integrated login.
If the language of the user was different from the user who created a dashboard, Content was not shown. Is corrected.
If a Task list referred a deleted Unit an error would be shown. Is corrected.
On the Analytics Template List of Items standard price and stock value could be calculated different than on the Item screen. Is corrected.
An error could occur if you pressed Save/Cancel while a reference grid was uploading documents. Is corrected.
On Dashboard Pie charts, the coloration had no effect on the legend. Is corrected.
During Counter readings big values was not always fully visible in the grid. Is corrected.
Comments
0 comments
Article is closed for comments.