Skip to main content

· 2 min read
NPS Development Team

Status: ✅ Resolved
Closed: December 26, 2025
Labels: bug, HRM and Payroll, PyR
Issue Link: View on GitHub

Description​

Contact Details​

nevena@nps.rs

What happened?​

  1. zvještaj Bolovanje preko 60 dana nisam uspjela da pronađem u programu
  2. OPPND koji šaljem opštinama svakog mjeseca ne dozvoljava da u filteru obračuna unesem sve obračune iz kojih treba da preuzme podatke. U trenutnoj verziji sistema, u kojoj radim, te filtere unosi sam sistem.

-RAD-1 ne nudi da odaberem filter obračuna i filter obračuna za naknade.

  • M4 nije dobar, M-12 nisam uspjela da pronađem u sistemu, OPD-2 u testnoj verziji unosi iznose sa decimalama, u trenutnoj verziji zaokružuje. -Ukupnu rekapitulaciju i izvještaj Doprinosi i ostale obaveze nisam uspjela da pokrenem jer mi ne nudi da odaberem obračune u filteru obračuna -Obračunski list takođe nisam uspjela da pokrenem -Spisak kredita po kreditorima u testnoj verziji prikazuje samo ime zaposlenog i uplaćeni iznos, dok u trenutnoj verziji prikazuje ime, poziv na broj odobrenja, broj rata, iznos rate, ukupan iznos, ranije uplaćeno, uplaćeni iznos, saldo. Takođe, u testnoj veziji sabira sve obustave kod određenog kreditora, koje se odnose na jednog zaposlenog, kada zaposleni ima više obustava kod kreditora, u trenutnoj verziji je izdvajao obustave, što je bolje zbog praćenja uplaćenih rata po različitim osnovama

What extentsion are you seeing the problem on?​

Localization features

Relevant log output​

No shell output provided.

Sharepoint Task 1885

This issue has been resolved and will be included in upcoming releases.

· One min read
NPS Development Team

Status: ✅ Resolved
Closed: December 26, 2025
Labels: bug, LOC
Issue Link: View on GitHub

Description​

Contact Details​

No response

What happened?​

Kreirati izveštaj Porez i prirez po opštinama (Tax & Contrib. by Community 2 (50110)). U prilogu txt file sa Cges BC14 baze. u filteru broj obračuna omogućiti odabir više obračuna.

prirez.txt

What extentsion are you seeing the problem on?​

Localization features

Relevant log output​

No shell output provided.

Sharepoint Task 1902

This issue has been resolved and will be included in upcoming releases.

· One min read
NPS Development Team

Status: ✅ Resolved
Closed: December 24, 2025
Labels: task, accepted, priority medium ➖, overdue, PyR
Issue Link: View on GitHub

Description​

Contact Details​

nevena@nps.rs

What happened?​

polje "primarna pozicija" se menja u slučaju da se otvori druga pozicija sa različitom grupom obračuna. sa aktivne pozicije se odčekira i čekira se novootvorena pozicija koja nije sa istom grupom. Molim za ispravku. Ako potoji aktivna pozicija sa grupom ZARADA (tip redovan rada) , polje primarna pozicija ostaje označeno. U slučaju da se otvara nova pozicija sa grupom ZARADA, BOLOVANJE, POROD, samo u tom slučaju oznaka sa predhodne pozicije se skida.

What extentsion are you seeing the problem on?​

Localization features

Relevant log output​

No shell output provided.

Sharepoint Task 1851

This issue has been resolved and will be included in upcoming releases.

· One min read
NPS Development Team

Status: ✅ Resolved
Closed: December 24, 2025
Labels: bug, priority medium ➖, HRM and Payroll, overdue, PyR
Issue Link: View on GitHub

Description​

Contact Details​

nevena@nps.rs

What happened?​

U izveštaju Rođendani zaposlenih (NPSPyR Employees Birthday (51105100) prikazani su zaposleni koji nisu više aktivni. Molim da se ispravi, izveštaj treba da prikazuje samo aktivne zaposlene. HR Status "Aktivan"

What extentsion are you seeing the problem on?​

Localization features

Relevant log output​

No shell output provided.

Sharepoint Task 1865

This issue has been resolved and will be included in upcoming releases.

· One min read
NPS Development Team

Status: ✅ Resolved
Closed: December 23, 2025
Labels: suggestion, accepted, priority medium ➖, HRM and Payroll, PyR
Issue Link: View on GitHub

Description​

Contact Details​

tijana.petrovic@nps.rs

No response

Describe the solution you'd like​

Potrebno je da polje Br.rešenja na evidenciji odsustva bude editabilno

Describe alternatives you've considered​

No response

Additional context​

No response

Sharepoint Task 1869

This issue has been resolved and will be included in upcoming releases.

· One min read
NPS Development Team

Status: ✅ Resolved
Closed: December 19, 2025
Labels: task, suggestion, accepted, EIN
Issue Link: View on GitHub

Description​

Contact Details​

danica@nps.rs

Polje Order Reference ID u tabeli Purchase Invoice Header (49021562) je ograničeno na 20 karaktera. Prilikom unosa fakture direktno na SEF-u u to polje je moguće uneti neograničen broj karaktera, klijenti već imaju takve slučajeve a mi trenutno prilikom preuzimanja nabavne e-fakture "sečemo" višak karaktera ako ima više od 20.

Describe the solution you'd like​

Ukoliko je moguće, potrebno je proširiti broj karaktera za ovo polje na barem 35.

Describe alternatives you've considered​

No response

Additional context​

No response

Sharepoint Task 1875

This issue has been resolved and will be included in upcoming releases.

· One min read
NPS Development Team

Status: ✅ Resolved
Closed: December 18, 2025
Labels: suggestion, Localization features, accepted, LOC
Issue Link: View on GitHub

Description​

Contact Details​

silvija.micik@nps.rs

Na proknjiženoj nabavnoj fakturi na akciji Ažuriraj dokument potrebno je dodati polje Datum dospeća, kao što je već dodati na proknjiženoj prodajnoj fakturi na akciji Ažuriraj dokument, kako bi moglo da se izmeni datum dospeća i na proknjiženoj nabavnoj fakturi.

Describe the solution you'd like​

Potrebno je dodati polje datum dospeća na akciji Ažuriraj dokument na proknjiženoj nabavnoj fakturi kako bi moglo da se imeni datum dospeća na proknjiežnoj nabvanoj fakturi kao što može na proknjiženoj prodajnoj fakturi.

Describe alternatives you've considered​

No response

Additional context​

No response

Sharepoint Task 1877

This issue has been resolved and will be included in upcoming releases.

· 3 min read

Overview​

Automatically creates blog posts when you publish a release on your app repositories. Each blog post includes:

  • Release notes
  • List of resolved issues (from NPS-Support)
  • Installation instructions

Setup​

1. Create a Personal Access Token (PAT)​

  1. Go to GitHub Settings → Developer settings → Personal access tokens
  2. Create token with these scopes:
    • repo (full control)
    • workflow (update workflows)
  3. Copy the token

2. Add Secret to App Repositories​

For each app repository (Business-Central-Localization, HRM-and-Payroll, etc.):

  1. Go to repository Settings → Secrets and variables → Actions
  2. Click "New repository secret"
  3. Name: DOCS_REPO_TOKEN
  4. Value: Paste your PAT
  5. Click "Add secret"

3. Add Workflow to Each App Repository​

Copy .github/workflows/EXAMPLE-app-repo-notify-release.yml to each app repo as:

.github/workflows/notify-release.yml

4. Label Issues in NPS-Support​

Make sure issues in NPS-Support have the repository name as a label:

  • Business-Central-Localization for localization issues
  • HRM-and-Payroll for payroll issues
  • Electronic-Invoicing for e-invoicing issues
  • etc.

How It Works​

  1. You create a release on an app repository (e.g., Business-Central-Localization v1.5.0)
  2. notify-release.yml workflow (in app repo) triggers and sends data to npsbeograd.github.io
  3. sync-release-to-blog.yml workflow (in this repo) receives the data:
    • Fetches all closed issues from NPS-Support with matching label
    • Creates a blog post in /blog/ (root, not updates/)
    • Includes release notes and resolved issues list
  4. Blog post is published automatically

Blog Post Structure​

Release posts go in /blog/ (root level), not /blog/updates/:

blog/
├── 2025-11-28-release-serbian-localization-v1-5-0.md  ← Release posts
├── 2025-11-29-release-hrm-payroll-v2-3-1.md
├── updates/                                            ← Issue updates
│   ├── 2025-11-20-issue-265-...md
│   └── 2025-11-21-issue-294-...md
└── authors.yml

Manual Trigger​

You can also manually trigger a release blog post:

  1. Go to Actions tab in npsbeograd.github.io
  2. Select "Sync App Releases to Blog"
  3. Click "Run workflow"
  4. Fill in:
    • Repository name (e.g., Business-Central-Localization)
    • Release tag (e.g., v1.5.0)
    • Release name (e.g., Version 1.5.0 - Tax Updates)
    • Release body (optional release notes)

Example Blog Post​

When you release Serbian Localization v1.5.0, a blog post is created:

---
slug: release-serbian-localization-v1-5-0
title: "Serbian Localization v1.5.0 Released"
authors: [nps_team]
tags: [release, Serbian Localization]
---

# Serbian Localization v1.5.0 - Tax Updates 2025

We're excited to announce the release of **Serbian Localization v1.5.0**!

## Release Notes

Updated tax rates and fiscal printer integration for 2025 regulations.

## Issues Resolved

This release includes fixes for **5 issue(s)**:

- [#265](url) - Payment comparison issue
- [#267](url) - Email sending error
- [#261](url) - Internal calculation
...

## Installation

To install this update, please visit Microsoft AppSource...

Benefits​

✅ Automated - No manual blog post writing
✅ Comprehensive - Shows all resolved issues in one place
✅ Professional - Clean format with release notes
✅ Organized - Releases in /blog/, issues in /blog/updates/
✅ RSS feed - Subscribers get notified of new releases

Troubleshooting​

Q: Blog post not created after release?

  • Check that app repo has DOCS_REPO_TOKEN secret
  • Verify notify-release.yml workflow is present in app repo
  • Check Actions tab for workflow errors

Q: No issues listed in blog post?

  • Ensure NPS-Support issues have the correct repository name label
  • Labels are case-insensitive but must match repo name

Q: Want to edit a release blog post?

  • Blog posts are in doc/blog/YYYY-MM-DD-release-*.md
  • Edit manually and commit

· One min read

This blog is organized into two categories:

📢 What's New (Root Level)​

Location: /blog/*.md

Manual blog posts written by the NPS team about:

  • Major feature announcements
  • Product releases
  • Company news
  • Tutorials and guides
  • Industry insights

Example:

blog/
  2025-11-28-new-electronic-invoicing-features.md
  2025-12-01-year-end-payroll-guide.md

🔧 Issue Updates (Subfolder)​

Location: /blog/updates/*.md

Automatically generated posts from closed GitHub issues in NPS-Support:

  • Bug fixes
  • Feature implementations
  • Tasks completed
  • Product-specific updates (LOC, EIN, PyR, TRO, MFM, TRL)

Example:

blog/updates/
  2025-11-20-issue-265-payment-comparison-issue.md
  2025-11-21-issue-294-salary-setup-configuration.md

RSS Feeds​

Both categories are included in the main RSS feed:

  • RSS: /blog/rss.xml
  • Atom: /blog/atom.xml

Creating Manual Posts​

To create a "What's New" post, add a markdown file to the root blog/ directory:

---
slug: your-post-slug
title: Your Post Title
authors: [author_id]
tags: [tag1, tag2]
---

Your content here...

Issue updates are created automatically - do not edit files in /blog/updates/ manually.