SAP Signavio Sync

1.5.102026-09-07

• The «Open in Signavio» chip now shares a line with other extensions' card chips. Turbo EA 2.132.2 lines those chips up in one row; this release drops the spacing the chip used to add for itself, so a card carrying chips from two extensions no longer grows a row for each. The «Maintained in SAP Signavio» notice on a pulled card still gets a full line of its own.

1.5.92026-09-06

• The Signavio revision on a process card is now the revision number you see in Signavio, not an internal id. The field used to show the 32-character revision identifier, which nobody can read or look up; it now shows the revision counter Signavio's own screens show. Every mirrored card is refreshed on the next pull. If your workspace does not report a revision number, the field is left empty rather than showing the identifier again.

1.5.82026-09-05

• The stored Signavio credential is now only ever sent to the address it was saved against. Until this release, an administrator of this extension could ask the panel to test a connection, or browse categories and folders, against a different Signavio URL while leaving the credential box empty — and the credential saved for your real tenant, which on the workspace surface is your password, was posted to that address. Testing another address now asks you to paste the credential for it. Nothing changes for normal use: re-testing your saved connection with the credential box empty works exactly as before.
• Redirects are no longer followed. The setting applied to every call the extension made, including the login request that carries your password, and it was never needed for anything Signavio actually does.
• A new Signavio URL must be an https:// address, as must the separate UI URL — that one is never fetched, but it is written into your cards as a clickable link. An address you have already saved keeps working untouched.
• The «Open in Signavio» chip now checks whether you may see the card it is on. It was available to any signed-in account, which could otherwise read back the Signavio link for any card in the landscape. It now asks Turbo EA the same question the card page itself asks, so people keep the chip on cards they can open — including cards they reach through a stakeholder role rather than through their own role — and lose it on cards they cannot.
• Refused connections now explain themselves in your language instead of showing an internal error code.

• A «Recent activity» list on the settings panel. Signavio Sync recorded whole sync runs but nothing else, so when a connection test or a category picker was refused you saw one message and, once you clicked away, nothing at all. Saves, connection tests and refused browses are now written down with SAP Signavio's own answer, newest first, under the run history — which is where you look when a colleague reports «it stopped working» and you were not the one watching. The list keeps the last 500 entries and tidies itself; it is an operator's aid, not an audit trail — Turbo EA's own Audit Log remains that.

• This release requires Turbo EA 2.130.0 or newer (it was 2.91.0), because the per-card check above is answered by Turbo EA itself rather than by this extension. Upgrade Turbo EA first; until you do, Turbo EA will decline to install this version and your current one keeps running.

1.5.72026-09-05

• This extension now ships a changelog. Every release from here on documents what changed for you in this file, and it travels inside the signed bundle so it is on disk wherever the extension is installed. The upgrade notes that used to live in the README have moved here.

1.5.62026-09-05

• The French interface calls a card «fiche» rather than «carte», matching Turbo EA's own vocabulary. «Carte» is kept only where it genuinely means a map.

1.5.52026-09-03

• The settings panel says what the Signavio account must be able to do, in Signavio's own words, in a block that stays on screen whether or not a token is already stored — the next token is usually created long after the first one.
• A stored token is now marked with a «Token stored» tag inside the field itself, so "is my token saved?" is answered at a glance. Pasting a new value replaces it; leaving the field empty keeps it.
• The mapping table has an empty state instead of a blank panel.

• A refused Signavio call now shows Signavio's own explanation. These answers used to be relayed as 502, which a proxy in front of Turbo EA replaces with its own error page — so the reason never reached the browser and the panel showed a bare error. The reason is now relayed intact and written to the sync log.

1.5.42026-09-02

• Picking a value from any of the four settings dropdowns no longer blanks the field. Selecting an option stored the wrong thing internally, leaving the control empty and making the save fail. Reported against 1.5.2, fixed here.
• The packaged wheel now carries the same version as the extension, so an install can no longer end up with mismatched halves.

1.5.22026-08-27

• Folder links open the Signavio Process Hub repository browser rather than the older Explorer route. Run one sync after upgrading: each mirrored folder card is rewritten once so the new link reaches cards that are otherwise in sync.

1.5.12026-08-27

• Names no longer carry HTML entities. A folder Signavio displays as Level 3 & 4: Employee Recruitment arrived as Level 3 & 4: … and became the card name verbatim.
• A process now links to the process. The old deep link used a route Signavio does not recognise, so it fell back to the containing folder. Run one sync after upgrading: both fixes change what is written to every mirrored process card, so each is rewritten once — one history entry and one Modified bump per card. Nothing is deleted.

1.5.02026-08-27

• The mapping table names both ends of a pairing and says what they are, without a read per row across two systems. Run one sync after upgrading to repair the labels on rows that were already in sync — nothing is republished and Last synced does not move.

• A crash on push.

1.4.12026-08-27

• The two new mapping-table components failed to render.

1.4.02026-08-27

• Background sync with live progress, so a large workspace no longer runs behind a spinner with nothing to show.
• A mapping table pairing each Turbo EA card with its Signavio object — direction, status, category and last sync — with both ends as links. Existing rows show a card id until the next sync fills the name in.

1.3.12026-08-27

• One bad entry costs one card, not the whole sync. A single malformed object used to abort the run.

1.3.02026-08-27

• The Trash folder is skipped structurally rather than by name.

1.2.22026-08-27

• Hardened the diagram parser against a malformed-input trap.

1.2.12026-08-27

• A 500 when pushing an update to an existing Signavio dictionary entry.

1.2.02026-08-27

• Pulled cards record where they came from in Signavio and who owns them.

• The change gate now notices a Signavio edit that moved only a timestamp. Signavio's updated and revision are written to the card, so a change to either has to reach it. The first sync after upgrading rewrites each linked process card once to populate the new section — one history entry and one Modified bump each. It settles after that run.

1.1.02026-08-27

• Sync preview — see what a run would write before it writes it.

• Dictionary categories resolve by their stable key rather than by name, and a preview no longer writes a category back.

1.0.02026-08-27

• First release. Two-way sync between SAP Signavio Process Manager and Turbo EA: processes and folders mirrored onto cards, dictionary entries pushed back, and a settings panel under Admin → Settings → Integrations. Signavio serves these resources at two different API surfaces depending on the tenant; the extension detects which one answers and reports it in the connection test.