MS-1070 Persistent step cache fix

[luhmirin-s]

JIRA ticket
Will be released in: 2025.3.0

Root cause analysis (for bugfixes only)

First known affected version: 2025.1.0

• The issue is with the persistent orchestration cache - the change in settings/permissions triggers full recreation of OrchestrationActivity from the persistent store. And when unmarshalling step params (that are kept as Bundles), the custom parcelable parameters in those bundles lose the type information and are restored as generic maps.

Notable changes

• Replace step parameters bundle with custom serialisable definition.
• Introduces separate marker interfaces for step params and results to enable serialisation to work.
• Once the cache issue was fixed, another related issue surfaced - when a step's fragment returns result after configuration change (nav graph recreation), the result handlers were not triggered.

Testing guidance

• Run all orchestration flows in all possible combinations.

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[luhmirin-s]

Uncovered code is either navigation contracts (basically just API definitions).

[sonarqubecloud]

Quality Gate failed

Failed conditions
63.8% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud